Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2003-02-10 : 06:15:20
|
| One of our server has suddenly popped up the following message after a re-boot:You SQL server installation is either corrupt or has been tampered with ( SQL registry version not the same as Server version). Uninstall and the re-install.Now I think - it's cool, I'll try and rebuild registry. Seems very simple, just run through as if you were installing. BUT - when I get to instance screen, it WON'T allow me to choose default instance. Which means I can't rebuild registry, because you must run exactly as the install was done, and the install was done for default instance.Is this a known problem ? Am I doing something stupid ? Is there a workaround ?SQL 2K (std) SP 2 on Win 2K sP3.I have tried re-running SP2 - does no good - runs through but no joy.ciao*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-10 : 12:13:52
|
| It sounds like you are going to have to completely rebuild SQL Server by starting with an uninstall. |
 |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2003-02-12 : 02:43:32
|
| Well, I have done the uninstall and reinstall of SQL. I'm not too happy about the fact that the rebuild registry refused to allow me to try and rebuild for the default instance! I think most people, due to licencing costs, are going to be running on 1 instance, which is thus likely to be default. If that is true, then issues with rebuild reigstry for default instance is a problem! We have tested it on another machine that was "clean" , and there the rebuild for registry was happy to allow the default instance to be chosen, so potentially the box was broken beyond registry rebuild's ability to fix ...Ciao*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
|
|
|
|
|
|
ugly SQL Server problem ... SQL DOWN