RE: SQL Server 2005 faulure when updating to SP1

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi,

Please also download Filemon:
http://www.sysinternals.com/Utilities/Filemon.html

Regmon:
http://www.sysinternals.com/Utilities/Regmon.html

to capture the data when you trying to install updates

Send me the log file v-xuwen@xxxxxxxxxxxxx

Hope I can find something in them.

Thanks.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: SQL Server 2005 faulure when updating to SP1
thread-index: AcaEr51Y8P4xZ0kbT4CXzR35fZrK6g==
X-WBNR-Posting-Host: 66.192.117.190
From: =?Utf-8?B?czAyNWphaw==?= <s025jak@xxxxxxxxxxxxxx>
References: <493DCC1C-60F4-43E8-B859-AAE3643F650F@xxxxxxxxxxxxx>
<#wvXwxsgGHA.1740@xxxxxxxxxxxxxxxxxxxxx>
<D4140A6B-11F4-4136-85F5-CEF91F21FDCD@xxxxxxxxxxxxx>
<U3PsFAJhGHA.5184@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: SQL Server 2005 faulure when updating to SP1
Date: Wed, 31 May 2006 05:42:02 -0700
Lines: 318
Message-ID: <A0511E5F-42E4-4926-9C9D-6070D7EDF81A@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.sqlserver.setup
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.setup:77065
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.setup

Good Morning Vincent,

The local "Administrators" group on the SQL Server has an ACL entry on
every
file under the "Data" directory granting "Full Control" due to permission
inheritence.

Also, I had found the same Microsoft article 918357 but took the stance
that
it did not apply because it specifically states that it's if you are
having a
problem upgrading the "Setup Support Files" and not the database
services,
and SQL Server Express was never installed on this box before SQL Server
2005
Standard.

Any other ideas? Thanks!

- Jason K.

"Vincent Xu [MSFT]" wrote:

Hi Jason ,

I do understand you don't want to re-install SQL 2005. I'll try my
best.
However, please understand we may have to do this at last. As a bottom
line.

I notieced that you said "The local machine's "Administrator" group has
an
entry on the directory " and I'd like to suggest you grant permission
to
Administrator to every file under the directory.

Meanwhile, you can try following hotfix:

http://support.microsoft.com/?id=918357


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader
so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no
rights.
======================================================



--------------------
Thread-Topic: SQL Server 2005 faulure when updating to SP1
thread-index: AcaD7bcOci3rN454RjaKr4bIkRpAAg==
X-WBNR-Posting-Host: 66.192.117.190
From: =?Utf-8?B?czAyNWphaw==?= <s025jak@xxxxxxxxxxxxxx>
References: <493DCC1C-60F4-43E8-B859-AAE3643F650F@xxxxxxxxxxxxx>
<#wvXwxsgGHA.1740@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: SQL Server 2005 faulure when updating to SP1
Date: Tue, 30 May 2006 06:34:02 -0700
Lines: 235
Message-ID: <D4140A6B-11F4-4136-85F5-CEF91F21FDCD@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.sqlserver.setup
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.setup:77041
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.setup

Vincent,

I realize what the errors that the Service Pack log is reporting but
they
seem incorrect. When I first found the section in the log file with
the
information, the first thing I did was to check the ACLs of the
"C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" directory and every
file
under
it. The local machine's "Administrator" group has an entry on the
directory
and each file granting "Full Control" along with the Local Windows
SQL
Server
group "SQLServer2005MSSQLUser$<server name>$MSSQLSERVER".

When installing the Service Pack, the Indexing Service is disabled
and I
have stopped the Antivirus service when I try the Service Pack
installation.
I believe that this is a bug as several users are experiencing the
same
problem and am confident that if others looked in their logs they
would
see
similar if not the same errors.

The other problem encountered when the service pack is rolling back
the
changes to the "Database Services" is that it doesn't put the user
account
back in the "SQLServer2005MSSQLUser" & "SQLServer2005SQLAgentUser"
local
groups keeping the services rom restarting since we designate a
certain
account to run under. Once the service pack is complete, I have to
go
back
to each group and add the user account and start the services
manually.

I have found others stating that the only course of action is to
backup
all
databases, uninstall SQL Server, re-install SQL Server, and restore
the
databases. I just want to voice my opinion that this is not a viable
option
and an appropriate solution needs to be found as this is an issue for
a
large
user base.

Your help and assistance is greatly appreciated!

- Jason K.

"Vincent Xu [MSFT]" wrote:

Hi ,

From the error log, it clearly indicates that there are issue with
setting
permission for the files under data folder.Setup was doing ACL on
the
following directory recursively down to each file. Please check the
ACL
of
the files under C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data
Please try to grant "Administrators" full permission to each of
those
files, and run SP1 again. It should be fine.

Also, please want to try to turn off the Indexing Service and your
anti-virus scanner and restarting. It is a recommendation that
disable
scanning file applications during the SQL installation?

Hope the information helps.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your
newsreader
so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no
rights.
======================================================



--------------------
Thread-Topic: SQL Server 2005 faulure when updating to SP1
thread-index: AcaBBxPsd15VhXHLT8+HD77VQoIung==
X-WBNR-Posting-Host: 66.192.117.190
From: =?Utf-8?B?czAyNWphaw==?= <s025jak@xxxxxxxxxxxxxx>
Subject: SQL Server 2005 faulure when updating to SP1
Date: Fri, 26 May 2006 13:58:02 -0700
Lines: 115
Message-ID: <493DCC1C-60F4-43E8-B859-AAE3643F650F@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.sqlserver.setup
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.setup:77018
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.setup

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.


.

Relevant Pages

  • Re: upgrading cluster hardware
    ... The install process puts RTM binaries on the new node. ... be updated with any service packs or hotfixes you ran. ... Microsoft SQL Server MVP ... > Do I have to install the service pack again? ...
    (microsoft.public.sqlserver.clustering)
  • Re: SBS03 SP2; SQL Server 2k upgrade to 05 SP2 help please
    ... Service Pack 2; like I mentioned that I saw from Control Panel/System. ... I find Sql Server Mgmt Studio, connect and create a db without a problem. ... Server Management Studio" to your SQL install? ... My PROBLEM is that BCM Database Manager will not create a database. ...
    (microsoft.public.windows.server.sbs)
  • Provider not found (Unspecified Error)
    ... You have installed service pack for SQL Server. ... Analysis Services in addition to service pack for Sql ... >I don't know what more I have to install after ...
    (microsoft.public.sqlserver.olap)
  • Re: SQL Server CE Server Tools installation Error ...
    ... > You need to install the version of SQL CE tools that matches the> version of the servcie pack you have applied to SQL Server, which> is service pack 3. ... >> "SQL Server CE Server Tools is compatible only with SQL Server 2000>> Service ...
    (microsoft.public.sqlserver.ce)
  • RE: SQL Server 2005 faulure when updating to SP1
    ... The local "Administrators" group on the SQL Server has an ACL entry on every ... When installing the Service Pack, the Indexing Service is disabled and I ... Please check the ACL ... The installation continues and then at the end states that everything ...
    (microsoft.public.sqlserver.setup)