Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 11331 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

'Base64ecode returned false' error after migration

kk20

migrating from 2008x64 5.2.2 installtion to 2012R2 5.2.2 installation on a new server.  Followed http://www.sophos.com/en-us/medialibrary/PDFs/documentation/sec_52_mgeng.pdf?la=en without any errors.  Got to point 12 where I would be putting the sophos update credentials into the new SUM when I got the 'Base64ecode returned false' error.

I followed the advice in KB article 110570 this does indeed spark a "wizard" but returns the same error. My licence details are the same as the old update server.

I have submitted a request to support and got a 6 point worksheet which didnt work; the sheet was concerned with re-adding the credentials and forcing an update - which is impossible as im having issue with precisely that!  Resubmitted the server logs to sophos and have heard nothing for 2 days. 

Has anyone else had this issue before?  I have come to the conclusion that SUM cannot be migrated - I had issues LAST time I migrated from an old server to a new one (in the end it was easier to delete everything and start again - this was a real pain, if I have to do that now then I might as start looking at another solution other than sophos)

:56632


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

    I would think you can just:

    1. Close SEC

    2. Stop the Sophos Management Service

    3. In regedit rename:
         HKEY_LOCAL_MACHINE\SOFTWARE\sophos\EE\Management Tools\Private
         to
         HKEY_LOCAL_MACHINE\SOFTWARE\sophos\EE\Management Tools\PrivateOld

    4. Start the Sophos Management Service

    5. Launch SEC and go into each policy of AutoUpdate and re-enter the password.  This will force the management service to re-write out the secure store entry for each password.  You might have to create the Private key but as long as SYSTEM has writes to read/write you're OK.

    6. Then go into the SUM configuration dialogs and enter the password for the accounts to talk to Sophos.

    Essentially anywhere there is a password relating to SUM and AutoUpdate.

    Clearly if you have hundreds of updating policies/SUMs, it might be easier to re-import the values with databackuprestore.

    Regards,

    Jak

    :56788
Reply
  • 0

    I would think you can just:

    1. Close SEC

    2. Stop the Sophos Management Service

    3. In regedit rename:
         HKEY_LOCAL_MACHINE\SOFTWARE\sophos\EE\Management Tools\Private
         to
         HKEY_LOCAL_MACHINE\SOFTWARE\sophos\EE\Management Tools\PrivateOld

    4. Start the Sophos Management Service

    5. Launch SEC and go into each policy of AutoUpdate and re-enter the password.  This will force the management service to re-write out the secure store entry for each password.  You might have to create the Private key but as long as SYSTEM has writes to read/write you're OK.

    6. Then go into the SUM configuration dialogs and enter the password for the accounts to talk to Sophos.

    Essentially anywhere there is a password relating to SUM and AutoUpdate.

    Clearly if you have hundreds of updating policies/SUMs, it might be easier to re-import the values with databackuprestore.

    Regards,

    Jak

    :56788
Children
No Data