Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 957008 - Last Review: August 27, 2008 - Revision: 2.1
SQL Server 2005 Service Pack 2 is not successfully updated when you try to install or to uninstall security update KB948108 or security update KB948109
SYMPTOMS
When you try to install the July 2008 security update for Microsoft SQL Server 2005 Service Pack 2 (security updates KB948108 and KB948109), Microsoft SQL Server 2005 is not successfully updated. Additionally, when you try to uninstall the security update, the security update is not uninstalled.
CAUSE
This issue occurs because the rollback process for security updates KB948108 and KB948109
incorrectly removes the SQL Server 2005 service accounts from the respective local SQL Server service
groups. The permissions are granted to local service groups
and not to the service accounts. Therefore, the services cannot access the required
resources, and the services cannot start.
RESOLUTION
To resolve this issue, follow these steps:
- Identify the SQL Server 2005 service group that is located on your
computer. To do this, follow these steps:
- Click Start, click
Run, type compmgmt.msc, and then press
ENTER.
- Expand Local Users and Groups, and
then click Groups.
- The SQL Server 2005 service group starts with "SQLServer2005." Identify each group, and then double-click to determine the group membership. If the group membership is empty, go to step 3. If the group membership is not empty, check the next group.
- In the Services Microsoft Management Console (MMC) snap-in, determine the service account for the SQL Server 2005
services.
To open the Services snap-in, click
Start, click Run, type
services.msc, and then press ENTER. - The names of SQL Server services start with "SQL Server." For example, "SQL Server (MSSQLSERVER)" is a SQL Engine service for the default instance of SQL Server. To determine whether this service is from SQL Server 2005, follow these steps:
- Right-click the service, and then click Properties.
- Locate the program file of this service. This file is shown in the Path to executable area.
- Right-click the file name, the properties, and the version. The file version should begin with either "9.0" or "2005.90."
- In the Computer Management MMC snap-in, double-click the service group name that you located in step 2. Determine whether the service account entry is missing in the service group. If
the service account entry is missing, click Add, type the
service account name in the Enter the object name to select
dialog box, and then click OK.
Note To open the Computer Management MMC snap-in, click
Start, click Run, type
compmgmt.msc, and then press ENTER. - In the Services MMC snap-in, start the SQL Server services.
Note To
open the Services snap-in, click Start, click
Run, type services.msc, and then press
ENTER.
MORE INFORMATION
The Microsoft SQL Server 2005 Setup program creates a local
Windows group for each service that you install. The created Windows group is
called a "service group."
The SQL Server 2005 Setup program adds the service
account for each service to its respective group. All the Windows NT permissions that are required by a specific SQL Server service are granted to
each Windows group.
These groups simplify the permission-granting process that is
required to run SQL Server services and other executables. These groups also help secure SQL
Server files. The SQL Server services access the Windows resources and SQL Server resources
through the service group membership.
The following services and
service groups are created during the SQL Server 2005 setup process.
Collapse this tableExpand this table
| SQL Server service
| Service group |
|---|
| SQL Server | Default instance:
SQLServer2005MSSQLUser$ComputerName$MSSQLSERVER
Named
instance:
SQLServer2005MSSQLUser$ComputerName$InstanceName |
| SQL Server Agent | Default instance:
SQLServer2005SQLAgentUser$ComputerName$MSSQLSERVER
Named instance:
SQLServer2005SQLAgentUser$ComputerName$InstanceName |
| Analysis Services | Default instance:
SQLServer2005MSOLAPUser$ComputerName$MSSQLSERVER
Named instance:
SQLServer2005MSOLAPUser$ComputerName$InstanceName |
| Reporting Services | Default instance:
SQLServer2005ReportServerUser$ComputerName$MSSQLSERVER
and
SQLServer2005ReportingServicesWebServiceUser$ComputerName$MSSQLSERVER
Named instance:
SQLServer2005ReportServerUser$ComputerName$InstanceName
and
SQLServer2005ReportingServicesWebServiceUser$ComputerName$InstanceName |
| Notification Services | Default or named instance:
SQLServer2005NotificationServicesUser$ComputerName |
| Integration Services | Default or named instance:
SQLServer2005DTSUser$ComputerName |
| Full-Text Search | Default instance:
SQLServer2005MSFTEUser$ComputerName$MSSQLSERVER
Named instance:
SQLServer2005MSFTEUser$ComputerName$InstanceName |
| SQL Server Browser | Default or named instance:
SQLServer2005SQLBrowserUser$ComputerName |
| SQL Server Active Directory Helper | Default or named
instance:
SQLServer2005MSSQLServerADHelperUser$ComputerName |
For more information about how to set up Windows service accounts, visit the following Microsoft Web site:
APPLIES TO
- Microsoft SQL Server 2005 Service Pack 2, when used with:
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Express Edition with Advanced Services
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Developer Edition for Itanium-based Systems Community Technology Preview
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems Community Technology Preview
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
| kbexpertiseinter kbfix kbbug kbsecvulnerability kbsecurity kbqfe kbpubtypekc KB957008 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please