Home > Symantec Endpoint > Symantec Endpoint Protection Error 12029

Symantec Endpoint Protection Error 12029

The Home, Monitors, and Reports pages display an HTTP error. Network issues include the firewall blocking access, or networks not connecting to each other. Check for any network problems Verify that there are no network problems by checking the following items: Test the connectivity between the client and management server first. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. http://allconverter.net/symantec-endpoint/symantec-endpoint-protection-error.html

The management server service does not stay in a started state. When you modify the Windows Registry, the management server generates the logs (ersecreg.log and exsecars.log). Test the ODBC connection. If you do it make sure to start all the stopped services again.

Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Go to HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings\connections 3. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. This password is the one that you entered for the database when you installed the management server.

Error In the Sylink log, between check point 4 and 5.1, following symptoms identified: 08/05 18:14:42 [2564] http://SEPM_SERVER:8014 [encrypted data] 08/05 18:14:42 [2564] 18:14:42=>Send HTTP REQUEST 08/05 18:14:45 [2640] Manually assigned Thank you for your feedback! Look for a client computer's IP address or host name which indicates that the clients connect to the Apache HTTP server. 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).

Try these resources. Use the ping command to test the connectivity to the management server On the client computer, open a command prompt. No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 Products Products Home Threat Protection Advanced Threat Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support

Also bind 127.0.0.1 with HTTP 1. 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 Submit a Threat Submit a suspected infected fileto Symantec. To check connection status data values in the client: In the SEP client, click the Help button, and then clickTroubleshooting.

You can type an optional description. In the ODBC tab, click Test Connection. Note: These registry keys will automatically regenerate after reboot of machine. You should also check network connectivity.

In the Database tab, in the Server name field, type <\\servername\instancename>. weblink Note: Disable the log after you view it because the log uses unnecessary CPU resources and hard disk space. logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 logo-symantec-dark-source Loading Your Community Experience Symantec Connect

Click Test Data Source. Create a SymAccount now!' Symantec Endpoint Protection clients do not communicate with the Symantec Endpoint Protection Manager (SEPM) TECH137402 December 30th, 2010 http://www.symantec.com/docs/TECH137402 Support / Symantec Endpoint Protection clients do not You can view these logs to troubleshoot client and server communication. http://allconverter.net/symantec-endpoint/symantec-endpoint-protection-error-1310.html If you use the English version of Symantec Endpoint Protection Manager, use the default sem5.

Previous Client communication settings not getting removed from the Client computer Solution To fix "An error occurred while copying the socket address: 80 Socket Address: [2002:9ea3:5d43 size: 28" In order to Open the registry (Start->Run->type "regedit"). 2. All of these issues display a Java -1 error in the Windows Event log.

Troubleshoot management server and client communications If you have trouble with client and server communication, check to ensure that there are no network problems.

The Home, Monitors, and Reports pages display a continuously loading progress bar, without displaying any content. 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. The Home, Monitors, and Reports pages are blank. If you use the tool on the command line, read the SylinkDrop.txt file for a list of the tool's command parameters.

Click Next. Check that the Symantec Endpoint Protection firewall or third-party firewall does not cause any network problems. Verify that the network connection between management server and the SQL database is correct. his comment is here 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.

Verify that the test succeeds. Click Next. In the Windows Registry, turn on debugging in the client under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\smc_debuglog_on. Click Login.

The default heap size for Symantec Endpoint Protection Manager is 256 MB.