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 over HTTP through Forefront TMG

Currently testing Sophos 9.7, I've setup a CID to be available over HTTP, published through MS Forefront TMG.

It has been working fine for almost a month, but suddenly my test "remote" client returned errors.

In short:

  • The client finds the remote CID to be corrupted ("CIDSYNC_E_RCIDERROR (Remote CID is corrupted.) " 
  • It then starts to look for the "/catalogue/sdds.esc97.xml " file, which does not exist
  • Sophos update fails 

Interestingly enough, this only happens when downloading through the Forefront TMG: when connecting to the same resource (i.e.: updates.domain.local), there is no problem.

The remote client's log reads:

Trace(2011-Sep-02 10:22:31): TrySyncProduct<class AutoUpdate::CIDUpdateLocation>, Calling SyncProduct with {E17FE03B-0501-4aaa-BC69-0129D965F311}
Trace(2011-Sep-02 10:22:31): CIDUpdateLocation::SyncProduct - Updating Product: SAVXP
Trace(2011-Sep-02 10:22:31): CIDUpdate(SyncProduct.Start): SAVXP, http://updates.domain.com/antivirus/xp/
Trace(2011-Sep-02 10:22:31): CIDUpdateLocation::Sync - Updating from http CID: http://updates.domain.com/antivirus/xp/savxp
Trace(2011-Sep-02 10:22:31): CIDSync(CidSyncMessage): 
Trace(2011-Sep-02 10:22:33): CIDSync(CidSyncMessage): svf.xml
Trace(2011-Sep-02 10:22:33): CIDSyncCallback, SynchronisationTerminated - Code = -2147217663
Trace(2011-Sep-02 10:22:33): CIDSyncCallback, SynchronisationTerminated - MapFile = C:\ProgramData\Sophos\AutoUpdate\cache\savxp.map
Trace(2011-Sep-02 10:22:33): CIDUpdateLocation::SyncProduct: Failed to update product (SAVXP) from "http://updates.domain.com/antivirus/xp/", Error is :CIDSYNC_E_RCIDERROR (Remote CID is corrupted.)
Trace(2011-Sep-02 10:22:33): CIDUpdate(CIDDownloadFailed): SAVXP, http://updates.domain.com/antivirus/xp/
Trace(2011-Sep-02 10:22:34): TrySyncProduct<class AutoUpdate::CIDUpdateLocation>, SyncProduct returned - 0
Trace(2011-Sep-02 10:22:34): TrySyncProduct<class AutoUpdate::CIDUpdateLocation>, Ended - 0
Trace(2011-Sep-02 10:22:34): TrySyncProduct<class AutoUpdate::SDDSUpdateLocation>, Started: 
Trace(2011-Sep-02 10:22:34): TrySyncProduct<class AutoUpdate::SDDSUpdateLocation>, creating update location
Trace(2011-Sep-02 10:22:34): Path to decode files to: C:\Windows\TEMP\sophos_autoupdate1.dir\1314951754
Trace(2011-Sep-02 10:22:34): Using top level catalogue sdds.esc97
Trace(2011-Sep-02 10:22:34): SDDSUpdateLocation, constructor start
Trace(2011-Sep-02 10:22:34): locConfig.m_server = http://updates.domain.com/antivirus/xp/
Trace(2011-Sep-02 10:22:34): Calling check on source.m_address.m_path = http://updates.domain.com/antivirus/xp/
Trace(2011-Sep-02 10:22:34): Calling package_source_init
Trace(2011-Sep-02 10:22:34): Creating package source to represent parent
Trace(2011-Sep-02 10:22:34): Create package source to represent local cache
Trace(2011-Sep-02 10:22:34): SDDSUpdateLocation::Constructor finished
Trace(2011-Sep-02 10:22:34): TrySyncProduct, Calling BeginSync
Trace(2011-Sep-02 10:22:34): SDDSUpdateLocation caught exception from BeginSync: Cannot create stream http://updates.domain.com/antivirus/xp/catalogue/sdds.esc97.xml GetLastError returned 0
Trace(2011-Sep-02 10:22:34): TrySyncProduct<class AutoUpdate::SDDSUpdateLocation>, Ended - 0
 

Is there anyone who can provide me any details on the "CIDSYNC_E_RCIDERROR " error and the "catalogue/sdds.esc97.xml " file?

Thank you very much!

:16117


This thread was automatically locked due to age.
Parents
  • HI,

    Have you tried removing the CID and letting SUM re-create it?

    Also is it right that only one client is failing in this way?  I wonder if the error might be due to a local problem on the client and the CID perhaps means the local cache in this context? 

    As a test, delete the CID, let SUM re-create it.  Try an update now, if the same problem, delete on the client the "contents" of "C:\ProgramData\Sophos\AutoUpdate\cache\" and delete: "C:\ProgramData\Sophos\AutoUpdate\data\status \status.xml" and let the client update.  Does that help?


    Jak 

    :16137
Reply
  • HI,

    Have you tried removing the CID and letting SUM re-create it?

    Also is it right that only one client is failing in this way?  I wonder if the error might be due to a local problem on the client and the CID perhaps means the local cache in this context? 

    As a test, delete the CID, let SUM re-create it.  Try an update now, if the same problem, delete on the client the "contents" of "C:\ProgramData\Sophos\AutoUpdate\cache\" and delete: "C:\ProgramData\Sophos\AutoUpdate\data\status \status.xml" and let the client update.  Does that help?


    Jak 

    :16137
Children
No Data