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 Management Console error upgradr

Hi,

Please advice us for our console cannot start the management console, the management service cannot start.

I look on the event viewer I found out this error:

Initialization failed.

Step: Migrating data if necessary

Error: std::runtime_error. Database upgrade failed. Please see KBA 113946.

Data: ErrorUnexpected

Sophos SEC V:4.7 upgrade to 5.1

Thanks in advance,

tedz

:39721


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

    You don't need to specify a UDL file unless you're running upgradedb.exe on a computer other than the Sophos Management server as a way to tell UpgradeDB.exe where the database instance and database is.  When you run upgradedb.exe on the management server it just reads this info from the registry.

    If the upgrade fails -- 

    Note: Tthe upgrade is just moving data from SOPHOS47 to SOPHOS51 in this case and then setting the upgradestatus in the upgrade table of SOPHOS52 to 2.

    If it fails to transfer the data it is also best to recreate the new database SOPHOS51 first using InstallDB.bat:

    http://www.sophos.com/en-us/support/knowledgebase/116768.aspx

    Then try UpgradeDB.exe again, in your case on the management server, as an administrator run:

    upgradedb.exe -debug -sourceVers ion=47

    If this still fails, have a look at:

    http://www.sophos.com/en-us/support/knowledgebase/65420.aspx

    You can see the stored procedure that actually gets called by UpgradeDB.exe,  running that manually will give you more specific info if there is a problem.

    Regards,

    Jak

    :39831
Reply
  • Hi,

    You don't need to specify a UDL file unless you're running upgradedb.exe on a computer other than the Sophos Management server as a way to tell UpgradeDB.exe where the database instance and database is.  When you run upgradedb.exe on the management server it just reads this info from the registry.

    If the upgrade fails -- 

    Note: Tthe upgrade is just moving data from SOPHOS47 to SOPHOS51 in this case and then setting the upgradestatus in the upgrade table of SOPHOS52 to 2.

    If it fails to transfer the data it is also best to recreate the new database SOPHOS51 first using InstallDB.bat:

    http://www.sophos.com/en-us/support/knowledgebase/116768.aspx

    Then try UpgradeDB.exe again, in your case on the management server, as an administrator run:

    upgradedb.exe -debug -sourceVers ion=47

    If this still fails, have a look at:

    http://www.sophos.com/en-us/support/knowledgebase/65420.aspx

    You can see the stored procedure that actually gets called by UpgradeDB.exe,  running that manually will give you more specific info if there is a problem.

    Regards,

    Jak

    :39831
Children
No Data