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

Problem upgrading to EC4.5 -> sql version 2000

otasseron

Hi all,

I am upgrading from Enterprise Console 3.0 to 4.5. I followed the advisory, but are running into a problem now.

Initially the enterprise console and database were on the same machine. msde 2000.

I did the following steps:

1> Move db to sql 2005 instance ( part of sql 2005 cluster)

2> Adjust registry keys to connect EC to database

= These steps worked as I could manage my installation and clients

3> Install EC 4.02 on db server...(fill db later)

4> Install EC 4.02 on EC server

5>ran upgradedb -sourceVersion=3

= Enterprise console did the conversion and is working.

6> Install EC 4.5 on db server (fill db later)

When I try to install EC 4.5 on the EC server, I get an error saying that the installer cannot continue because sql version 2000.

I checked the compatibility mode of the database. This is version "90". (sql2005)

I stopped the instance of msde on the EC server

What can I do more to complete the upgrade?

Any help would be appreciated.

Kind regards,

Oscar Tasseron

:9953


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

    HI,

    So you changed the key:

    hklm\software\[wow6432node]\sophos\ee\management tools\database installer\instance

    to contain the name of the new SQL instance?  If it's a no-named instance you put in MSSQLSERVER.

    You also changed the:

    hklm\software\[wow6432node]\sophos\ee\management tools\databaseconnectionms

    to reference the new database locations and the management service starts ok and SEC is fine.

    I would suggest uninstalling the MSDE instance that is on the management server.  I assume it was a SOPHOS named instance purely for the use of Sophos?

    Regards,

    Jak

    :9957
Reply
  • 0

    HI,

    So you changed the key:

    hklm\software\[wow6432node]\sophos\ee\management tools\database installer\instance

    to contain the name of the new SQL instance?  If it's a no-named instance you put in MSSQLSERVER.

    You also changed the:

    hklm\software\[wow6432node]\sophos\ee\management tools\databaseconnectionms

    to reference the new database locations and the management service starts ok and SEC is fine.

    I would suggest uninstalling the MSDE instance that is on the management server.  I assume it was a SOPHOS named instance purely for the use of Sophos?

    Regards,

    Jak

    :9957
Children
No Data