Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 9781 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

[updating] could not contact server

phidippus

Hello,

I am having an updating problem. The message says 'could not contact server'. I see there are many posts on this issue, but I was unable to make use of the existing posts, partly because I don't understand them. So I decided to post my own. My OS is Windows 7 Enterprise (64bit), and Sophos Endpoint Security and Control is version 9.5. I paste a log from the application below. Thank you for your help.

*****************************************************************

Time: 1/29/2012 23:39:30Message: AutoUpdate finishedModule: ALUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:29Message: Installation of Sophos AutoUpdate skippedModule: ALUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:29Message: Installation of SAVXP skippedModule: ALUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:29Message: Downloading phase completedModule: ALUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:28Message: Product cache update from secondary server successfully finishedModule: SDDSUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:28Message: Downloading product Sophos AutoUpdate from server SophosModule: SDDSUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:27Message: Product cache update from secondary server successfully finishedModule: SDDSUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:26Message: Downloading product SAVXP from server SophosModule: SDDSUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:24Message: Download of product RMSNT from server Sophos skipped because it is unavailable from this locationModule: ALUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:23Message: ERROR:   Download of Sophos AutoUpdate failed from server http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP/Module: CIDUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:23Message: Downloading product Sophos AutoUpdate from server http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP/Module: CIDUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:21Message: ERROR:   Download of SAVXP failed from server http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP/Module: CIDUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:21Message: Downloading product SAVXP from server http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP/Module: CIDUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:19Message: ERROR:   Download of RMSNT failed from server http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP/Module: CIDUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:18Message: Downloading product RMSNT from server http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP/Module: CIDUpdateProcess ID: 4660Thread ID: 4228
Time: 1/29/2012 23:39:18Message: ***************          Sophos AutoUpdate started          ***************Module: ALUpdateProcess ID: 4660Thread ID: 4228

:21439


This thread was automatically locked due to age.
Parents
  • 0

    HI,

    Are you able to paste the contents of the AutoUpdate trace log during a failed update.  You can find them here:

    "C:\ProgramData\Sophos\AutoUpdate\Logs \ALUpdate[timestamp].log"

    Just the text beween the text:

    ALUpdate started:

    and

    ALUpdate started:

    of the last update check should do.

    Out of interest, is this the only machine updating from that same location ( http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP ) with the problem, this should rule out the distribution location being the issue.

    Regards,

    Jak

    :21441
Reply
  • 0

    HI,

    Are you able to paste the contents of the AutoUpdate trace log during a failed update.  You can find them here:

    "C:\ProgramData\Sophos\AutoUpdate\Logs \ALUpdate[timestamp].log"

    Just the text beween the text:

    ALUpdate started:

    and

    ALUpdate started:

    of the last update check should do.

    Out of interest, is this the only machine updating from that same location ( http://140.112.8.164/webinst/CIDs/S000/SAVSCFXP ) with the problem, this should rule out the distribution location being the issue.

    Regards,

    Jak

    :21441
Children
No Data