Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 4213 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

Sophos Enterprise Console Upgrade (5.2.2 to 5.4.1) Error - Management Server Connection Failed

Fahid Shaheen

Hi,

 

I just upgraded our on-prem SEC from 5.2.2.

The back up and upgrade seemed to go OK, but I can't launch the Console.

The Sophos management service will refuse to start.

And the SQL Sophos Agent is stopped.

I've checked the MDF files and SOPHOS521 is at 6Gb where as SOPHOS540 is 70Mb.

 

I've tried the upgradeDB command to no avail.

 

Please can you help, I need SEC up and running urgently.

 

Many thanks.



This thread was automatically locked due to age.
  • 0

    When you try to start the management service, what error is in the Application Event log?  I guess a message that essentially means the database has not been upgraded?  This would make sense given the sizes of the DBs you mention as the new should be much larger once the data is moved to it.

    What version of MS SQL server are you running?  I can see it's a Sophos instance but is it SQL Express 2005, 2008, 2008R2, 2012 etc..?

    I wonder if the max sizes of database could be coming into play?

    Microsoft SQL Server 2005 Express edition has a database size limit to 4GB
    Microsoft SQL Server 2008 Express edition has a database size limit to 4GB
    Microsoft SQL Server 2008 R2 Express edition has a database size limit to 10GB
    Microsoft SQL Server 2012 Express edition has a database size limit to 10GB
    Microsoft SQL Server 2014 Express edition has a database size limit to 10GB

    Given the info in: https://community.sophos.com/kb/65420, I might be interested to try using SQL Management studio to run the same stored procedures UpgradeDB.exe calls to perform the data migration to see if any more specific SQL error is returned.  

    If I had SQL Profiler, to be sure I'm running the correct command I'd run UpgradeDB.exe as you have done: E.g. upgradedb.exe -debug -sourceVersion=521 and see the stored procedure get called to kick off the data migration and with which parameters.  

    In the Upgrade Scenario table of the above KBA, I don't think your exact upgrade path is covered? 5.2.2 to 5.4.1.

    Is it:

    dbo.FromX 52, 0
    dbo.RedirectSynonyms 'SOPHOS540'

    or:

    dbo.FromX 522, 0
    dbo.RedirectSynonyms 'SOPHOS540'

    I guess it wouldn't do any harm to try the first, you should know it's working pretty quickly.  The good news is it won't affect the "existing" SEC versions database and you can keep creating the new database and try the migration of data as many times as is necessary.

     has done more with database migrations than I have recently.  He might be able to confirm the commands based on the version you are going from and to.

    Regards,

    Jak

  • +1 in reply to jak

    Many thanks for your reply Jack.

     

    Yes I should have properly checked the event log... which reported DB migration failed.

     

    Anyhow, was on to Holden in Canada and then Ravi in UK (Sophos support) and both were awesome.

    Both helped in ascertaining that the BD migration failed due a permissions issue.  After running the UpgradeDB command with the reset flag included but as the DB owner, all worked successfully.

     

    We're now back up and running... so a simply lesson but important one... do the upgrade as DB owner if possible, thus avoiding this issue in the first place.

     

    Many thanks for the forum and Sophos support for their help.

Unfiltered HTML