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

Server to Server move - Cannot update SEC

Hi Everyone

I've migrated my SEC from a physical box which was working 100% and never missed a beat. Now ive migrated over to a new VM on 2012 R2 i cannot get the SEC update manager to download the updates from Sophos. I have the correct EM username and password. 


Ive been through KB111428 and everything is reading ok. Ive sent the analyser logs off to sophos but waiting back.

Im getting the following message:

Timeout while attempting to connect to the specified address. There may be a problem with the network.

Ive looked in the UpdateManager logs and im getting:

Error Decode operation failed with an unexpected error. Details: Failed to read customer file content.

Error Version information for product 'A845A8B5-6532-4EF1-B19E-1DB2B3CB73D1' was not gathered by dispatcher 'DispatcherSupplements-2014-10-28T13-34-49-29', as the last synchronization of that product failed.

Error Synchronize operation failed when synchronizing protection data. Details: Failed to download valid remote customer file content.

Also, the CID and Warehouse folders werent created so i have creted these myself to see if that was the problem - that didnt help a bit.

Update: Just to add to this, ive just checked my old server any its running 5.2.1. My new server which i migrated to is running 5.2.2. Have i broken this now? Should i upgrade the old version to 5.2.2 and then migrate?

:54341


This thread was automatically locked due to age.
  • Hello SHS_ICT,

    how exactly did you migrate? What did you import - database, etc.?

    Where and when does the error occur - following 111428 at the end of step 2 the connection is attempted when you click OK in the Source Details pop up. I'd expect the error at this point. Could you also check the SUMTrace log?

    Christian

    :54345
  • Hi Christian

    I migrated by following the Server to Server guide, its the 38 page documentation.

    I imported everything as the guide told me. 

    The error is indeed at the point where you are thinking,

    Ive attached the SUMtrace.log files for you to look at.


    Thanks


    Tim

    :54347
  • Interestingly I came on the boards to start my own thead on pretty much the same topic.  I'm not sure if I should still start my own thread or post on yours!  I'll start here for now.

    My SEC/Management Server/Database are all currently installed on a Windows Server 2003 32-bit VM - Sophos1.  The SEC is 5.2.2.

    I created a new Windows Server 2008 64-bit VM to migrate these services to.  This new server is on a new domain (in fact a whole new forest), although there is full trust between the domains and the Sophos1 server is currently protecting PCs on both domains.

    The migration guide available here - http://www.sophos.com/en-us/support/knowledgebase/28276.aspx - does explicitly state that the servers should be on the same domain, so I'm not complying from the off.

    However I have an extensive list of Device Control exemptions that would be an absolute nightmare to recreate, for both users and admins.  So I really need to carry this list from the old server to the new.

    I have tried a few times to migrate now but have failed each time.

    1.  I named the new server the same as the old one.  I then followed the migration guide through.  This move failed because of the same reason the OP of this thread states - the UM on the Management Server fails to connect to Sophos.  The details are all exactly as they were on the old server but it does not connect.  I could find no reason for this despite repeatedly checking networking/firewalls etc.

    2.  I tried again with a differently named server - eg Sophos2.  I then followed the migration guide through again.  This time I was unable to get the UM on the new server to show up in the Console, so I couldn't even enter the updating info.  None of my existing UMs would report to the console.  I even tried installing a new UM from the new servers installer - it still did not report in.

    3.  In a desperate attempt before my change window closed I tried to extract the SQL tables form the database and import into a clean database, although I didn't expect this ever to work, and the way I did it didn't.

    I have a ticket open with support but the guy is suggesting I just backup the database and restore on the new server.  I don't really see how this is going to work but it is the best plan I have at present. 

    I won't be able to get approval for another change window until next week so in the meantime I thought I would see if anyone on the message boards has successfully carried out such a move and has any advice to offer...!

    :54351