How to find out portal version, patch level information, components installed and system level information

From SLD

To find out the desired information about the portal, you can use the System Landscape Directory.

If an SLD server exists in your NetWeaver landscape, enter the following URL to access the SLD:http://<sldserver&gt;:<port>/sld
If you’re running a standalone portal, use the following URL to access the SLD informationhttp://<portalserver>:<port>/sld

From Portal

If the SLD hasn’t been set up or the above links won’t work, you can get the desired information directly from the portal server.

1.To find out about the current version of portal you are working on.

2. The patch level information on the current portal.

3. The components installed on the current portal.

4. The system level information of the portal.

All the above information can be gathered by accessing the URL below.

For System Information: http://<hostname&gt;:portnumber/sap/monitoring/SystemInfo

For Component Information: http://<hostname&gt;:portnumber/sap/monitoring/ComponentInfo

OR

http://<hostname&gt;:portnumber/index.html and access the link System Information

Exit codes in JAVA stack and it’s significance

Here are the exit codes in JAVA and it’s reason. Also for some of the return code you can refer to the snote mentioned with the exit code:

#Common exitcodes:

0    =Normal exit.

11  =Cannot initialize xml parser (Service Manager) or error reading properties (likeyinst tool).

666=Out of memory.

#Engine exitcodes:

1        =Forced shutdown.

888    =Engine shutdown cannot finish for “haltTimeout” the VM is halted with this exit code.

999    =Error occurs during AS Java shutdown.

-1501 =Framework error.

-333   =Missed broadcast due to network problems (MSLib).

333    =Missed broadcast due to network problems (MSLib).

-334  =Error getting confirmation during reconnectng. (MSLib).

334   =Error getting confirmation during reconnecting. (MSLib).

-335  =Timeout reconnecting (MSLib).

335   =Timeout reconnecting (MSLib).

-336 =No notification from Message Server (MSLib).

336  =No notification from Message Server (MSLib).

-337 =Exiting listener loop – restart the node (MSLib).

337  =Exiting listener loop – restart the node (MSLib).

-338 =Message is invalid – restart the node (MSLib).

338  =Message is invalid – restart the node (MSLib).

-339 =Client is not authorized to access the Message Server – restart the node (MSLib).

339  =Client is not authorized to access the Message Server – restart the node (MSLib).

-11111  =License expired (jlaunch will not restart the process).

-11112  =Shutdown command (jlaunch will not restart the process).

-11113  =Core service start fails when engine is starting or additional service starts fail and “HaltOnAdditionalServiceFailure=true” (Service Manager).

-11114  =Enqueue Server was restarted without restarting the AS Java. This could lead to data inconsistencies and requires a restart of the entire system (Locking Manager).

11114  =Enqueue Server was restarted without restarting the AS Java. This could lead to data inconsistencies and requires a restart of the entire system (Locking Manager).

-11116 =Cycle detected in the class loader references (Service Manager).

11115 =Services load timeout expired and “haltOnServiceTimeout=true” (Service Manager).

#Service Manager exit codes for version > 7.1 AP7.

2150=Core service start fails on initial startup.

2151=Additional service fails to start on initial startup and property ‘HaltOnAdditionalServiceFailure’ is true.

2152=Services startup timeout expires; try to increase services load timeout value ‘LoadTimeout’ property.

-2100=Cycle detected in the class loader references.

-2101=Missing manager; check kernel.properties

-2102=Cannot read component filters; check filters.txt.

-2103=Component filters are empty; check filters.txt.

-2104=Cycle detected in the hard reference dependences.

-2105=Core components missing or not loaded.

#The offline tools exit codes are as follows (last updated on 13-11-2006):

#1 – insufficient or invalid arguments – this exit code should be left for wrong arguments only.

2=Error while loading subsequent classes.

3=Unsupported VM on this platform.

10=Cannot initialize Configuration Manager or missing property file (offline deploy tool) or license already installed (likeyinst tool).

12=Error installing license (likeyinst tool).

13=Error connecting to external system (likeyinst tool).

64=Error reading bootstrap properties (bootstrap).

65=Error modifying DB (bootstrap).

66=Unknown startup mode or action (bootstrap).

#Bootstrap exitcodes:

66=Bootstrap exits with error code 66 in dev_bootstrap* log file.

500=Unknown exception. For more information, check the bootstrap logs and see SAP Note 915825.

501=Properties file found, but cannot be read. Check the file permissions. For more information, see SAP Note 915825.

502=Incorrect property value. For more information about the valid values, see SAP Note 915825.

503=Error while initializing the database connection. Check if the database is running. For more information, check the bootstrap logs and see SAP Note 915825.

504=Custom parameters mappings not found in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

505=Problem accessing the database. Make sure the database is running and check the database connection details. For more information, check the bootstrap logs and see SAP Note 915825.

506=Cannot access the synchronization root. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

507=Cannot access the synchronization root. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

508=Cannot access the version information in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

509=Cannot access the version information in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

510=Inconsistent bit length configuration. The JVM reports different bit length than the bit length of the Startup Framework. Check the installation consistency. For more information, see SAP Note 915825.

511=Problem accessing the instance meta data. Check the database settings. For more information, check the bootstrap logs and see SAP Note 915825.

512=Problem accessing the instance meta data. Check the database settings. For more information, check the bootstrap logs and seeSAP Note 915825.

513=Problem accessing the instance meta data. Check the database settings. For more information, check the bootstrap logs and see SAP Note 915825.

514=Problem accessing the file system entry j2ee/os_libs. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

515=Cannot find information about the native files. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

516=Cannot find information about the native files. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

