Symptom
Starting the J2EE engine has not been successful. The following exception messages are visible in the file traces:
dev_jstart:
********************************************************************************
*** ERROR => Node 'bootstrap' failed with exit code 558.
***
*** Please see section 'Failures in the 'synchronizing binaries' phase'
*** in SAP Note 1316652 for additional information and trouble shooting advice.
********************************************************************************
jvm_bootstrap.out:
Starting to initialize database connection
Exception occurred for component [internal/unkown] of type [unkown]
...
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
...
...
Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLException caught: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s)
...
... 13 more
Caused by: java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
Read more...
Environment
- Release Independent
- SAP NetWeaver
Product
Keywords
Exit code 558, database, J2EE engine not started, login failed , KBA , BC-JAS-SF , Startup Framework , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.