 |
| SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005. |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|

April 9th, 2008, 02:39 AM
|
|
Registered User
|
|
Join Date: Apr 2008
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
SP4 Killed SQL Server 2000
I recently upgraded my SQL Server 2000 to SP4. Unfortunately, upon completing the installation my SQL Server has been rendered useless. Whenever I would open Enterprise Manager, it would splash the error "MMC could not create the snap-in". I tried to manually add the snap-in as others had suggested in other questions, however it would give me an error when I would attempt to do so. So I uninstalled SQL Server and reinstalled. However, it did no good, except change the error symptoms. Now when I go into Enterprise Manager, I get the error "Microsoft SQL-DMO - Error 65535: General Error" and then if I try to add a new sql server registration, it gives me the error "Server registration information cannot be changed on remote Registries". Now, I cannot even uninstall, for if I try, it complains that "The log file 'C:\Program Files\Microsoft SQL Server\80\Tools\Uninst.isu' is not valid or the data has been corrupted. Uninstallation will not continue."
Thanks in advance for any help with reviving my system.
|
|

April 9th, 2008, 05:02 AM
|
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 15
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Try installing again as a named instance.
You may have to clean the registry and delete the files. There are third party products which clean the rgistry. Keep a backup of the registry first.
Actually for the problem you faced first, si something common. But to resolve that issue, Dont even jump in for a reinstallation. Re-installation should always the last thing you should do.
G.R.Preethiviraj Kulasingham
|
|

April 9th, 2008, 07:17 AM
|
|
Registered User
|
|
Join Date: Apr 2008
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Thanks for the reply, Preethi.
Unfortunately, even installing again as a named instance does no good. This is rather frustrating, considering that I am trying to use this machine for development.
|
|

April 9th, 2008, 07:39 AM
|
|
Registered User
|
|
Join Date: Apr 2008
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Imar,
I'm not sure what you mean. I'm simply trying to connect to SQL Server through Enterprise Manager.
|
|

April 9th, 2008, 07:55 AM
|
|
Registered User
|
|
Join Date: Apr 2008
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Imar,
I think you misunderstand. I understand how to connect to SQL Server. The issue is that Enterprise Manager is not functioning. I don't even get to a place where I would be able to enter connection information to register my server.
|
|

April 9th, 2008, 08:17 AM
|
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 15
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
I am afraid the only option (Other than format & re-install all) is the remove all the files in the SQL folder and remove the registry entries too.
(This is where you need to use a third party registry cleaner)
Just before that please have a look into this. Some people faced the MMC issue and resolved in different way. I remember you too faced the same problem initially.
http://support.microsoft.com/kb/914157
G.R.Preethiviraj Kulasingham
|
|

April 9th, 2008, 12:22 PM
|
|
Registered User
|
|
Join Date: Apr 2008
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Thanks for the comments, guys.
Ultimately, it looks like I will be formatting during some off time. Oh well.
|
|
 |