517=Error while reading index information from the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

518=Error while reading index information from the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

519=Error while reading index information from the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

520=Error while reading index information from the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

521=Error while reading index information from the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.

522=Cannot access the file system index file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

523=Cannot access the file system index file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

524=Problem accessing the cluster file system global version. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825.

525=Problem accessing the cluster file system global version. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825.

526=Problem accessing the cluster file system global version. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825.

527=Problem accessing the versions repository of the cluster file system. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825.

528=Problem accessing the versions repository of the cluster file system. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825.

529=Problem accessing the meta data of the cluster file system. Check the database state and the Deploy Controller component version. For more information, check the bootstrap logs and see SAP Note 915825.

530=Problem accessing the meta data of the cluster file system. Check the database state and the Deploy Controller component version. For more information, check the bootstrap logs and see SAP Note 915825.

531=Index not found in the file system. Check the file system consistency. For more information, check the bootstrap logs and see SAP Note 915825.

532=Index not found in the database. Check the database consistency and the version of the OfflineDeploy component. For more information, check the bootstrap logs and see SAP Note 915825.

533=Error while synchronizing the files in j2ee/cluster/bootstrap. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

534=Error while synchronizing the files in j2ee/cluster/bootstrap. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

535=Error while synchronizing the files in j2ee/cluster/bootstrap. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

536=Error while synchronizing the files in j2ee/cluster/bootstrap. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

537=Error while synchronizing the files in j2ee/oslibs. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

538=Error while updating the j2ee/cluster/instance.properties file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

539=Error while synchronizing the server files in j2ee/cluster/server<n>/dtd. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

540=Error while synchronizing the server files in j2ee/cluster/server<n>. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

541=Index not found in the file system. Check the file system consistency. For more information, check the bootstrap logs and see SAP Note 915825.

542=Index not found in the database. Check the database consistency and the version of the OfflineDeploy component. For more information, check the bootstrap logs and see SAP Note 915825.

543=Error while synchronizing the AS Java binaries. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

544=Error while writing the j2ee/cluster/version.bin file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

545=Current VM type is not supported according to the specified compatibility list. For more information, check the bootstrap logs and see SAP Note 915825.

546=Problem reading kernel properties from the DB. For more information, check the bootstrap logs and see SAP Note 915825.

547=Problem writing cluster/kernelProperties.bin file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

548=Problem reading the managers’ properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825.

549=Problem reading the managers’ properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825.

550=Problem reading the services’ properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825.

551=Problem reading the services’ properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825.

552=Problem writing cluster/servicesProperties.bin or or cluster/kernelProperties.bin file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

553=Native file not found in the DB, but present in the descriptor. For more information, check the bootstrap logs and see SAP Note 915825.

554=Invalid value for the AS Java startup mode. For more information, check the bootstrap logs and see SAP Note 915825.

555=Invalid value for the AS Java startup action. For more information, check the bootstrap logs and see SAP Note 915825.

Activating the Emergency User in Java only system

Why SAP* user activation required

Sometime we end up in a situation when none of the user are able to log in into SAP or even Administrator user is locked or not working. In this scenario you have to activate the emergency user SAP*.

Please note: This method is only for Java Only system, for dual stack systems you can activate SAP* or lock unlock user via SU01. (Will provide a link shortly to unlock SAP* in ABAP stack).

Once SAP* is activated all other users will be deactivated until SAP* is disabled again.

How to activate SAP*

1. Launch Configtool – Go to to /usr/sap/<SID>/JC*/j2ee/configtool/ and execute configtool.sh (On UNIX like environment, please setup DISPLAY as per X11 /Reflection application).
2. Go to Global Server Config > Services > com.sap.security.core.ume.services node.
3. Change the following UME parameters.

   

4.Select the property and enter the Value as shown in step 3 and save it by pressing “Set” button.

5.SAP* will get activated after Java restart.

6.Now you can log in with SAP* and unlock Administrator or any other desired user.

7.After step 6 deactivate SAP*.

Reset locked SDM Password

The SDM password allows 3 logon attempts waiting for the correct password. Unfortunately if it is locked we cannot unlock the SDM password rather we would have to reset it. The below is the method to reset the SDM password. Logon to the Application server as <sid>adm

For Windows OS:

Open a command prompt and navigate to the folder <Drive>:usrsap[SID]JC[sys-nr]SDMprogram such as D:usrsapDVJJC51SDMprogram

Execute the below commands:
StopServer.bat
sdm jstartup “mode=standalone”
sdm changepassword “newpassword=<Enterthenewpassword>”
sdm jstartup “mode=integrated”
StartServer.bat

For Unix OS:

Open a Telnet window and navigate to the folder /usr/sap/[SID]/JC[sys-nr]/SDM/program such as /usr/sap/DVJ/JC51/SDM/program

Execute the below commands:

./StopServer.sh
./sdm.sh jstartup “mode=standalone”
./sdm.sh changepassword “newpassword=<Enterthenewpassword>”
./sdm.sh jstartup “mode=integrated”
./StartServer.sh

Post processing (for Unix or Windows):

You must change the password in the config tool. If you forget that step, you will not be able to deploy using SDM. SAP note 701654 explains the process:

Use the Config Tool to change the entry in secure storage as follows:

(Execute <SAPj2eeEngine_install_dir> configtoolconfigtool.bat.)

secure store

The configuration for the secure storage in the file system appears.

admin/password/<SID> (enter the password for J2EE_ADM_[SID], not the SDM password)

click on the SAVE button.

Note: Contrary to the message that appears, you do not need to restart the server or cluster for this change to take effect