Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

SEP 12.1 clients not updating

Created: 13 Feb 2012 | 7 comments
scasperson's picture
0 0 Votes
Login to vote

Hi

I have a number of clients that are connected to a Symantec Endpoint Protection Manager that are not downloading updates from the server. The error message that I am getting is:

Downloaded new content update from the management server failed. 

 
Remote file path: http://192.0.1.22:8014/content/{55DE35DC-862A-44c9-8A2B-3EF451665D0A}/120211002/xdelta120210002.dax
 
If i navigate to the link, I can download the file. Also if I perform a manual update from the internet, I am able to update the client without any problems.
 
This does not happen on all clients, just a few.
 
Also, at another site, I am having similar problems, however the difference with those machines are is that they are configured to download updates directly from the internet. These machines are configured to use a local proxy server that does not need any authentication. Again, if I do a manual update, it works ok. No entry in the logs refering to any updates attempted or failures. This does not affect all machines, just a few.
 
Any ideas?
 
Thanks,
Sam.

Comments

Ashish Sharma's picture
14
Feb
2012
0 Votes 0
Login to vote

If they are then, you may

If they are then, you may have to work on these articles below:

Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting

http://www.symantec.com/docs/TECH160964

Symantec Endpoint Protection: LiveUpdate Troubleshooting Flowchart

http://www.symantec.com/docs/TECH95790

Thanks In Advance...

Ashish Sharma

 

If the suggestion has helped to solve your problem, please mark the post as a solution

 

 

 

pete_4u2002's picture
14
Feb
2012
1 Vote +1
Login to vote
scasperson's picture
14
Feb
2012
0 Votes 0
Login to vote

I have attached the sylink

I have attached the sylink log files from two clients that are experiencing problems.

 

The file 'Client non proxy updates from server' is the client that has the error

 

Downloaded new content update from the management server failed. 

 
Remote file path: http://192.0.1.22:8014/content/{55DE35DC-862A-44c9-8A2B-3EF451665D0A}/120211002/xdelta120210002.dax
 
This machine is configured to download updates from the management server which is on the local network.
 
The other log file 'Client Proxy updates from internet' is the one configured to download the updates directly from the internet. This machine has been configured from the management server to connect via a proxy server without authentication. This does not have any errors in the logs, nor does it have any messages where it attempts to update.
 
Again, both machines will update if done manually using live update.
 
I have not gone though the troubleshooting steps stated above, but will start now.
 
Thanks,
Sam.
AttachmentSize
Client non proxy updates from server- sylink.txt 206.93 KB
Client Proxy updates from internet - sylink.txt 116.59 KB
pete_4u2002's picture
15
Feb
2012
0 Votes 0
Login to vote

from the client log which is

from the client log which is not updated, it is in process for downloading the ddefinition.

didn't the client update?

can you collect for longer time?

Nazar E Noor's picture
15
Feb
2012
0 Votes 0
Login to vote

Hi,   Can you please check

Hi,

 

Can you please check your proxy configuration its block any limitation

or

check your network firwall also.

scasperson's picture
15
Feb
2012
0 Votes 0
Login to vote

New sylink file

 

Thanks for the help so far.

I have attached a new sylink file from the server that isn’t downloading updates from the management server. 

On this particular machine, the firewall is disabled, and allowing all communication through. I have also explicitly defined in the live update policy to not go through a proxy, and connect directly to the server. I can navigate to the zip file that it is trying to download it using ie and it can download just fine. Most other clients don’t seem to have an issue in downloading the updates either.

In regards to the clients which are downloading their updates from the internet, the machine that I was collecting logs for decided to start working. I am currently collecting logs from another machine that is experiencing the same issue. This machine does not have a firewall enabled (the rules are set to allow everything), and it is configured to go through a proxy. This machine is using the same proxy as other clients which do not have issues in updating. Its dns and gateway setting are the same as other funtioning clients too. 

I am currently collecing sylink logs for this machine now. Maybe by the process of observing it in action will cause it to behave differently and work. 

 

Many Thanks,

Sam.

AttachmentSize
Clent Non Proxy Updates from Server.txt 3.38 MB
scasperson's picture
16
Feb
2012
0 Votes 0
Login to vote

Having some success

I think some of my misbehaving clients are bound to the Heisenberg uncertainty principle. As soon as I start collecting logs, they start to work. However they are only the clients which download updates from the internet and not the management server. I will go though these clients one by one and get them to start logging and they should come in line.

 

However not eveything is so rosy. Some of my clients that are getting updates from the management server are still failing with the errors stated above. Again, most clients are working fine, just some of them fail to update.