Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A System Center Configuration Manager 2007 site fails to upgrade to Service Pack 2


Symptoms

A System Center Configuration Manager 2007 site fails to upgrade to Service Pack 2 and reports SQL Error: The server service principal name already exists.  You may also see the following in the Configmgrsetup.log file:

<MM-DD-YYYY HH:MM:SS> ***SqlError: [42000][15025][Microsoft][ODBC SQL Server Driver][SQL Server]The server principal '<Domain>\Server1$' already exists.
<MM-DD-YYYY HH:MM:SS> SqlExecute < IF NOT EXISTS(SELECT * FROM sys.database_principals dp JOIN sys.server_principals sp ON dp.sid=sp.sid AND dp.name='dbo' AND sp.name='<Domain>\Server3$') BEGIN IF NOT EXISTS(SELECT * FROM master.sys.server_principals where name='<Domain>\Server3$') CREATE LOGIN [<Domain>\Server3$] FROM WINDOWS IF NOT EXISTS(SELECT * FROM sys.database_principals where name='<Domain>\Server3$') CREATE USER [<Domain>\Server3$] EXEC sp_addrolemember 'smsdbrole_MP', '<Domain>\Server3$' END

↑ Back to the top


Cause

This can occur when a server in a site server role is renamed and the SPN's and SQL logins remain associated with the old computer name.

↑ Back to the top


Resolution

1. Remove the <Domain>\<OldServerName> login record from the Configuration Manager database using SQL Management Studio.

2. Remove the old Service Principle Name using ADSIEdit:

  1. Click Start, click Run, and enter adsiedit.msc to launch the ADSIEdit MMC console.
  2. If necessary, connect to the site server's domain.
  3. In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=Users,and right-click CN=<Service Account User>. On the context menu, click Properties.
  4. In the CN=<Service Account User> Properties dialog box, remove the servicePrincipalName value.

3. Add the new, proper SPN using the following command:

setspn –A MSSQLSvc/<SQL Server computer name>:1433 <Domain\Account>.

Note: See How to Configure an SPN for SQL Server Site Database Servers for more information.

4. Run SP2 setup again.  This time it should complete successfully.

↑ Back to the top


More Information

How to Configure an SPN for SQL Server Site Database Servers: http://technet.microsoft.com/en-us/library/bb735885.aspx

Configuration Manager Service Principal Name Requirements: http://technet.microsoft.com/en-us/library/bb735877.aspx

↑ Back to the top


Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2269959
Revision : 1
Created on : 1/18/2017
Published on : 9/16/2010
Exists online : False
Views : 249