SQL Server 2005 faulure when updating to SP1
- From: s025jak <s025jak@xxxxxxxxxxxxxx>
- Date: Fri, 26 May 2006 13:58:02 -0700
This is going to be a long one. I know there have been several posts in the
Microsoft newsgroups and other blogs and newsgroups on the web, but I haven't
seen any yet that can answer the problem that a lot of people are having with
the 'Database Services' not getting upgraded. I decided to do some digging
in the rather large and cryptic log files generated by the service pack
install and believe that I have found the pertinent information, but can't
figure out the resolution to the problem as I don't understand why it is a
problem. Hopefully all of the information I have gathered will help in
getting this issue resolved finally.
During the install, users that are having this same problem get the an error
message that the service pack was unable to install. If you have error
reporting turned on and choose to see the information that will be submitted
to Microsoft, the thirs line in the "Error signature" section says the
following:
"_depot_sqlvault_setupmain_setup_sqlse_sqlsedll_copyengine.cpp - 856".
The installation continues and then at the end states that everything was
successfully upgraded except for the 'Database Services' and that you can
look at the log files for more details. The log files that I believe had the
key information to the problem are the following:
1- "C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090.log"
2- "C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log"
The line numbers and timestamps will be different for everyone, but this is
how mine look. If you look at Log #1, you'll see a gap in the time sequence
from Line 167 to 168 (The beginning of the line after the timestamp says "MSP
returned 1603"). You take that gap in the time sequence and find the
approximate point in Log #2 where the sequence starts and start going over
every line until you get down to Line 36629 which is where things start to
fail. This was very tedious, but led me to what I believe is the root of the
problem. The excerpt from Log #2 below goes from Line 36629 to 36686.
**********************
Configuring ACL:
Object: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
ACL: (A;OICI;FA;;;[SQLServer2005MSSQLUser$TAMSOHDC19872$MSSQLSERVER])
Action: 0x103
Failed ACL:
SetSecurityFileDescriptor is failed at the error code 5; Converted SDDL:
'(A;OICI;FA;;;S-1-5-21-3626100450-2051294516-1571732110-1007)'
Error Code: 0x80077342 (29506)
Windows Error Text: Source File Name: sqlca\sqlsddlca.cpp
Compiler Timestamp: Tue Jan 10 13:41:21 2006
Function Name: ExceptionInSDDL
Source Line Number: 65
---- Context -----------------------------------------------
Setting status of unmanaged components and removing unmanaged resources
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
Error Code: 29506
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Transforming table Error.
MSI (s) (40!C4) [10:23:50:541]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40!C4) [10:23:50:541]: Product: Microsoft SQL Server 2005 -- Error
29506. SQL Server Setup failed to modify security permissions on file
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user kinderj.
To proceed, verify that the account and domain running SQL Server Setup
exist, that the account running SQL Server Setup has administrator
privileges, and that exists on the destination drive.
Error 29506. SQL Server Setup failed to modify security permissions on file
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user kinderj.
To proceed, verify that the account and domain running SQL Server Setup
exist, that the account running SQL Server Setup has administrator
privileges, and that exists on the destination drive.
<Failure Type='Fatal' Error='29506'>
<EndFunc Name='LaunchFunction' Return='29506' GetLastError='0'>
MSI (s) (40:68) [10:23:50:557]: User policy value 'DisableRollback' is 0
MSI (s) (40:68) [10:23:50:557]: Machine policy value 'DisableRollback' is 0
Action ended 10:23:50: InstallFinalize. Return value 3.
**********************
I have gone over all of the permissions in the directory structure with no
luck and can not find a problem. I have tried the Local Administrator,
Domain Administrator, and other users with Administrative privileges but the
installs fails with the same error all of the time.
Sorry this was such a long post, but I wanted to put the extra information
out there to try and get this problem resolved especially since this is on
our production database server the same as other users.
- Jason K
.
- Follow-Ups:
- RE: SQL Server 2005 faulure when updating to SP1
- From: Vincent Xu [MSFT]
- RE: SQL Server 2005 faulure when updating to SP1
- Prev by Date: Re: Small Business Server and SQL Server 2005
- Next by Date: RE: Sql 2005 License Mode
- Previous by thread: Install SQL Server 2005 silently
- Next by thread: RE: SQL Server 2005 faulure when updating to SP1
- Index(es):
Relevant Pages
|
