Error: "Failed to connect to the server, Verify that server name and port are correct". Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Verify that the network connection between management server and the SQL database is correct. You should also check network connectivity. have a peek at this web-site
Type the following command: 32-bit operating system: %systemroot%\system32\odbcad32.exe 64-bit operating system: %systemroot%\syswow64\odbcad32.exe In the ODBC Data Source Administrator dialog box, click System DSN. Don't have a SymAccount? Click "Go." The download page will appear. Click OK.
Click Next. Note:Java7is supported from SEP 12.1 RU2 onwards. The correct Java version will be installed.
For Login ID, type sa. Thank you for your feedback! When you modify the Windows Registry, the management server generates the logs (ersecreg.log and exsecars.log). Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.
Try to start the Symantec Endpoint Protection Manager service in Service Control Manager. Check that the Symantec Endpoint Protection firewall or third-party firewall does not cause any network problems. Look on the client to see if the client connects to the management server You can check several important connection data values in the client. The SEPM console itself cannot connect to the Database.
If the client connects, the client's connection problem is probably not a network issue. No Yes Products Products Home Threat Protection Advanced Threat Protection Endpoint Protection Endpoint Protection Cloud IT Management Suite Email Security.cloud Data Center Security Blue Coat Products Information Protection Data Loss Prevention Try these resources. Test the ODBC connection.
Try these resources. To view the Apache HTTP server Access log: On the management server, open C:\Program Files\Symantec\Symantec Endpoint Protection Manager\apache\logs\access.log. Instead, an earlier version of Java is installed. Solution Disable or remove incompatible versions of Java.
In the left pane, click Debug Logs. http://netlookmag.com/symantec-endpoint/symantec-endpoint-protection-error-0x80070005.html Look for a client computer's IP address or host name which indicates that the clients connect to the Apache HTTP server. Disable or Remove Incompatible Versions of Java There are two methods of dealing with incompatible versions of Java. In the System DSN tab, double-click SymantecEndpointSecurityDSN.
No Yes Products Products Home Threat Protection Advanced Threat Protection Endpoint Protection Endpoint Protection Cloud IT Management Suite Email Security.cloud Data Center Security Blue Coat Products Information Protection Data Loss Prevention The command should return the server's correct IP address. Click "Yes" when asked if you are sure you want to remove Java. Source Try these resources.
Install Java 6 Update 14 Method 1: Download the latest Java 6 update 14 from the Symantec Endpoint Protection Manager's remote console website. Check that the management server heap size is correct You may need to adjust the heap size that is appropriate for the management server's operating system. If you get a Java security error that says "Block potentially unsafe components from being run?" click "No".
If not, reference the following document for further troubleshooting: http://www.symantec.com/business/support/index?page=content&id=TECH102413&locale=en_US References "Which communication ports does the Symantec Endpoint Protection Manager 11.x use?" http://www.symantec.com/business/support/index?page=content&id=TECH102416&locale=en_US This document is available in the following Submit a Threat Submit a suspected infected fileto Symantec. Click the "Download JRE" link. Repeat steps 3-5 if multiple incompatible versions are installed.
Click OK. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Ensure that sem5 is selected for the default database. have a peek here Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.
The correct version of Java is 1.7.9. The name entered into the console is not able to be resolved to the correct computer. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation Why is logging into Symantec Endpoint Protection Manager producing the error: Make sure all boxes are checked, and click OK.
The scm-server log is typically located at C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-0.log. Open an internet browser. Click OK to close the dialog boxes. The Java Control Panel will appear.
Click Next. Close Login Didn't find the article you were looking for? Submit a Threat Submit a suspected infected fileto Symantec. If the client computer cannot ping or Telnet to the management server, verify the DNS service for the client.