Home > Symantec Endpoint > Symantec Endpoint Protection Error 12029

Symantec Endpoint Protection Error 12029

Ensure that sem5 is selected for the default database. Solution The legacy proxy settings can be removed by performing the following steps: 1. Submit a Threat Submit a suspected infected fileto Symantec. Thank you for your feedback! http://mmonoplayer.com/symantec-endpoint/symantec-endpoint-protection-error-1719.html

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. 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 Submit a Threat Submit a suspected infected fileto Symantec. Test the ODBC connection.

Check the client's routing path. In the System DSN tab, double-click SymantecEndpointSecurityDSN. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. 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.

Thank you for your feedback! 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. To check connection status data values in the client: In the SEP client, click the Help button, and then clickTroubleshooting. Then expand the network adapters and disable “Microsoft 6to4 adapter”.

View the connection status data values. Click Test Data Source. You can run the tool remotely or save it and then run it on the client computer. Note: Ensure that the Computer Browser Service is running on the server.

To check the inbox logs on the management server: On the management server, under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SEPM, set DebugLevel=3. In the Login tab, in the User ID field, type dba. In the Database tab, in the Server name field, type <\\servername\instancename>. Open the registry (Start->Run->type "regedit"). 2.

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. These channels include, server to client, server to database, and server and client to the content delivery component, such as LiveUpdate. Look for a client computer's IP address or host name which indicates that the clients connect to the Apache HTTP server. Check that the management server does not have a network problem.

Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. check over here If you do it make sure to start all the stopped services again. If the client computer cannot ping or Telnet to the management server, verify the DNS service for the client. Point 4 is really necessary.

Don't have a SymAccount? To verify ODBC connection to the SQL database: Click Start > Run. Provide feedback on this article Request Assistance Print Article Products Related Articles Subscribe to this Article Manage your Subscriptions Search Again Situation After uninstalling and reinstalling of SEPM with a fresh http://mmonoplayer.com/symantec-endpoint/symantec-endpoint-protection-error-code-6.html Click Finish.

Click Yes to restart the SEPM service. You can test the communication between the client and the management server in several ways. Check system requirements Ensure that both the client and the management server meet the minimum or recommended system requirements.

Close Login Didn't find the article you were looking for?

Click Next. You can view these logs to troubleshoot client and server communication. Solution The communication channels between all of the Symantec Endpoint Protection components must be open. Click on View menu and select Show hidden devices 3.

Reboot the machine. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. The Home, Monitors, and Reports pages display an HTTP error. weblink PHP checks for a global configuration file (php.ini).

In the Password field, type the password for the database. Close Login Didn't find the article you were looking for? Don't have a SymAccount? Network issues include the firewall blocking access, or networks not connecting to each other.

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. Try these resources. Look for the result that states "TESTS COMPLETED SUCCESSFULLY!". 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

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 Enable and view the Access log to check whether the client connects to the management server You can view the Apache HTTP server Access log on the management server to check Click Next. Type netsh http add iplisten ipaddress=127.0.0.1 3, Select YES 4.

Click Login. This file usually appears in \Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\log.