January 5, 2008 at 7:13 pm
Hi
I'm trying to install MSDE 2000 on my WIN XP machine using the setup.exe, but it always gives me error saying "The Instance name specified is invalid", after the message " Please Wait while windows configures Microsoft SQL Server Desktop Engine"
I also tried installing it by command line command below, it shows that its configuring and installing software, but disapeears in the middle. I see the folders inside C:\Program Files\Microsoft Sql Server folder, but its still not listed in the installed programs
msiexec /i sql2000.msi /log exception.log instancename="imalla
" securitymode=sql sapwd="sapassword"
Your help would be greatly appreciated
Thanks
January 5, 2008 at 8:00 pm
If you stopped in the middle of an installation or uninstall an existing one, you may have to reboot your machine to install a new one.
January 5, 2008 at 8:07 pm
It didn't stop in the middle. It has happened couple of times, that the installation window just disappears. and even after reboot, I'm not able to see sql installed.
Thanks
January 5, 2008 at 8:10 pm
Can you install it now?
January 5, 2008 at 8:15 pm
But how do u want me to install? Is the command mentioned by me correct? So you want me to try installing by executing the same command again?
January 5, 2008 at 8:43 pm
That is what I mean. You can try to install either from the command line or from setup.exe on your Windows. If it still fails, please check your installation log and see what you can get.
January 8, 2008 at 12:27 am
Yes, I tried again using command line, It again opens the Configuring MS sql server windows, and aftersometime disappears. SQL agent service is installed in services, and C:\Program Files\Microsoft SQl server has the Bin, Data, Install and Log folder installed.
But SQL server not installed.
Below is what was logged in Errorlog in Log folder ( I gave instance name as imalla, and my computer name is imallaw2)
[font="Courier New"]2008-01-07 23:19:08.14 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2008-01-07 23:19:08.15 server Copyright (C) 1988-2002 Microsoft Corporation.
2008-01-07 23:19:08.15 server All rights reserved.
2008-01-07 23:19:08.15 server Server Process ID is 3688.
2008-01-07 23:19:08.15 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$IMALLA\LOG\ERRORLOG'.
2008-01-07 23:19:08.19 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2008-01-07 23:19:08.71 server SQL Server configured for thread mode processing.
2008-01-07 23:19:08.72 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2008-01-07 23:19:08.87 spid3 Warning ******************
2008-01-07 23:19:08.87 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2008-01-07 23:19:08.91 spid3 Starting up database 'master'.
2008-01-07 23:19:09.54 server Using 'SSNETLIB.DLL' version '8.0.766'.
2008-01-07 23:19:09.55 spid5 Starting up database 'model'.
2008-01-07 23:19:09.65 spid3 Server name is 'IMALLAW2\IMALLA'.
2008-01-07 23:19:09.65 spid3 Skipping startup of clean database id 5
2008-01-07 23:19:09.65 spid3 Skipping startup of clean database id 6
2008-01-07 23:19:09.65 spid3 Starting up database 'msdb'.
2008-01-07 23:19:10.21 spid5 Clearing tempdb database.
2008-01-07 23:19:10.92 spid5 Starting up database 'tempdb'.
2008-01-07 23:19:10.98 server SQL server listening on Shared Memory.
2008-01-07 23:19:10.98 server SQL Server is ready for client connections
2008-01-07 23:19:11.10 spid3 Recovery complete.
2008-01-07 23:19:11.10 spid3 SQL global counter collection task is created.
2008-01-07 23:19:11.13 spid3 Warning: override, autoexec procedures skipped.
2008-01-07 23:19:20.88 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
[/font]
January 8, 2008 at 1:22 pm
You may check if you can start your SQL Service from the services console. Check if you can use an account to start it.
It may also happens because of improper uninstallation. An improper uninstallation left unclean registry on your machine. In order to fix this issue, you may read the article in the following link,
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=79343&SiteID=1
Please pay more attention to the comment chain at the end.
Here is another link, which may be helpful.
http://support.microsoft.com/kb/312995
You need to follow the procedures carefully to remove the registry of SQL. Then, re-install it.
Best luck.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply