Error Messages While Connecting to the
Standalone Log Viewer Server
Problem Description
The Standalone Log Viewer client cannot connect the user to the Standalone Log Viewer server. The test of the connection (File ® Configuration ® Test connection) is not successful.
|
Scenario Type: |
Error analysis |
|
NetWeaver Component: |
J2EE Engine |
|
Validity: |
J2EE Engine 6.40 and higher |
Possible Error Sources
Error Message |
Analysis |
Unable to connect to standalone Logviewer server on <host>:<port>. Please make sure the server is started on that machine and port. |
● Invalid connection parameters ● The Standalone Log Viewer server is not running on the host |
Error… |
● The version/patch level of the Standalone Log Viewer client and the Standalone Log Viewer server are not compatible ● The JRE version that is used for the Standalone Log Viewer server is different from the JRE version that is used for the Standalone Log Viewer client |
Decision Roadmap
Prerequisites
If you have an SAP Web Application Server Java (SAP Web AS Java) 6.20 or lower, you may download the standalone_logviewer.zip file on SAP Service Marketplace at service.sap.com/swdc ® Download ® Support Packages and Patches ® Entry by Application Group ® Additional Components ® Java Log Viewer ® SAP Java Log Viewer 6.30 ® #OS independent. In this case JDK version 1.3.11 or higher but lower than 1.4 must be installed on the system. The Java version must be same on the server and on the client.
If you have an SAP Web AS Java 6.30 or higher, you can find the Standalone Log Viewer installation in the following directory: on Microsoft Windows: <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\admin\logviewer_standalone and on UNIX: /usr/sap/<SID>/<Instance name>/j2ee/admin/logviewer_standalone. Make sure that the logviewer script file is in this directory.
Main Tools
Standalone Log Viewer
Execution
...
1. To start the Standalone Log Viewer client, on Microsoft Windows, go to the <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\admin\logviewer_standalone directory and run the logviewer.bat file.
2. Choose File ® Configuration.
3. If you want to connect to a server to which a connection has already been configured, select the name of the server.
4. If you want to configure a new connection to a server, choose Add and enter the server details.
5. To test the connection to the server before you save the configuration, choose Test Connection.
Analysis
If you receive the following message after the test of the connection, continue with step 1 below:
1. Invalid connection parameters
Make sure that you have entered the correct host name/port number and user/password.
By default, the Standalone Log Viewer server is listening for new logs on port 1099.
If the port is in use, in the <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\admin\logviewer-standalone\server\LogViewerServer.properties file, change the port in the Logviewer_java.naming.provider.url property.
Test the connection again.
To check whether the port is in use, in the command line, execute the following commands: on Microsoft Windows: netstat –a | findstr 1099, and on UNIX: netstat –a | grep 1099. If the port is in use, a line with state LISTENING is returned.
If the test of the connection is not successful, continue with step 2.
2. The Standalone Log Viewer server is not running
If you do not have the Standalone Log Viewer server running as a service, to start the server manually, go to the <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\admin\logviewer-standalone directory and run the remoteserver.bat file. If the ToolLauncher screen appears with the following message, the server is started:
Starting registry on port 1099.
Server started.
Test the connection as described above. If the test of the connection is successful, you receive the following message:
For more
information about running the Standalone Log Viewer server as a service on
Microsoft Windows, see
Installing the Log
Viewer as a Service.
To check the status of the service, on Microsoft Windows choose My Computer ® Manage ® Services and Applications ® Services. If the service is not running, try to start the service again. You may consider setting the startup type of the service to Automatic so that it is started automatically at logon time. After starting the service, test the connection as described above.
The Standalone Log Viewer server runs at the customer side, it is configured to listen on an NI socket connection. The Standalone Log Viewer client usually runs at SAP support and tries to connect to the server via an NI socket connection. This connection is usually made via an SAP router that allows connections through corporate firewalls. If you are connecting through the NI socket connection, run the remoteserver.batfile on your remote machine.
3. The version/patch level of the Standalone Log Viewer client and the Standalone Log Viewer server are not compatible
Make sure that the version/patch level of the Standalone Log Viewer server is lower or equal to the version/patch level of the Standalone Log Viewer client. To check the version/patch level on the client side, choose Help ® About.
To check the version on the server side, check the LogViewerServer.properties file.
If you do not have this file, you have an old version of the Standalone Log Viewer server and you must update it. The test of the connection may be successful, but you cannot work with the Standalone Log Viewer client. Continue with step 4.
4. The JRE version that is used for the Standalone Log Viewer server is different from the JRE version that is used for the Standalone Log Viewer client
You receive the following incomplete error message:
Error…
Make sure that you use the same JRE version for the Standalone Log Viewer server:
and the Standalone Log Viewer client:
If you want to run the Standalone Log Viewer as a service on Microsoft Windows, we recommend that you install JDK version 1.4.2 or higher.
Additional Information