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

Upgrade from 4.7 to 5.0 Console Fail. Management service refuses to start.

Just attempted to upgrade to Management console version 5.0 from 4.7

Installation appeared to go perfectly. Followed upgrade guide to the letter.

However, the management service now refuses to start.

A little investigation into the event logs shows.....

Sophos Managements Service :

Initialization failed.
Step: Migrating data if necessaryError: std::runtime_error. Database upgrade failed. Please see KBA 113946.Data: ErrorUnexpected

It would appear the database has not been upgraded. 

After more diggings I've checked the database instances using :

sqlcmd -E -S .\sophos -Q "select name from sysdatabases"

This returns all databases including SOPHOS45, SOPHOS47 (current version) and SOPHOS50

More digging I have tried to update the database manually....

upgradedb.exe -debug -sourceVersion=47

returns.....

25.04.2012 11:39:20      ... successfully completed.25.04.2012 11:39:20 Validating parameter values ...25.04.2012 11:39:20      ... successfully completed.25.04.2012 11:39:20 Transferring data to the new database ...25.04.2012 11:39:23 Error: std::exception thrown  SP Error: 55 (ErrorDataTransferFailed)25.04.2012 11:39:23 Exit code 5 (Failed to transfer data from the old database.)

Help please????? Thanks.

:24119


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

    What is the error in the application event log from the management service when it fails to start?

    KB: http://www.sophos.com/en-us/support/knowledgebase/111898.aspx should help based on the error.

    The management service will not start if it unsure of the state of the database.  The "upgradestatus" value in the "upgrade" table of the "new" database should be 2. 

    sqlcmd -E -S .\sophos -d sophos51 -Q "select upgradestatus from upgrade"

    should return 2 if you're upgrading to SEC 5.1 for example.   It is set to 2 when the migration of the data from the old to new database is complete.  UpgradeDB.exe (http://www.sophos.com/en-us/support/knowledgebase/65420.aspx) is the tool that runs as part of the management server upgrade.  It connects to the newly created database (e.g. SOPHOS51 if you're upgrading to SEC 5.1) and calls the stored procedure as metnioned in the article.

    Regards,

    Jak

    :34987
Reply
  • HI,

    What is the error in the application event log from the management service when it fails to start?

    KB: http://www.sophos.com/en-us/support/knowledgebase/111898.aspx should help based on the error.

    The management service will not start if it unsure of the state of the database.  The "upgradestatus" value in the "upgrade" table of the "new" database should be 2. 

    sqlcmd -E -S .\sophos -d sophos51 -Q "select upgradestatus from upgrade"

    should return 2 if you're upgrading to SEC 5.1 for example.   It is set to 2 when the migration of the data from the old to new database is complete.  UpgradeDB.exe (http://www.sophos.com/en-us/support/knowledgebase/65420.aspx) is the tool that runs as part of the management server upgrade.  It connects to the newly created database (e.g. SOPHOS51 if you're upgrading to SEC 5.1) and calls the stored procedure as metnioned in the article.

    Regards,

    Jak

    :34987
Children
No Data