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

    Hi,

    I Put the name of the instance in the value Instance.

    I haven't installed the msde version of sql  because there was also another instance on this MSDE. I checked it and stopped both running instances. but I am not sure if I could deinstall it. Have to investigate it further....

    I don't see an installation of msde in add/remove programs either.

    Tnx for your reply.

    Regards,

    Oscar 

    :9959
  • 0

    When you do move the database, you should really run the installer again on the management server machine and then uncheck the database role.  This will then force the installer to re-ask, where the database is, which will update the registry keys mentioned above.  Maybe that should be done.  I suspect that the MSDE instance is not showing as it was installed with SEC.

    Maybe have a look through he following registry key for the string "SQL Server Desktop Engine" or even just SQL:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

    Maybe a registry key such as:
    NoRemove (no this exactly but there are keys such as NoModify, NoRemove, NoRepair etc)

    is set or there is one to hide it from Add or remove programs.

    I don't have an install handy to check.

    The other approach is to run the install with Process Monitor running and use that to see how it's detecting the instance of MSDE.

    Regards,

    Jak

    :9961
  • 0

    Hi Jak,

    Tnx for your suggestions. I changed the installation and removed database.

    After this I was able to install 4.5.

    everything is working now.

    the only thing is that after starting Enterprise console give the message that EM Library is still running in the updating hierarchy. But maybe this is a normal message.

    I have to resolve this.

    Thanks again and have a nice weekend.

    Regards,

    Oscar

    :9963
  • 0

    Glad it's ok. Uninstalling the database role should really be done as it is this action which remove the database feature from the install.


    The Upgrade Advisor obtains from MSI the features installed.  If it finds that the database feature is installed but the database is remote then it will suspect something is not how it should be.  The "Database location" check int the UGA will fail this condition.

    Regards,
    Jak

    :10279