If you use the tool on the command line, read the SylinkDrop.txt file for a list of the tool's command parameters. Note: Disable the log after you view it because the log uses unnecessary CPU resources and hard disk space. View the connection status data values. You can use the server IP address in place of the computer name. http://rss4medics.com/connect-to/php-cannot-connect.php
If there are multiple configuration files, you must force each product to use its own interpreter. You can check the debug log by using the following methods: In the SEP client, click the Help button, and then click Troubleshooting. Verify that the network can properly resolve the name of the computer running the Database if it is not hosted on the SEPM server. Click Test Data Source. https://www.symantec.com/connect/forums/i-cant-login-symantec-endpoint-protection-manager-121
Click Database. Recover lost client communication by using the SylinkDrop tool From the installation files, go to the \Tools\NoSupport\SylinkDrop folder, and run SylinkDrop.exe. Thank you for your feedback!
You can test the communication between the client and the management server in several ways. Symantec Endpoint Protection Manager Failed To Connect To The Server Make Sure In the browser command line, type the following command, where management_server_address is the management server's DNS name, NetBios name, or IP address: http://management_server_address:8014/secars/secars.dll?hello,secars When the Web page appears, look for one Click Next. When each product uses the correct version of PHP associated with it, the management server operates properly.
Submit a False Positive Report a suspected erroneous detection (false positive). However, for compatibility with 1.6, the SEPM must be RU6 or later. The Home, Monitors, and Reports pages display a continuously loading progress bar, without displaying any content. Note: Ensure that the Computer Browser Service is running on the server.
Troubleshoot management server and client communications If you have trouble with client and server communication, check to ensure that there are no network problems. check it out In the SEPM, export the communication file (sylink.xml) from the client group to which you want the client computer to connect. Sepm Failed To Connect To The Server Submit a Threat Submit a suspected infected fileto Symantec. Symantec Endpoint Protection Manager Service Not Starting Deploy the communication file to the client computer: An additional option in SEP 12.1.2 (RU2) and later is the Communication Update Package Deployment.
If the ping command does not return the correct address, verify the DNS service for the client and check its routing path. this page Check that the management server does not have a network problem. In the ODBC tab, verify that the Data source name drop-down list is SymantecEndpointSecurityDSN. Remove the hash mark (#) from the following text string, and then save the file: #CustomLog "logs/access.log" combined Using services.msc, restart the Symantec Endpoint Protection Manager Webserver service (Apache). Failed To Contact Symantec Endpoint Protection Linux
If not, fix the name resolution issues on the network or enter in the manager IP address instead. Did this article resolve your issue? If the word OK does not appear, the client computer cannot connect to the management server; the problem is likely at the server's end. get redirected here TECH102769 August 2nd, 2013 http://www.symantec.com/docs/TECH102769 Support / Unable to Logon to Symantec Endpoint Protection Manager.
You can run the tool remotely or save it and then run it on the client computer. Solution The communication channels between all of the Symantec Endpoint Protection components must be open. 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.
Try to start the Symantec Endpoint Protection Manager service in Service Control Manager. To check connection status data values in the client: In the SEP client, click the Help button, and then clickTroubleshooting. Click Login. Check the inbox logs on the management server You can use a Windows Registry key to generate logs about activity in the management server inbox.
Close Login Didn't find the article you were looking for? The SEPM console itself cannot connect to the Database. This article describes how to troubleshoot communication issues. useful reference The management server service does not stay in a started state.
Java version 1.4 and earlier are not supported and will need to be upgraded. Troubleshoot management server and console or database communications If you have a connection problem with the console or the database, you may see one of the following symptoms: The management server Open the log file. Type ping and the computer name of the management server, and then press Enter.
In the Database tab, in the Server name field, type <\\servername\instancename>. Network issues include the firewall blocking access, or networks not connecting to each other. In the left pane, click Debug Logs. The Home, Monitors, and Reports pages are blank.
Provide feedback on this article Request Assistance Print Article Products Related Articles Subscribe to this Article Manage your Subscriptions Search Again Situation Symantec Endpoint Protection Manager (SEPM) 12.1 is logging errors You should also check network connectivity. Don't have a SymAccount? If the management server runs the remote SQL database, perform the following actions: Verify that you have specified a named instance when you installed and configured Symantec Endpoint Protection Manager.
In the Password field, type the password for the database. The command should return the server's correct IP address. Create a SymAccount now!' Troubleshoot communication issues with Endpoint Protection Manager 12.1 TECH160964 May 30th, 2016 http://www.symantec.com/docs/TECH160964 Support / Troubleshoot communication issues with Endpoint Protection Manager 12.1 Did this article resolve To find the specific cause for the Java -1 error, look in the scm-server log.
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. In the Password field, type the password for the database. Error: "Failed to connect to the server, Verify that server name and port are correct". 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.