Click Next. Step 2) LiveUpdate Installer Assumethe wrong LiveUpdate version is installed onthe system, locate the LiveUpdate installer shipped with your release of Symantec Endpoint Protection as per above. Type ping and the computer name of the management server, and then press Enter. Submit a False Positive Report a suspected erroneous detection (false positive).
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 Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Monitor the system for a few days to ensure that updates are downloaded and installed properly. TECH163079 March 28th, 2014 http://www.symantec.com/docs/TECH163079 Support / Liveupdate cannot connect to server - What IP-s (IP addresses) should be configured as Firewall and Proxy exceptions to enable LiveUpdate?
Failed or corrupted installation of LiveUpdate If LiveUpdate files are corrupted or missing, the LiveUpdate session may fail with this error message. For Login ID, type sa. Don't have a SymAccount? In the Windows Registry, turn on debugging in the client under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\smc_debuglog_on.
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. The Home, Monitors, and Reports pages display an HTTP error. 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. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription.
Use the ping command to test the connectivity to the management server On the client computer, open a command prompt. Don't have a SymAccount? 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 Check that the management server is not running multiple versions of PHP You can check whether the management server runs multiple software packages that use different versions of PHP.
Confirm that Windows is set to show all files. Close Login Didn't find the article you were looking for? For directions, read How to make Windows show all files. Click “Refresh” on the Console home page, if this is not the case.
Close Login Didn't find the article you were looking for? https://www.symantec.com/connect/forums/urls-default-symantec-liveupdate-server Thank you for your feedback! 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. You should also check network connectivity.
How to determine the server that LiveUpdate is attempting to connect to: 7/16/2014, 20:50:42 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/liveupdate_184.108.40.206_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads" How to tell this contact form Thank you for your feedback! Re-registering/Resetting Symantec Endpoint Protection Manager content with LiveUpdate The following steps should only be performed if troubleshooting steps indicate that the problem is due to Symantec Endpoint Protection Manager content not WARNING: Do not delete the entire Symantec\LiveUpdate folder or the Product.Catalog.LiveUpdate file.
Submit a False Positive Report a suspected erroneous detection (false positive).
Do one of the following, depending on your version of Windows: Windows 2003/XP/2000: Go to the Documents and Settings\All Users\Application Data\Symantec\LiveUpdate folder. No Yes When you start LiveUpdate manually from the Symantec AntiVirus user interface, the LiveUpdate session uses the active user account.
A LiveUpdate session that is scheduled through the Symantec System Center or scheduled through the User Interface of Symantec AntiVirus uses the System account. This problem happens when the client cannot connect to the specified host. Exit Windows Explorer. Check that the management server does not have a network problem.
If you use the tool on the command line, read the SylinkDrop.txt file for a list of the tool's command parameters. File may be saved as .zip, please rename the file to .jdb when the download is complete. 2) LiveUpdate Installer shipped withthe release of Symantec Endpoint Protection in use. If Windows 98 was updated from Windows 95, the location is C:\Windows\Application Data\Symantec\LiveUpdate. Check This Out The Settings.LiveUpdate file is corrupted This problem can happen when the Settings.LiveUpdate file becomes corrupted.
In the ODBC tab, click Test Connection. Close Login Didn't find the article you were looking for? In most cases, Autoupdt.trg and Livetri.zip files are present. The issue causing the updateissue may be resolved by the improved processing and enhanced features available in a software version later than what is running.
These channels include, server to client, server to database, and server and client to the content delivery component, such as LiveUpdate. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. This requires that the SEPM have internet access. Technical InformationBy default, LiveUpdate is set to Express Mode for SEP clients.
Click Start > Run Enter the following command including the quotes:"C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\LuCatalog.exe" -cleanup This command will unregister all Symantec Endpoint Protection Manager content from LiveUpdate. This functionality is now included in the LiveUpdate client; hence this file is no longer needed. Verify that the network connection between management server and the SQL database is correct.