Delete the contents of the Downloads folder, and then run LiveUpdate again. The following are typical invalid entries: 127.0.0.1 www.symantec.com 127.0.0.1 securityresponse.symantec.com 127.0.0.1 symantec.com 127.0.0.1 liveupdate.symantecliveupdate.com All such entries should be removed. If Windows 98 was updated from Windows 95, the location is C:\Windows\Application Data\Symantec\LiveUpdate. Set TcpTimedWaitDelay to a decimal value of 30. Source
Click View Log. Close Login Didn't find the article you were looking for? Windows NT: Go to the Winnt\Profiles\All Users\Application Data\Symantec\LiveUpdate folder. Verify that the test succeeds. https://www.symantec.com/connect/forums/live-update-cannot-connect-host
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 Otherwise, leave Server name blank. In the Windows Registry, turn on debugging in the client under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\smc_debuglog_on. Don't have a SymAccount?
Click OK. 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 Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. The settings for LiveUpdate to connect to the Internet are incorrect By default, LiveUpdate uses the Internet options in the Windows Control Panel.
Look for the result that states "TESTS COMPLETED SUCCESSFULLY!". Submit a False Positive Report a suspected erroneous detection (false positive).
Click Next. Click Login. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation After you start LiveUpdate, you see the message "LU1814: LiveUpdate could Use a browser to test the connectivity to the management server on the client computer On the client computer, open a web browser.
In the Database tab, in the Server name field, type <\\servername\instancename>. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation At random intervals, the process or scanengine log of Symantec Protection 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). To fix the problem, install LiveUpdate again.
For directions, read How to make Windows show all files. this contact form Check system requirements Ensure that both the client and the management server meet the minimum or recommended system requirements. Test the ODBC connection. The connection will be terminated after the timeout value has been reached if the connection is not approved by an end-user who is logged in.
Check the debug logs on the client computer You can check the debug log on the client computer. If this file is present and the necessary settings are not in the Settings.LiveUpdate file, LiveUpdate fails to connect and shows the LU1814 error. Try these resources. have a peek here 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.
This article describes how to troubleshoot communication issues. All of these issues display a Java -1 error in the Windows Event log. 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. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription.
Test database and management server connectivity If the management server runs the embedded Sybase database, perform the following steps: Verify that the Symantec Embedded Database service runs, and that the dbsrv11.exe Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. To find the specific cause for the Java -1 error, look in the scm-server log. Close Login Didn't find the article you were looking for?
Submit a Threat Submit a suspected infected fileto Symantec. Delete all copies of the Settings.LiveUpdate file, and then run LiveUpdate again. Don't have a SymAccount? You can run the tool remotely or save it and then run it on the client computer.
Possible error: LU1835: Connection to the LiveUpdate server failed. Exit Windows Explorer. Do not delete the Downloads folder itself. If the client has communication problems with the management server, status messages about the connection problem appear in the logs.
Open the Downloads folder. The client is not configured correctly to connect to the internal LiveUpdate server.