Hi,
I hope there is some body arround here to solve my problem.
After reinstalling SQL server 2005 I got this message:
Your SQL Server installation is either corrupt or has been tampered with ( Error getting Instance ID From name).
Please uninstall, then re-run stetup to correct this problem.
There are also 51 setup log files in: Setup/Boostrap/Log/files/
Can Ido that manually? Or is there another way to solve this problem.
Henk
I would suggest that your first step is to examine the set of logs from your most recent attempt to seek more informaton about a specific error that we can troubleshoot. If that fails, there is a KB article that discusses removing SQL 2005 from your computer, you can find it at http://support.microsoft.com/kb/909967.
Mike
|||Thanks for answering.
Uninstalled everything, I suppose, but after reinstalling I got the same message on setup
Sql Server Database Services. Installation fails. See log.
It says go to:
http;//www,microsoft.com/products/ee/transform.aspx?prodname=Microsoft+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtId=29503&EvtType=sqlsetuplib%5cservice.cpp%40D0=sqlShutDownRANUInstance%40sqls%3a%3aService%3a%3aStart%40x41d.
Reading Summary.txt it says:
Error number (1053)
Error number 29503
But I found nothing there.
Question: Where can I find the error inI the log file? It's that immense big and I am not that experienced.
Comparing the registry with a working machine and the machine that fails, there are some od differences.
Such as.
Working machine: One MSSQL.1
Not working Machine: Missing MSSQL.1
One MSSQL.2
One MSSQL.3
To reinstall XP Pro is not an option.
Is there a possibility to rebuild the registery so that is everything new?
Looking for a great answer to solve my problem.
Henk
|||
post back the configuration. OS/SQL Sever version /Edition/Service Pack
Madhu
|||Hi,
Suggest you to use Windows Installer Cleanup Utility to see if their are something that is pending, remove if any and install fresh copy of sql express and report back with findings
|||You can find the logs at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG. Summary.txt will tell you which component failed and give a pointer to the detail log for that component. In the component error log, look for actions with a Return Value of 3, which indicates falure; the information above the return value will indicate what was happening during the failure.
I suggest that you don't use the Windows Installer Cleanup Utility. All this tool does is hack your registry to remove the Uninstall keys for program. It doesn't fix anything and it doesn't correct anything. This tool does have it's uses, but not in this case.
Mike
|||Madhu K Nair,
Thanks for answering.
OS Version: Windows XP Professional Service Pack 2 (Build 2600)
Microsoft SQL Server 2005 9.00.3042.00
Microsoft SQL Server Setup Support files
Product version: 9.00.3042.00
Install: Successful
Microsoft SQL Server Native Client
Product version: 9.00.3042.00
Install: Successful
Microsoft SQL Server VSS Writer
Product version: 9.00.3042.00
Install: Successful
MSXL 6.0 Parser
Product version: 6.10.1129.0
Install: Successful
SQL Server Database Services
Error: SQL Server can't start.
Last entry:
Product: Microsoft SQL Server 2005 Express Edition
Product Version: 9.2.3042.0
Install failed.
Error string SQL server can't Start
Error is (1053)
Error number : 29503
This is everything in Summary.txt
|||Thanks Mike for answering.
Found return value 3.
The most of the messages are in Dutch.
I try to translate them.
Unable to start service)1053)
Error code: 0x8007041d (1053) Windows error text : The service coul'dn't be started.
Source File Name: sqlsetuplib\service.cpp Compiler. Timestamp: wed Jun 14 16:29:04 2006
Function Name: sqls:: Service:: Start Source Line Number : 316
Context--
Setting status of unmanaged componets and removing unmanaged sources
Error Code: 1053
MSI (s) (3C!08) [20:48:04:375] Product : Microsoft SQL Server 2005 Express Edition. SQL Server-service can't start. See
SQL Server Books Online.
Error 29503. SQL Server can't start.
Hope this will be enough.
Henk van Andel
|||Hi Henk,
1503 seems to be a windows error indicating that you don't have permissions to something on the file system. One more set of logs to investigate I'm afraid.
Check out the SQL error logs that are found at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG and look for the log dated around the time that your setup failed. (It will probably be the last one unless you've fixed this sine then.) Look through the log, it will probably be short since startup failed, for errors indicating that the server couldn't access or open a file or registry key.
Let me know what you find.
Mike
No comments:
Post a Comment