Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 20 replies
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 25490 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

Update from HTTP CID failing after updating to SAV 10.7.6 and SAU 5.10.139

Ahsan Amin

Update from HTTP CID failing after updating to SAV 10.7.6 and SAU 5.10.139

Reinstalling the earlier version works fine.

Do I need to make a change to IIS?

 

I have a case logged with Sophos, just checking if anyone else has the same issue?



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

    Hello Ahsan Amin,

    I'm not aware of any changes in the CID that cause problems or that SAU 5.10 fails on an IIS CID.
    [shamelessly quoting a post I've writte just a few minutes ago]
    please check the ALUpdate log on the endpoints one should suffice as the error seems to be the same for all - BTW: Does your SEC server update or does it show the same error? Please note: If you follow the ALUpdate.log link in the article it takes you to the significant files article but the location given there is incorrect, the ALUpdate.log is in %ProgramData%\Sophos\AutoUpdate\Logs\. If you want us to have a look at it even though you've logged a case please post one complete cycle here. 

    Christian

  • 0 in reply to QC

    QC said:

    BTW: Does your SEC server update or does it show the same error?

    The person who setup Sophos no longer works here and the backup is off sick. I've been figuring out how it all fits together by following the guides and posts here.

    I deleted the SAVSCFXP folder from the "Initial Install Source" and watched as the SUM recreated it.

    Any clients on SAU 5.7.533 are able to connect to the HTTP CID, download and update to SAU 5.10.139. Once on the new SAU version, they are unable to connect to the server. This included the SEC which also updated to 5.10.139.

Reply
  • 0 in reply to QC

    QC said:

    BTW: Does your SEC server update or does it show the same error?

    The person who setup Sophos no longer works here and the backup is off sick. I've been figuring out how it all fits together by following the guides and posts here.

    I deleted the SAVSCFXP folder from the "Initial Install Source" and watched as the SUM recreated it.

    Any clients on SAU 5.7.533 are able to connect to the HTTP CID, download and update to SAU 5.10.139. Once on the new SAU version, they are unable to connect to the server. This included the SEC which also updated to 5.10.139.

Children
No Data
Unfiltered HTML