Table of Contents
Advertisement
Troubleshooting communication problems between the management server and the console or the database
Verifying the connection with the database
The Home, Monitors, and Reports pages display an HTTP error.
The Home, Monitors, and Reports pages are blank.
The Home, Monitors, and Reports pages display a continuously loading progress
bar, without displaying any content.
All of these issues display a Java -1 error in the Windows Event log. To find the
specific cause for the Java -1 error, look in the scm-server log. The scm-server log
is typically located in the following location:
C:\Program Files\Symantec\Symantec Endpoint Protection
Manager\tomcat\logs\scm-server-0.log
Checking the communication with the console or database
Table 24-3
What to check
Test the connectivity
between the database and
the management server.
Check that the management
server heap size is correct.
Check the system
requirements.
The management server and the database may not communicate properly. You
should verify that the database runs and then test the connection between the
server and the database.
Perform the following steps:
Verify that the Symantec Embedded Database service runs and that the
dbsrv9.exe process listens to TCP port 2638.
Test the ODBC connection.
Troubleshooting installation and communication problems
Description
You can verify that the management server and the database
communicate properly.
See
Verifying the connection with the database"
You may need to adjust the heap size that is appropriate for
the management server's operating system. If you cannot
log in to the management server's remote console, or if you
see an out-of-memory message in the smc-server log, you
may need to increase the heap size. The default heap size for
Symantec Endpoint Protection Manager is 256 MB.
You can check whether both the client and the management
server run the minimum or recommended system
requirements.
See
System requirements"
on page 323.
on page 41.
323
Advertisement
Table of Contents
Troubleshooting
