Visual Administrator: Logon
Failure 
Problem Description
The user cannot log on to the Visual Administrator of the J2EE Engine.
|
Scenario Type: |
Error analysis |
|
NetWeaver Component: |
Web AS Java: J2EE Engine (BC-JAS) |
|
Validity: |
J2EE version >= 6.30 on Windows and Unix platforms and a Web Application Server >= 6.40 SP1 |
Possible Error Sources
Error Source |
Analysis |
Error while connecting. Connection lost. |
● J2EE Engine is not running |
Error while connecting. User authentication failed |
● Invalid user name/password ● User has been locked |
Error while connecting. Cannot open connection on host: <IP-address> and port: 50004 |
● P4 port is incorrect ● Wrong transport layer selected |
Error while connecting com.sap.engine.services.security.exceptions.BaseSecurityException: Internal server error. An error log with ID [000D9D9558AB00520000000700000B440003DE272FEA7E00] is created. For more information contact your system administrator at … |
● SAP DB is offline |
Decision Roadmap
Prerequisites
You have configured the list of connection properties for connecting the Visual Administrator tool to the J2EE Engine, or you have selected a previously configured entry that you want to connect to.
Main Tools
● Visual Administrator
● SAPMMC
● SAP Config Tool
Execution
...
Start the Visual Administrator tool, select a connection entry from the list of connections and choose Connect.
If
your logon fails, take a look at the error message by clicking on the 
icon.
Analysis
1. The J2EE Engine is not running
The task error message appears like this:
The cause of the problem should be that the J2EE Engine is not running on the host. In this case, connect to the host and restart the J2EE server/cluster using the SAPMMC.
If the J2EE server is running but the connect fails, continue with step 2.
2. Invalid connection parameters
The task error message appears like this:
The cause of the problem should be:
● P4 port is incorrect
● The wrong transport layer was selected
You can find the correct P4 port on the J2EE Engine Config Tool:
The batch file named configtool.bat can be found under: <path Of J2EE installation>/<SysID>/JC<nr>/j2ee/configtool
Verify also if the transport layer specified by the connection parameters has been selected correctly.
See 
Creating a New
Connection Entry how to specify the correct connection parameters for
logging on to the J2EE Engine.
3. Invalid user name / password or the user has been locked
If the task error message looks like this
The cause of the problem should be:
● Invalid password/user name
● User has been locked
Look at the file: …server0\log\system\security.log
to find the initial exception, such as
Invalid password for user Administrator.
Verify if the user name and password specified by the connection parameters are correct.
If there is a message in the server’s log similar to: …\log\system\security.log
Invalid password for user TEST_USER.
User 'TEST_USER' locked after 6 unsuccessful attempts to login.
The user cannot log on to the J2EE Engine using the Visual Administrator because he or she has been locked due to numerous unsuccessful logon attempts. In this case you should make sure that an administrator user can log on to the engine and unlock the user you need. In the cluster tab, select the Security Provider service next to the server node. Select the tab User Management ® Tree to choose the locked user. To unlock the user select Unlock.
If you have not yet created any additional administrator user(s), then you cannot log on to the J2EE Engine to perform administrative tasks. To correct this situation, set up an emergency administrator user. See SAP Note 669848 for setting up an emergency administrator user.
4. Database is offline
The task error message appears like this:
Error while connecting
com.sap.engine.services.security.exceptions.BaseSecurityException: Internal server error. An error log with ID [000D9D9558AB00520000000700000B440003DE272FEA7E00] is created. For more information contact your system administrator.
at…
This internal server error indicates that the problem is not on the user side. Instead, it is a server problem. Here the database is down, but this is not visible in the error message. The exception Internal server errorindicates that you ought to look at file: …/log/system/server.log.
The server.log contains Dbconnection exceptions:
Connect to the host and open the SAPMMC. Select the database node in the SAP Systems tree. To start the SAP DB, select Online on the State tab in the Database Manager.
