Quantcast
Channel: The Official Configuration Manager Support Team Blog
Viewing all articles
Browse latest Browse all 715

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

$
0
0
KBSymptoms

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

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.

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.

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

=====

For all the details and the latest version of this document please see the following new Knowledge Base article:

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

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002


Viewing all articles
Browse latest Browse all 715

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>