cancel
Showing results for 
Search instead for 
Did you mean: 

J2ee engine refuse to start at bootstrap was EP 7.0 MSSQL

Former Member
0 Kudos

Hello

I performed the Install of a SAP WAS EP portal 7.0 on a Windows 2003 server with MSSQL 2005 database .

Everything was running fine until yesterday where the J2ee engine refused to start and jcontrol stopped

at bootstrap with a return eror code 66 . The only maintenance task performed on this server was a J2ee license

install (various time but unsuccesfully because wrong license file)and and the install of the mssql Bacward package

in order to solve backup problem with data protector (SQLServer2005_BC) .

I have tried to , bring offline and online the DB (Ok ), restart the SAPSID_XX service in control pannel and reboot

the server , without results .

Nothing was modified in the bootconfig .

I noticed that when I stopped the DB in SQL studio as DOMAIN\sapsid (Windows integrated) user or SAPSIDuser(Sql auth)

I can take it offline but I'm not able to bring it online back (error cannot open user default database, login failed).

I must log with the user sa to start it fine .But once up ( I can query the db) the J2ee is failing to start again .

Here is the main exerpt form the jvm bootstrap

Exception occurred:

com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties

Caused by: java.sql.SQLException: [NWMss][SQLServer JDBC Driver][SQLServer]Invalid object name 'J2EE_CONFIG'.

at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)

The full trace output :

Bootstrap MODE:

<INSTANCE GLOBALS>

determined by parameter [ID0542064].

-


Exception occurred:

com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)

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.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data,

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)

at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)

at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:62)

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)

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: java.sql.SQLException: [NWMss][SQLServer JDBC Driver][SQLServer]Invalid object name 'J2EE_CONFIG'.

at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)

at com.sap.nwmss.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseStatement.postImplExecute(Unknown Source)

at com.sap.nwmss.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseStatement.commonExecute(Unknown Source)

at com.sap.nwmss.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)

at com.sap.nwmss.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)

at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:97)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:281)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:248)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getConfiguration(DBAccessDefault.java:578)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:102)

... 15 more

[Bootstrap module]> Problem occurred while performing synchronization.

Thanks a lot for your help .

Lionel

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

I had a similar error and found it to be that my schema user had the 'sysadmin' 'server role' in the sql install.

hope it will help if you get it again

ivo_kotev
Employee
Employee
0 Kudos

Thank you Eitan ritk Bi. I have the same problem and after I removed sysadmin role everything is fine.

Former Member
0 Kudos

Thanks a lot. my issue also got resolved after I removed sysadmin server role from sap<sid>db user from SQL Server Management Studio.

ricardocarrega_filho
Participant
0 Kudos

Thanks for sharing the solution, guys! Removing the sysadmin role from the schema also did the trick on my case.

Best of luck!

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello

I've tried to troubleshoot this issue using the SAP STN tool , but it returned an error

no sap data found .

Finally I performed a full reinstall of the Portal .

Thanks for your help .

Lionel

Former Member
0 Kudos

Lionel,

Thanks for your update.

cheers,

Hari.

Former Member
0 Kudos

Hello

Thanks to both of you for your help .

- I already reboot the Server without results .

- The mssql is listening to the port 1433 as in the config tool . The URL string is specifying the server name in Upper case , while the command hostname display it in lower case, is it important fo the Jdbc connection ?

- The authentication mode for the database was already set to mixed mode .

The J2ee engine used to run fine since then . How can I test the Jdbc login against the database for the SAPXXXDB user ?

Thanks a lot again.

Lionel

Former Member
0 Kudos

Hi,

Check if the Database is in Mixed Authentication mode. It is necessary for the Java Engine to be running.

Also check the Database Coonection URL in the Configtool. Make a note of the port in the URL. And make sure that SQLSERVER is running on th smae TCP/IP Port.

Thanks,

Tanuj

Former Member
0 Kudos

Hi,

Try to give a OS reboot, it may solve.

Regards,

Hari.