April 11, 2007 at 3:15 am
Hi All,
We have a test server running SQL 2005 Standard Edition with 8 named instances installed. All are configured to use windows authentication. When I run through the SP2 installation a message appears saying "Hotfix.exe has encountered a problem and needs to close etc" when I look more closely at the hotfix.log file I see the following error...
04/11/2007 09:19:01.062 Stopping service: SQLAgent$INST1
04/11/2007 09:19:12.265 Stopped service: SQLAgent$INST1
04/11/2007 09:19:12.265 Stopping service: MSSQL$INST1
04/11/2007 09:19:15.296 Stopped service: MSSQL$INST1
04/11/2007 09:19:15.296 Installing file: sqlrun_sql.msp
04/11/2007 09:19:15.296 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
04/11/2007 09:19:15.312 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
04/11/2007 09:19:15.312 Registry: Cannot read registry key value "Debug"
04/11/2007 09:21:41.593 MSP Error: 29534 Service 'MSSQL$INST1' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
04/11/2007 09:21:50.718 MSP returned 1603: A fatal error occurred during installation.
I don't understand why it can't start the MSSQL$INST1 service. The domain administrator account was verified against each instance as part of the SP2 install. It's got to be something straightforward but just can't see it!
Any ideas?
April 12, 2007 at 7:55 am
What does the SQL ERRORLOG file show for the attempted start. Also, is there anything relevant in the Windows System or Application Event Logs?
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 12, 2007 at 12:01 pm
check your c:\winnt\registration folder security properties. WU messes them up
April 13, 2007 at 9:16 am
Guys,
Thanks for your replies. Upon further investigation the SQL Server log file was suggesting that the systemresource db was either corrupt or could not be accessed.
I had split the mdf's and ldf's onto different physical disks (including all system db's) so when I came to install SP2 I found it had recreated the systemresource data files on the same drive as the existing .mdf. As the -l parameter ws pointing to a different physical location for the log file the mssql service wouldn't start!
Anyway, to cut a long story short i've decided not to split the systemresource files and to leave them in their default location.
Thanks for replying to my original post.
April 13, 2007 at 9:29 am
I had the same issue. It looks like the SP2 install places a new version of the Resource DB and distmdl in the same folder where master.mdf is located. BOL does say that the Resource DB should be in this folder, I now know why!
As a result, our SQL 2005 build standard has been changed to say the the Resource DB and distmdl mdf and ldf files must be placed in the same folder as master.mdf.
The more I deal with the Resource DB, the less I like it. It is not possible to back up this database, but if its files are missing or corrupt SQL will not start! We should be able to take backups of this DB in the same way as any other, and there should be a documented restore process.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 14, 2007 at 1:06 pm
Ed,
It would be nice to keep things tidy. (i.e split all mdf's and ldf's) but obviously this just isn't possible. Thanks for your reply.
I too am looking at producing a standard build for SQL 2005 and I guess we'll adopt the same policy... keep the systemresource data files in the same folder as the master.mdf.
Thanks again for your post.
Mark
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply