Failed MSDE installation - Feedback on posting by Jason Howell

Hi Jason, Hi all,
I have been having an error installing MSDE and discovered a thread in this
newsgroup, which appears to handle the same error.
Specifically, the post http://tinyurl.com/2vtzv by Jason Howell seemed
relevant.
Interestingly, setting BLANKSAPWD=1 did get the installation to complete,
but I was still not able to start the service. This did not really help me.
Now I believe that I have more information , which may be interesting to
others.
The problem appears to be related to the facts that,
- I have the SQL Server 2000 Enterprise Edition client tools installed on my
machine
- I have already installed and deinstalled an MSDE instance with the same
instance name (CS3DB).
I have managed to install a second instance of MSDE using a different
instance name (CS3DBTEST) and this works perfectly.
The problem is clearly related to the instance name CS3DB.
However, although I had unistalled the CS3DB instance, various entries were
left in the registry. These were:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
InstalledInstances=CS3DB CS3DBTEST
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component Set
InstanceComponentSet.1={E09B48B5-E141-427A-AB0C-D3605127224A}
InstanceComponentSet.2={689404D2-1C94-44B3-9203-BEC5594FDA7A}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\CS3DB
...
which all indicate to me that the CS3DB instance had not been removed
properly, and that in some manner or other, there were still two versions
installed. However, the CS3DB instance no longer appeared in the Add/Remove
programs dialog in the control panel.
My suspision is, that is you have the SQL Server 2000 client tools installed
before you install MSDE, then you cannot cleanly remove the first instance
of MSDE.
I have now modified the registry, by:
removing CS3DB from
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\InstalledInstances
deleting
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component Set
InstanceComponentSet.1={E09B48B5-E141-427A-AB0C-D3605127224A}
deleting the related key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\{E09B
48B5-E141-427A-AB0C-D3605127224A}
and deleting the key and subkeys
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\CS3DB
This seems to have down the trick.
I have now reinstalled the MSDE instance CS3DB and it seems to be working.
So again, my guess is that uninstalling MSDE in the presence of the SQL
client tools does not work properly.
Hope this helps somebody and any feedback would be appreciated.
Phil
Hi,
I have now repeated this, as follows:
- uninstall instance CS3DB
- try to reinstall - it fails
- remove registry entries as described before
- try to reinstall - it works.
Phil
|||"Phil Jollans" <nospam@.messring.de> wrote in message
news:2kg1ioF1qnrpU1@.uni-berlin.de...
> Hi,
> I have now repeated this, as follows:
> - uninstall instance CS3DB
> - try to reinstall - it fails
> - remove registry entries as described before
> - try to reinstall - it works.
> Phil
>
This may not be big news to others, but it's a valuable piece of information
to me, as we use MSDE in our labs and classrooms, and many of our students
use it at home in conjunction with Visual Studio .NET. (Next time I have a
student who is having MSDE trouble, I now have one more question/possible
solution to use).
Thanks very much for sharing! It's what makes these groups so valuable.
Peter [MVP Visual Developer]
Jack of all trades, master of none.