Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 3932 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 SEC 5.0 to 5.1 with error "Invalid source version: 50"

IK

Whilst attempting to upgrade a server to SEC 5.1, I bumped into the error stating: "The Server cannot be upgraded, the database needs to be upgraded first." ..

Looking at Sophos KB article 65420 and running “UpgradeDB.exe –debug –sourceVersion=50” it comes back with an error:

C:\Program Files (x86)\Sophos\Enterprise Console>UpgradeDB.exe -debug -sourceVer
sion=50
27.09.2012 11:45:46      ... successfully completed.
27.09.2012 11:45:46 Validating parameter values ...
27.09.2012 11:45:46 Invalid source version: 50
27.09.2012 11:45:46 Exit code 1 (Invalid command line qualifier.)

In our case the regkey for the database server is pointing to the right location, albeit not the same server where SEC runs on.

Value Name: DatabaseConnectionMS
Value Data: Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS50;Data Source=SQLSERVERNAME;

I've opened a case with Sophos [#3474860] and will update this thread with future steps.

:33279


This thread was automatically locked due to age.
  • 0

    Hello IK,

    if this is the UpgradeDB from the production system - which is at 5.0 - no wonder it doesn't accept 50?

    Please have a look at http://www.sophos.com/en-us/support/knowledgebase/33980.aspx

    Christian

    :33305
  • 0

    As QC points out...you need to create the new 5.1 databases on the database server first (by running the SEC 5.1 installer there), then when you run the 5.1 installer on the management server, upgradedb.exe will be called automatically by the management server upgrade process to move your existing data from the SOPHOS50 and SOPHOSPATCH databases to the new SOPHOS51 and SOPHOSPATCH51 databases.  Once happy you cxan drop the SOPHOS50 and SOPHOSPATCH databases becasuse they are no longer required.

    The upgrade procedure is always to upgrade the DB role first then the management server, then any remote consoles.

    Regards,

    Jak

    :33307
  • 0

    Thanks for these guys.

    Basically I had a small Change window open to perform this, which had to be reraised to continue the efforts.

    Ultimately it was indeed as simple as updating the SQL server before the SEC server, however, the upgrade guide (Product Version 5.1 // Document Date June 2012) doesn't state any of this, which didn't help this.

    The environment was pre-existing before we took control of this, therefore we weren't part of the initial set-up fro, the beginning.

    Again, you guys are doing an amazing job in supporting the community, where I have relied on over the past months, and probably will lurk around going forward too.

    Happy weekend guys! Have one on me! :smileywink:

    :34429
  • 0

    Hello IK,

    thanks for your write-up.

     updating the SQL server before the SEC server [...] the upgrade guide doesn't state any of this

    right, and it doesn't even lists the assumptions under which it is written. But - the upgrade checker (which you've quoted in your initial post) should also have given you a link referring you to the ServerUpgradeChecks section in this article.

    Christian

    :34503