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

Migrating EC v4 to new server - updates now fail

Good evening,

Recently moved an installation of Sophos EC  v4 from our old server to the new live server. Followed the Sophos Migration guide to the letter (no number just dated June 2010).

Initially tried to move everything from v4 to v4.5 but that did not work. Doh should have engaged brain first, stupid.

Then installed v4.0 on the new server and the migration seemed to go ok. EC started up fine and all the computers were present.

Selected Update Manager and tried to force an update. This went away for a while and then failed. Might have a handle on this as I realised I did not clean out the Sophos Update share between version (v4.5 and v4.0) so I have a plan on how to solve that issues.

Went to a client and tried to get it to update it failed with 'Could not connect to server'. From memory its running EP 9.0

On checking the configuration of the update I noticed it uses SophosUpdateMgr as the user with a hidden password. Now my understanding is that the EC will create this user with a random password when it is installed if it does not already exist. Does this then get changes when I restore the registry / certificates / database  or do I have to invade the AD on the old server to find the password and then set it on the new and run the Sophos 'hide' it etc.?

If its not that can anyone please provide a pointer to the probable cause of the problem.

Regards

Gary

:5531


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

    Thank-you for the guidance. I have to agree that the client connection problems are probably caused by either a password error (hope that is now fixed) or more likely the fact that the CIDs are not present as I cannot actually do an update within SUM.

    I had a little time at the customner's site today and concentrated on the SUM update issues.  I did a few update now operations and reviewed what was shown in the logs. Interestingly the file that always failed on update 8b53ecb8caaa96d152d45c855fcab71ex000.dat was in fact not present on the SOPHOS update server.

    Fortunately on one of the update runs some other files did manage to stream correctly, which I believe shows that any authentication in place is working correctly. It just appears to be that single update. 

    010-11-02 15:55:20 : Cmd-ALL << [I1012][1da90b76a90390c59d2522165e3b2b2ax000.dat] Starting to synchronise file '1da90b76a90390c59d2522165e3b2b2ax000.dat'...
    2010-11-02 15:55:20 : Cmd-ALL << [I1013][1da90b76a90390c59d2522165e3b2b2ax000.dat] Finished synchronisation of file '1da90b76a90390c59d2522165e3b2b2ax000.dat'.
    2010-11-02 15:55:20 : Cmd-ALL << [I1012][61a5fb191ae2ae876db31dcce75e4183x000.dat] Starting to synchronise file '61a5fb191ae2ae876db31dcce75e4183x000.dat'...
    2010-11-02 15:55:24 : Cmd-ALL << [I1013][61a5fb191ae2ae876db31dcce75e4183x000.dat] Finished synchronisation of file '61a5fb191ae2ae876db31dcce75e4183x000.dat'.
    2010-11-02 15:55:24 : Cmd-ALL << [I1012][8b53ecb8caaa96d152d45c855fcab71ex000.dat] Starting to synchronise file '8b53ecb8caaa96d152d45c855fcab71ex000.dat'...
    2010-11-02 15:55:24 : Error during package synchronisation: Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat
    2010-11-02 15:55:24 : Sync failure: Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat
    2010-11-02 15:55:24 : EventLog: 3758112769 1 Inserts:> "F26F7EC0-1302-4DA7-8B6B-A5383051D41A" "Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat" "RECOMMENDED" "http://sophos.yhgfl.net/libraryv4//Warehouse"
    2010-11-02 15:55:24 : Cmd-ALL << [E4001][F26F7EC0-1302-4DA7-8B6B-A5383051D41A][Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat][RECOMMENDED][http://sophos.yhgfl.net/libraryv4//Warehouse] Synchronise operation failed when synchronising payload 'F26F7EC0-1302-4DA7-8B6B-A5383051D41A'. Details: Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat
    2010-11-02 15:55:24 : EventLog: 3758112827 1 Inserts:> "7D48A012-0C64-4F21-BA27-A9CEDF442749" "Not attempted." "0.0.0" "http://sophos.yhgfl.net/libraryv4//Warehouse"
    2010-11-02 15:55:24 : Cmd-ALL << [E403B][7D48A012-0C64-4F21-BA27-A9CEDF442749][Not attempted.][0.0.0][sophos.yhgfl.net/.../Warehouse] Payload '7D48A012-0C64-4F21-BA27-A9CEDF442749' could not be synchronised because the synchronise operation failed due to an earlier error.

    Before doing these updates I stopped the SUM service, cleared our the Warehouse and deleted the SUM..xml file, then restarted the service as instructed for a 80040406 error by Sophos.

    Does anyone have any idea why this rogue update is still appearing even though I have cleared the Warehouse and SUM update status file? IS this error causing all the remaining updates to fail and thus the CIDs not to be generated?

    Regards

    Gary

    :5709
Reply
  • Hi

    Thank-you for the guidance. I have to agree that the client connection problems are probably caused by either a password error (hope that is now fixed) or more likely the fact that the CIDs are not present as I cannot actually do an update within SUM.

    I had a little time at the customner's site today and concentrated on the SUM update issues.  I did a few update now operations and reviewed what was shown in the logs. Interestingly the file that always failed on update 8b53ecb8caaa96d152d45c855fcab71ex000.dat was in fact not present on the SOPHOS update server.

    Fortunately on one of the update runs some other files did manage to stream correctly, which I believe shows that any authentication in place is working correctly. It just appears to be that single update. 

    010-11-02 15:55:20 : Cmd-ALL << [I1012][1da90b76a90390c59d2522165e3b2b2ax000.dat] Starting to synchronise file '1da90b76a90390c59d2522165e3b2b2ax000.dat'...
    2010-11-02 15:55:20 : Cmd-ALL << [I1013][1da90b76a90390c59d2522165e3b2b2ax000.dat] Finished synchronisation of file '1da90b76a90390c59d2522165e3b2b2ax000.dat'.
    2010-11-02 15:55:20 : Cmd-ALL << [I1012][61a5fb191ae2ae876db31dcce75e4183x000.dat] Starting to synchronise file '61a5fb191ae2ae876db31dcce75e4183x000.dat'...
    2010-11-02 15:55:24 : Cmd-ALL << [I1013][61a5fb191ae2ae876db31dcce75e4183x000.dat] Finished synchronisation of file '61a5fb191ae2ae876db31dcce75e4183x000.dat'.
    2010-11-02 15:55:24 : Cmd-ALL << [I1012][8b53ecb8caaa96d152d45c855fcab71ex000.dat] Starting to synchronise file '8b53ecb8caaa96d152d45c855fcab71ex000.dat'...
    2010-11-02 15:55:24 : Error during package synchronisation: Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat
    2010-11-02 15:55:24 : Sync failure: Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat
    2010-11-02 15:55:24 : EventLog: 3758112769 1 Inserts:> "F26F7EC0-1302-4DA7-8B6B-A5383051D41A" "Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat" "RECOMMENDED" "http://sophos.yhgfl.net/libraryv4//Warehouse"
    2010-11-02 15:55:24 : Cmd-ALL << [E4001][F26F7EC0-1302-4DA7-8B6B-A5383051D41A][Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat][RECOMMENDED][http://sophos.yhgfl.net/libraryv4//Warehouse] Synchronise operation failed when synchronising payload 'F26F7EC0-1302-4DA7-8B6B-A5383051D41A'. Details: Cannot create stream http://sophos.yhgfl.net/libraryv4//Warehouse/8b53ecb8caaa96d152d45c855fcab71ex000.dat
    2010-11-02 15:55:24 : EventLog: 3758112827 1 Inserts:> "7D48A012-0C64-4F21-BA27-A9CEDF442749" "Not attempted." "0.0.0" "http://sophos.yhgfl.net/libraryv4//Warehouse"
    2010-11-02 15:55:24 : Cmd-ALL << [E403B][7D48A012-0C64-4F21-BA27-A9CEDF442749][Not attempted.][0.0.0][sophos.yhgfl.net/.../Warehouse] Payload '7D48A012-0C64-4F21-BA27-A9CEDF442749' could not be synchronised because the synchronise operation failed due to an earlier error.

    Before doing these updates I stopped the SUM service, cleared our the Warehouse and deleted the SUM..xml file, then restarted the service as instructed for a 80040406 error by Sophos.

    Does anyone have any idea why this rogue update is still appearing even though I have cleared the Warehouse and SUM update status file? IS this error causing all the remaining updates to fail and thus the CIDs not to be generated?

    Regards

    Gary

    :5709
Children
No Data