Portal Kernel Upgrade jcontrol.exe dying exitcode = 66

[former_member196664]

Hi ALl,

Got another issue today. I upgraded Kernel in portal 7.20_ext manually. jcontrol.exe died. Config tool also not starting due to DB connection issue. Pls help.

**********************************************************************

JControlStartJLaunch: program = E:\usr\sap\EPQ\JC00\exe\jlaunch.exe

-> arg[00] = E:\usr\sap\EPQ\JC00\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\EPQ\SYS\profile\EPQ_JC00_sapepqas
-> arg[02] = -DSAPINFO=EPQ_00_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=E:\usr\sap\EPQ\JC00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2968
-> arg[06] = -nodeName=bootstrap_ID5821950
-> arg[07] = -jvmOutFile=E:\usr\sap\EPQ\JC00\work\jvm_bootstrap_ID5821950.out

-> arg[08] = -stdOutFile=E:\usr\sap\EPQ\JC00\work\std_bootstrap_ID5821950.out

-> arg[09] = -locOutFile=E:\usr\sap\EPQ\JC00\work\dev_bootstrap_ID5821950

-> arg[10] = -mode=BOOTSTRAP

-> arg[11] = pf=E:\usr\sap\EPQ\SYS\profile\EPQ_JC00_sapepqas

-> lib path = PATH=C:\j2sdk1.4.2_13-x64\jre\bin\server;C:\j2sdk1.4.2_13-x64\jre\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;E:\usr\sap\EPQ\SYS\exe\uc\NTAMD64

-> exe path = PATH=C:\j2sdk1.4.2_13-x64\bin;E:\usr\sap\EPQ\JC00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;E:\usr\sap\EPQ\SYS\exe\uc\NTAMD64

[Thr 4072] Wed Nov 19 14:25:14 2014

[Thr 4072] *** ERROR => invalid return code of process [bootstrap_ID5821950] (exitcode = 66) [jstartxx.c   1647]

[Thr 4072] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID5821950] (rc = 66)

[Thr 4072] JControlCloseProgram: started (exitcode = 66)

[Thr 4072] JControlCloseProgram: good bye... (exitcode = 66)

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:474)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:156)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:946)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)
... 14 more
Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
... 17 more

[Bootstrap module]> Problem occurred while performing synchronization.

[Reagan · Accepted solution]

Hello Kavitha

Could you supply the contents of the bootstrap.properties file?

E:\usr\sap\EPQ\JC00\exe\cluster\bootstrap\bootstrap.properties

Also run this command and provide the output.

sapcontrol -nr 00 -function GetVersionInfo

Reagan

[former_member196664 · Accepted solution]

Hi All,

I have fixed the issue with config tool. Removed sys admin role from SAPEQDB user. I m fine with this issue now. I will attempt changing JDK as per ur advise and move forward with SUM.

Thank you all again.

[Matt_Fraser]

Hi Kavitha,

What release of the Portal are you using, and what versions of SQL Server and Windows? One possibility is that you have chosen a kernel version that is incompatible with your Windows or SQL Server version, or you have chosen 32-bit or 64-bit binaries when you really needed the other one. What was your prior kernel version?

The EXT kernel is only compatible with Windows 2008 and higher and SQL Server 2008 and higher. If you are using Windows 2003 and/or SQL Server 2005, that could be a problem. Also, the EXT kernel requires a different version of C runtimes to be installed in Windows. It comes with a vcredist executable that you must run once on the server. See Note 1553465 about that.

No doubt you searched for "exitcode 66" and found Note 997510, and followed the troubleshooting steps there. Did you confirm that your database is running? This error can also indicate the database is down.

Did you update with both SAPEXE.SAR and SAPEXEDB.SAR? You should use the same patch version for both. You also must replace IGS with the EXT version of IGSEXE and IGSHELPER.

Check Note 1553301 for more information about the 7.20_EXT kernel and its restrictions.

Finally, depending on your Portal (NetWeaver) release, you may need to deploy updates to SAPJTECHF and SAPJTECHS. See Note 1636252.

Regards,

Matt

[former_member196664]

As per note 997510  - Troubleshooting J2EE Engine 6.40/7.0 Bootstrap Issues

If java.lang.ClassNotFoundException is present as a cause for the bootstrap error, most likely the driver class specified in Secure Store is incorrect, or the driver jar file cannot be found.  In this case check whether the path to the driver jar files is configured correctly in SecureStore.

I cant login to config tool. Please help how to fix this. I can login in SQL management studio with user SAPEPQDB and with a specific password.

Thanks,

Kavitha Rajan.

[Sriram2009]

Hi  Kavitha

Could you check this SAP KBA

1602004 - J2EE System fails with "exitcode = 66"

1950926 - System cannot start due to login SQLServerException

BR

SS

[Matt_Fraser]

You don't need to login to Config Tool in order to check the bootstrap log files. The Note you referenced tells you where you can find them in the filesystem. Until you check those files, you don't know if it's a Secure Store issue or not.

However, you should be able to access the Config Tool with the system down. Config Tool doesn't depend on the system being up. If you can't get in with Config Tool, then you may have something else as a cause. Did you change any passwords, at the database or OS level?

[former_member196664]

Sriram,

First note has exactly my issue. My problem I am not able to login to config tool. DB is up and running.

[former_member196664]

Matt,

1109274  - New JDBC driver for NetWeaver 7.0 and higher             class and url has to be changed in secure store. But I am not able to login to config tool.

[former_member196664]

I did not change any password.

[Sriram2009]

Hi

1. You database services status show's started?

2. Is it dual stack? if it yes just run the r3trans -d

BR

ss

[Matt_Fraser]

Are you using SQL Server 2005? If so, then you can't use the 7.20_EXT kernel. It's not compatible. If this is the case, I recommend you swap the kernel back to whatever you had before, and/or update to the 7.21 kernel (not 7.21_EXT).

[former_member196664]

This is Portal server. I can login to SQL management studio and verified SAPEPQDB user is not locked.

[former_member196664]

Matt,

I performed this kernel upgrade in EP dev. With no issues. Copied the NTAMD64/ and exe folders from DEV which was deployed by SUM. Since my SUM has issue, I tried manually to deploy kernel. It is SQL 2005.

[Matt_Fraser]

7.20_EXT kernel is not compatible with SQL 2005. You have to switch back to 7.20, or to 7.21. This is your problem.

[former_member196664]

Matt,

This is interim, next will be CRM upgrade SQL upgrade.. My project for another 6 months. PAM is showing SQL 2005 though.