Problem Registering an SQL 7.0 Server in SQL 2000

[Bob Jacobs]

We are running 3 versions of SQL - 6.5, 7.0, and now 2000.
I have all three versions installed on my PC and run Enterprise
Manager to manage the 2000 and 7.0 servers. The one 7.0 server
is registered fine. When I try to register the other 7.0 server
I get the following message -

(SQL DMO) SQL Server xxxx must be upgraded to
version 7.0 or later.

This same server is registered through Enterprise Manager on
another PC running the 3 versions of SQL and both SQL 7.0 servers
work fine on that Enterprise Manager installation.

Any suggestions as to what I need to do to be able to register
the 7.0 server on the Enterprise Manager running on my PC?

[Paul]

having all 3 versions on the same m/c is the problem. even just having 7 & 2000 on the same m/c can cause problems. They are meant to work happily together if installed in different directories but don't forget Microsoft want you to upgrade so they don't make it as nice and easy as perhaps it should be ? Also remember that having all 3 versions on the same m/c can cause registry conflicts afterall they are all SQL Server DB packages by Microsoft.

Lose SQL6.5 if possible.


------------
Bob Jacobs at 2/7/01 9:14:07 AM

We are running 3 versions of SQL - 6.5, 7.0, and now 2000.
I have all three versions installed on my PC and run Enterprise
Manager to manage the 2000 and 7.0 servers. The one 7.0 server
is registered fine. When I try to register the other 7.0 server
I get the following message -

(SQL DMO) SQL Server xxxx must be upgraded to
version 7.0 or later.

This same server is registered through Enterprise Manager on
another PC running the 3 versions of SQL and both SQL 7.0 servers
work fine on that Enterprise Manager installation.

Any suggestions as to what I need to do to be able to register
the 7.0 server on the Enterprise Manager running on my PC?

[Chris Wood]

I think that the problem is more having 2000 and 7 together. Microsoft have said that if you
install 2000 client it will over write 7 client. One thing I have seen is SEM does not forget a
servers information if you have it registered and then change the server in some way. If the
problem server is registered already and cannot be accessed now then un-register it and
re-register it. Otherwise you may have to use theclient network utility to define its connection
different from your standard method.

Chris Wood
Alberta Department of Resource Development
CANADA


------------
Paul at 2/8/01 9:19:57 AM

having all 3 versions on the same m/c is the problem. even just having 7 & 2000 on the same m/c can cause problems. They are meant to work happily together if installed in different directories but don't forget Microsoft want you to upgrade so they don't make it as nice and easy as perhaps it should be ? Also remember that having all 3 versions on the same m/c can cause registry conflicts afterall they are all SQL Server DB packages by Microsoft.

Lose SQL6.5 if possible.


------------
Bob Jacobs at 2/7/01 9:14:07 AM

We are running 3 versions of SQL - 6.5, 7.0, and now 2000.
I have all three versions installed on my PC and run Enterprise
Manager to manage the 2000 and 7.0 servers. The one 7.0 server
is registered fine. When I try to register the other 7.0 server
I get the following message -

(SQL DMO) SQL Server xxxx must be upgraded to
version 7.0 or later.

This same server is registered through Enterprise Manager on
another PC running the 3 versions of SQL and both SQL 7.0 servers
work fine on that Enterprise Manager installation.

Any suggestions as to what I need to do to be able to register
the 7.0 server on the Enterprise Manager running on my PC?

[Bob Jacobs]

Thanks to each of you for your replies to my problem.
I wish it were as simple as upgrading the older versions of SQL but
because of the software running on each server that can't be done
until the software vendors upgrade their packages.

I was able to get the SQL 7.0 server registered on the 2000 MMC. I
uninstalled both SQL 2000 and 7.0 from the PC having the problem -
deleting some remaining directories that weren't cleared when the
uninstall ran and then reinstalled first SQL 7 and then SQL 2000 and
the SQL 7 server could then be registered. I'm not sure what was unique
about the 7.0 server in question because we have another 7.0 server
and were able to register it correctly from the start.

Anyway, thanks so much for your advice and support.

Bob Jacobs

------------
Paul at 2/8/01 9:19:57 AM

having all 3 versions on the same m/c is the problem. even just having 7 & 2000 on the same m/c can cause problems. They are meant to work happily together if installed in different directories but don't forget Microsoft want you to upgrade so they don't make it as nice and easy as perhaps it should be ? Also remember that having all 3 versions on the same m/c can cause registry conflicts afterall they are all SQL Server DB packages by Microsoft.

Lose SQL6.5 if possible.


------------
Bob Jacobs at 2/7/01 9:14:07 AM

We are running 3 versions of SQL - 6.5, 7.0, and now 2000.
I have all three versions installed on my PC and run Enterprise
Manager to manage the 2000 and 7.0 servers. The one 7.0 server
is registered fine. When I try to register the other 7.0 server
I get the following message -

(SQL DMO) SQL Server xxxx must be upgraded to
version 7.0 or later.

This same server is registered through Enterprise Manager on
another PC running the 3 versions of SQL and both SQL 7.0 servers
work fine on that Enterprise Manager installation.

Any suggestions as to what I need to do to be able to register
the 7.0 server on the Enterprise Manager running on my PC?