Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1164 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

Upgrade advisor finding 'Non-Sophos' databases

Issgazer

Windows Server 2003 - SAV 7.6.2.1 - EM Lib 1.3.2 -  Enterprise Console 3.1.0

Everything on the same box. Responding to the 'Require to upgrade by 31st March' messages.

I have run the upgrade advisor and it's reporting:

"Finding non-Sophos databases,Non-Sophos databases have been added to the SOPHOS instance. Applications relying on these databases may stop working after the upgrade. The non-Sophos databases detected are: SOPHOS,SOPHOS2.,Warning"

Connecting with SQL Server Management Studio Express I can see SOPHOS - SOPHOS2 and SOPHOS3 (don't know what happened to SOPHOS1). I can also see:

"SQL server compatibility,The SQL server used is no longer supported. The upgrade will involve upgrading the SQL server.,Warning"

Every other check has the status 'OK'

Does this look like the upgrade path is going to work (no red errors) or will the upgrade software require manual intervention due to the warnings?

Thanks,

John

:8089


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

    Hi,

    The database to SEC version mappings are as follows:

    SEC1 - SOPHOS

    SEC2 - SOPHOS2

    SEC3 - SOPHOS3

    SEC4 - SOPHOS4

    SEC4.5 - SOPHOS45

    SEC4.7 - SOPHOS47  (when released)

    So there has never been a SOPHOS1. :)

    When you upgraded from SEC1 to SEC2, the SOPHOS database would have remained attached to the SQL instance, likewise on any upgrades, the previous database would have also been left.  You could take a backup of them, detatch, them and drop them.  If you're happy that you no longer require all but the current one, in this case SOPHOS3 is required.

    This article describes dropping an old database using OSQL.

    http://www.sophos.com/support/knowledgebase/article/17508.html

    I guess you're also running MSDE, so this will be updated to a later version of SQL Express.  They are only warning and you should be able to continue and follow the advice in the html page selected by the Upgrade Advisor.

    Just as a FYI, In order to restore your SEC3 installation, should anything go wrong, a backup of the key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Certification Manager\CertAuthStore

    and a backup of the SOPHOS3 database should be all that is required, so it's worth grabbing both of those before performing the upgrade.

    Regards,

    Jak

    :8117
Reply
  • 0

    Hi,

    The database to SEC version mappings are as follows:

    SEC1 - SOPHOS

    SEC2 - SOPHOS2

    SEC3 - SOPHOS3

    SEC4 - SOPHOS4

    SEC4.5 - SOPHOS45

    SEC4.7 - SOPHOS47  (when released)

    So there has never been a SOPHOS1. :)

    When you upgraded from SEC1 to SEC2, the SOPHOS database would have remained attached to the SQL instance, likewise on any upgrades, the previous database would have also been left.  You could take a backup of them, detatch, them and drop them.  If you're happy that you no longer require all but the current one, in this case SOPHOS3 is required.

    This article describes dropping an old database using OSQL.

    http://www.sophos.com/support/knowledgebase/article/17508.html

    I guess you're also running MSDE, so this will be updated to a later version of SQL Express.  They are only warning and you should be able to continue and follow the advice in the html page selected by the Upgrade Advisor.

    Just as a FYI, In order to restore your SEC3 installation, should anything go wrong, a backup of the key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Certification Manager\CertAuthStore

    and a backup of the SOPHOS3 database should be all that is required, so it's worth grabbing both of those before performing the upgrade.

    Regards,

    Jak

    :8117
Children
No Data