Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 4652 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.
Parents
  • 0

    Hello again,

    Can we check the line in a iconn.fg file from a failing client:
    \program files\sophos\AutoUpdate\Config\iconn.cfg

    Or

    \program data\sophos\AutoUpdate\Config\iconn.cfg (if on Vista +)

    In the Primary update section it should have a line such as:

    ConnectionAddress = \\[server]\SophosUpdate\CIDs\S[XXX]\SAVSCFXP\

    If you check in the “Bootstrap location” menu in SEC, can you find the path and its correspond subscription is this correct? 

    The S number is most important.  Does a machine in the same group and therefore have the same updating policy that is working, have exactly the same line in it?

    If you check the updating policy for the group this failing machine is in, does the machine say it’’’’s complies with the updating policy and in the policy, under the "Subscription" tab is the correct subscription chosen and this shows the expected version of SAV below?

    I'm starting to think this is most likely due to a mismatch of subscription ids and the clients that are failing are pointing to a S number that doesn't exist on the update location.  The client is probably pointing at the right server, but the S value is incorrect for the subscription.  The fact you have multiple SUMs makes this more likely.

    Thanks

    Jak

    :5326
Reply
  • 0

    Hello again,

    Can we check the line in a iconn.fg file from a failing client:
    \program files\sophos\AutoUpdate\Config\iconn.cfg

    Or

    \program data\sophos\AutoUpdate\Config\iconn.cfg (if on Vista +)

    In the Primary update section it should have a line such as:

    ConnectionAddress = \\[server]\SophosUpdate\CIDs\S[XXX]\SAVSCFXP\

    If you check in the “Bootstrap location” menu in SEC, can you find the path and its correspond subscription is this correct? 

    The S number is most important.  Does a machine in the same group and therefore have the same updating policy that is working, have exactly the same line in it?

    If you check the updating policy for the group this failing machine is in, does the machine say it’’’’s complies with the updating policy and in the policy, under the "Subscription" tab is the correct subscription chosen and this shows the expected version of SAV below?

    I'm starting to think this is most likely due to a mismatch of subscription ids and the clients that are failing are pointing to a S number that doesn't exist on the update location.  The client is probably pointing at the right server, but the S value is incorrect for the subscription.  The fact you have multiple SUMs makes this more likely.

    Thanks

    Jak

    :5326
Children
No Data