By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,917 Members | 1,305 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,917 IT Pros & Developers. It's quick & easy.

Help! Sql Server 2005 kicked my Sql Server 7's You-Know-What

P: n/a
Life is not good.

So I've got a machine that I do some development work on, nothing
major, but I'd like to keep some things intact. I'm running SQL Server
7, it's an old installation, but it works and I've got a number of
databases on it.

So I see the new 2005 Express downloads and I download the Web
Developer edition, install it, it installs 2005, but my SQL Server 7
installation now seems to be hosed.

The SQL Server Service Manager still shows SQL Server 7 starting and
running, but the Enterprise Manager can no longer connect, it gives a
vague "General Error" message even though the sqlservr.exe process is
still running. It was not able to connect upon installing the other
products.

I've de-installed the new Express stuff and now just have my trusty
VS2003 installation. Everything seems fine except nothing can talk to
the database, which makes sense since the database now doesn't even
show up on the Enterprise Manager. The Application node of the Event
Log shows no errors coming from SQLServer. But when I try to connect
or re-register a database I get: "Server registration information
cannot be changed on remote registries"

Nothing like this has even vaguely happened to me before. Is there
anyone with any constructive advice? I'd be grateful.

Peace,
Greg McClure
Jul 20 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
I suspect this is down to a DMO error, SQL Express installs a new version of
DMO and when it uninstalls DMO is de-registered but it does not put back the
old one.

try the following:

regsvr32 SQLDMO.dll you can find the file in the SQL Server 7 directory.

-Euan

"Greg McClure" <gm******@gmail.com> wrote in message
news:9a**************************@posting.google.c om...
Life is not good.

So I've got a machine that I do some development work on, nothing
major, but I'd like to keep some things intact. I'm running SQL Server
7, it's an old installation, but it works and I've got a number of
databases on it.

So I see the new 2005 Express downloads and I download the Web
Developer edition, install it, it installs 2005, but my SQL Server 7
installation now seems to be hosed.

The SQL Server Service Manager still shows SQL Server 7 starting and
running, but the Enterprise Manager can no longer connect, it gives a
vague "General Error" message even though the sqlservr.exe process is
still running. It was not able to connect upon installing the other
products.

I've de-installed the new Express stuff and now just have my trusty
VS2003 installation. Everything seems fine except nothing can talk to
the database, which makes sense since the database now doesn't even
show up on the Enterprise Manager. The Application node of the Event
Log shows no errors coming from SQLServer. But when I try to connect
or re-register a database I get: "Server registration information
cannot be changed on remote registries"

Nothing like this has even vaguely happened to me before. Is there
anyone with any constructive advice? I'd be grateful.

Peace,
Greg McClure

Jul 20 '05 #2

P: n/a
"Euan Garden" <eu*********@hotmail.com> wrote in message news:<Z6OFc.22019$Oq2.12415@attbi_s52>...
I suspect this is down to a DMO error, SQL Express installs a new version of
DMO and when it uninstalls DMO is de-registered but it does not put back the
old one.

try the following:

regsvr32 SQLDMO.dll you can find the file in the SQL Server 7 directory.


Yup, this did it, mostly. Thank you, I appreciate your help!
Enterprise Manager still isn't quite behaving the way it used to. It
doesn't show the database "coming on" after a moment and I have to
force it to connect. But it does connect and at least I can access my
databases, so this was a huge help.

I suppose it's likely there are some other DLLs that were unregistered
and that need to be re-registered, so I'll check that possibility out
and perhaps my old functionality will be restored.

Thanks for your guidance.
Jul 20 '05 #3

P: n/a
Thank you Euan-

I was facing the same symptoms and your fix resolved my problem.

Much appreciated!

-SplitDiff
Jul 20 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.