Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 4952 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

We have a strange thing going on here 00000071 ERROR: Could not find a source for updated packages

Rene-T

Hello all,

on a large part of our clients we can see this behaviour  (several 100's of about 4500+ clients)

10/5/2010 6:51:25 PM 00000071  ERROR: Could not find a source for updated packages
10/5/2010 12:30:06 PM 00000000  Updated successfully                    
 10/5/2010 11:30:08 AM 00000071  ERROR: Could not find a source for updated packages
  10/3/2010 1:20:44 PM  00000000  Updated successfully                    
   10/3/2010 12:27:48 PM 00000071  ERROR: Could not find a source for updated packages
   10/3/2010 8:42:38 AM 00000000  Updated successfully                   

The server is online all the time and can be reached from all locations.

This results in a lot of helpdesk tickets , user report a red cross on the programm icon.

Does anyone have an idea what this can be ?

Regards,

René

:5303


This thread was automatically locked due to age.
  • 0

    Hi Jak

    yes  theres a limit to the max message size

    regards

    rené

    :5343
  • 0

    Hello René,

    you can use, for example, http://pastebin.com/ 

    Christian

    :5344
  • 0

    Hi,

    That "failed" failed update looks like it found the CID ok and therefore wouldn't have generated error 00000071 back in SEC. The check for AutoUpdate completed ok and the SAV one looked like it was going ok as well before the logs were cut short.

    It's odd that from the logs in SEC it seems to toggle between working and not working, I assume this is a laptop that maybe moves around and can't always access the CID?  The references from SEC you include don't include this test update from the logs?  I assume that was ok in SEC though?

    If the client tries to update when the CID is not available, RMS will queue the failed attempt and then send it when the client comes back "online", is this happening?  Could it be that the failed message is appearing from the previous attempt before the next update succeeds and clears the alert?

    Jak

    :5358
  • 0

    If you have not tried this yet then go to the Sophos\Auto Update\cache\ folder and delete everything in it ( EVERYTHING)

    If it does not allow you to delete everything then I am willing to bet you have a locked file in the SAVXP subfolder.

    I would also be willing to bet you have upgraded to Internet Explorer 8 which can in (Random) fashion tie in with the Windows Indexing service and lock files.

    So try turning off that service and clearing the cache again then update.

    :5362
  • 0
    Hi, Thanks for you replys, the posted log really was laptop, i will request for a test laptop and will try this scenario. We also assigned a second CPU to this machine, it seemed to peak at 100% several minutes a day making the server slow responding (its a VM ) I will check review incomming helpdesk calls regarding Sophos and give you a feedback later this week. Another ting we see al lot is failing MSI , but i have to do more reseach on this on before i "scream for help here" :-) Regards, René
    :5367
Unfiltered HTML