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

SEC 4.5 to 4.7 upgrade

1976saint

Hi, has anyone else come across this;

I attempted to upgrade my SOPHOS4.5 SQL2005 database server in my test lab and during the install it failed reporting that it was unable to upgrade the SOPHOS3 database (which was still on the box from our previous step upgrade from 3.1 to 4.0 to 4.5)!

Why it was attempting to do this I don't know but I took the step to do a bit of tidying up and deleted SOPHOS3 and 4 databases leaving only SOPHOS45.


Once deleted I tried the upgrade again but all I was presented with to install was the Sophos Enterprise Console. When I looked at SQL a SOPHOS47 database had appeared I guess from the original upgrade which failed.

Luckily for me this was a VM server that I snap shotted before so I reverted back, deleted the databases again and then installed with just SOPHOS45. The upgrade completed okay this time.

Anyone else come across this as this as a surprise.

:17613


This thread was automatically locked due to age.
  • 0

    Hello 1976saint,

    if you still have the snapshot Support (or QA) might be interested. Not knowing the details it's guesswork why it failed - but it could be that the 4.7 installer got confused when it found the SOPHOS3 database. You said the the upgrades up to 4.5 were without problem? 

    Once deleted I tried the upgrade again but all I was presented with to install was the Sophos Enterprise Console

    The install consists of several steps depending on the components already present. The installer did a rollback when it could not upgrade the database, didn't it? While the rollback removes SEC it will keep the database though if it has already been created. Only finding the SOPHOS45 database this time I think it's likely that the installer would have completed successfully. 

    Christian

    :17615
  • 0

    Hi Christian

    I do have the Snapshot as this is my test rig so if they are interested let me know.

    The installation did roll back and the Sophos47 DB was present in this case. As this server was not the SEC server (only the DB server) I anticipated running the installer again to make sure it completed without errors. On the second pass it only presented me with the SEC install, as you've implied the database was created already so that answers that question but leads to another.

    In this case, I would be able to upgrade my SEC box and it should have been okay?

    Thanks for your quick response.

    :17707
  • 0

    Hello,

    if they are interested let me know

    I'm not affiliated with Sophos :smileyhappy: - so you'd have to ask them yourself.

    In this case, I would be able to upgrade my SEC box and it should have been okay?

    Normally yes, the logic is pretty much the same

    [Edit: I was about to leave yesterday when I posted the answer and I feel I should ass some details and caveats]

    At first I did not glean that you only installed the database (I was not sure and then assumed a full install in my first reply without asking).

    It depends on the state the database was left after the incomplete install. It might have again failed to upgrade. But - the logic is quite robust and the upgrade does not touch the "old" database an can be retried. If it fails again you can manually run UpgradeDB.exe with the -reset switch. Please see also Distributed Enterprise Console installation error, it gives you an idea what the installer does under the covers. It's not as complicated as it seems on first reading and if you feel confident it's usually faster than uninstalling or reverting and doing the install all over.

    Christian

    :17717