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

Question

Just attempted to upgrade to Management console version 5.2 from 5.0

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&colon; 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, SOPHOS50 (current version) and SOPHOS52

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

upgradedb.exe -debug -sourceVersion=50

returns.....

03.06.2013 10:45:55 Parsing command-line qualifiers ... successfully completed.

03.06.2013 10:45:55 Validating parameter values ...
03.06.2013 10:45:55 ... successfully completed.
03.06.2013 10:45:55 Transferring data to the new database ...
03.06.2013 10:46:01 Error: std::exception thrown SP Error: 55 (ErrorDataTransfe
rFailed)
03.06.2013 10:46:01 Exit code 5 (Failed to transfer data from the old database.)

Help please. Thanks in advance.

This thread was automatically locked due to age.

jak · Answer

Hi,

I would suggest trying to run the Stored Procedure directly to perform the migration of the data as UpgradeDB.exe just calls a Stored Procedure in the new database.

I would:

1. install SQL Server Management Studio first if you don't already have it.

2. Re-create the SOPHOS52 database (I assume you are going to SEC 5.2.0 rather than the just released 5.2.1?)

As some data might have been copied over which could potentially cause another problem on the next transfer, So best to start with a clean SOPHOS52.

To do so, If SEC database is installed on a DC run:

C:\sec_52\ServerInstaller\DB\Core\InstallDB.bat (local)\SOPHOS [NetBIOSDomainName] SOPHOS52 Sophos_InstallCore52DB.log

If SEC DB is on a workgroup computer or member server:

C:\sec_52\ServerInstaller\DB\Core\InstallDB.bat (local)\SOPHOS [NetBIOSComputerName] SOPHOS52 Sophos_InstallCore52DB.log

NetBIOSDomainName or NetBIOSComputerName should be replaced accordingly, this values is essentially where the "Sophos DB Admins" group resides, i.e. is it a domain local group or a local group.

Details here if needed:
http://www.sophos.com/en-us/support/knowledgebase/116768.aspx

3. Then n SQL Server Management Studio connect to the newly created SOPHOS52 database and execute the command:

exec dbo.FromX 50, 0

Make sure, you're running this with enough rights to read from SOPHOS50. And it also needs the ability to call "SET IDENTITY_INSERT" which requires higher rights (http://msdn.microsoft.com/en-us/library/aa259221(v=sql.80).aspx). It's best therefore to run this one off command as a SQL admin I would suggest to rule out any problems.

If this errors, it should print more specific errors to the SQL window.

If that doesn't work you could try calling the SP; "dbo.From50 0" as this is the SP that FromX would call in your case. If this completes, then you need to manually set the upgrade status in nthe upgrade table to 2. I.e.

UPDATE dbo.Upgrade SET UpgradeStatus =2

Regards,

Jak