Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 2473 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

error upgrading sophos45 db to 50 on sql 2008

tdubb

I am getting an error when running the sophos5 installer on the db server to upgrade the 45 database. 

MSI (s) (3C:98) [12:26:29:733]: Note: 1: 1402 2: UNKNOWN\Components\DA42BC89BF25F5BD0AF18C3B9B1A1EE8\2BEDF90E8F2D7E14E94486F6F593A14E 3: 5 MSI (s) (3C:98) [12:26:29:734]: Product: Sophos Enterprise Console -- Error 1402.Could not open key: UNKNOWN\Components\DA42BC89BF25F5BD0AF18C3B9B1A1EE8\2BEDF90E8F2D7E14E94486F6F593A14E.  System error 5.  Verify that you have sufficient access to that key, or contact your support personnel.
MSI (s) (3C:98) [12:26:29:738]: User policy value 'DisableRollback' is 0MSI (s) (3C:98) [12:26:29:738]: Machine policy value 'DisableRollback' is 0Action ended 12:26:29: InstallExecute. Return value 3.MSI (s) (3C:98) [12:26:29:748]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1077240654,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)MSI (s) (3C:98) [12:26:29:748]: Executing op: DialogInfo(Type=0,Argument=1033)MSI (s) (3C:98) [12:26:29:749]: Executing op: DialogInfo(Type=1,Argument=Sophos Enterprise Console)MSI (s) (3C:98) [12:26:29:750]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back actions,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])MSI (s) (3C:B0) [12:26:29:759]: I/O on thread 5768 could not be cancelled. Error: 1168MSI (s) (3C:B0) [12:26:29:759]: I/O on thread 4704 could not be cancelled. Error: 1168MSI (s) (3C:B0) [12:26:29:759]: I/O on thread 7056 could not be cancelled. Error: 1168MSI (s) (3C:B0) [12:26:29:759]: I/O on thread 5784 could not be cancelled. Error: 1168MSI (s) (3C:B0) [12:26:29:759]: I/O on thread 5884 could not be cancelled. Error: 1168MSI (s) (3C:B0) [12:26:29:759]: I/O on thread 5148 could not be cancelled. Error: 1168

:21133


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

    That will be the tool UpgradeDB.exe.  

    UpgradeDB.exe (http://www.sophos.com/support/knowledgebase/article/65420.html ) is run on the management server as part of the upgrade of the management server.  At the point it is run the new SOPHOS50 database should already have been created on the database machine.

    UpgradeDB.exe reads the MSConnectionString registry key (HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\EE\Management Tools ) from the management server machine to locate the new database (SOPHOS50) in the relevant instance also defined in the connection string.  

    It runs the Stored Procedure "dbo.FromXTo4" which then ultimately ends up running the relevant stored procedure that perfoms the migration of data, these are:

    • From45To50
    • From47To50
    • From4To50

    depending on the parameters passed to "dbo.FromXTo4" by UpgradeDB.exe.  UpgradeDB.exe in your case would have been run with the switch -sourceVersion=45 , it would have then run: 


    dbo.FromXto4 45, 0

    Which would have called:
    dbo.From45To50

    If this returned success, dbo.FromXTo4 will set the UpgradeStatus in the dbo.Upgrade table of the new SOPHOS50 database to 2 so when the Sophos Management Service connects to the new database (SOPHOS50), it knows it has been updated and is ready to be used.

    So you can either run:
    UpgradeDB.exe -sourceVersion=45  

    on the management server or run:

    sqlcmd -E -S .\SOPHOS -d SOPHOS50 -Q "dbo.FromXto4 45, 0 "

    on the SQL server, where the above command references a local instance called SOPHOS.

    Hope this helps explain what's going on under the hood and what you need to do.

    Regards, 

    Jak

    :21141
Reply
  • 0

    That will be the tool UpgradeDB.exe.  

    UpgradeDB.exe (http://www.sophos.com/support/knowledgebase/article/65420.html ) is run on the management server as part of the upgrade of the management server.  At the point it is run the new SOPHOS50 database should already have been created on the database machine.

    UpgradeDB.exe reads the MSConnectionString registry key (HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\EE\Management Tools ) from the management server machine to locate the new database (SOPHOS50) in the relevant instance also defined in the connection string.  

    It runs the Stored Procedure "dbo.FromXTo4" which then ultimately ends up running the relevant stored procedure that perfoms the migration of data, these are:

    • From45To50
    • From47To50
    • From4To50

    depending on the parameters passed to "dbo.FromXTo4" by UpgradeDB.exe.  UpgradeDB.exe in your case would have been run with the switch -sourceVersion=45 , it would have then run: 


    dbo.FromXto4 45, 0

    Which would have called:
    dbo.From45To50

    If this returned success, dbo.FromXTo4 will set the UpgradeStatus in the dbo.Upgrade table of the new SOPHOS50 database to 2 so when the Sophos Management Service connects to the new database (SOPHOS50), it knows it has been updated and is ready to be used.

    So you can either run:
    UpgradeDB.exe -sourceVersion=45  

    on the management server or run:

    sqlcmd -E -S .\SOPHOS -d SOPHOS50 -Q "dbo.FromXto4 45, 0 "

    on the SQL server, where the above command references a local instance called SOPHOS.

    Hope this helps explain what's going on under the hood and what you need to do.

    Regards, 

    Jak

    :21141
Children
No Data
Cookie Information Banner