You cannot connect to the site database after you successfully install a site server in Systems Management Server 2003 (886143)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

When you install Microsoft Systems Management Server (SMS) 2003 with advanced security, after the SMS Setup program finishes, you notice the following symptoms:
  • The SMS Administrator console cannot connect to the site database.
  • You find entries that are similar to the following in the driveletter:\Sms\Logs\Adminui.log file:
    [DateTime]:Setting connection to NameSpace: \\1-2SMS\root\sms\site_SiteCode
    [DateTime]:Info(ConnectServer): Connecting to server : namespace \\1-2SMS\root\sms\site_SiteCode
    [DateTime]:Info(ConnectServer): Connecting to server. Network : \\1-2SMS\root\sms\site_SiteCode
    [DateTime]:Wbem call failed: T_WbemSyncEnumToContainer_Core, return code: -2147217389
    [DateTime]:Wbem call failed: T_WbemSyncEnumToContainer_Core, return code: -2147217389
    [DateTime]:Query select SiteCode, SiteName, ServerName, BuildNumber from SMS_Site where ReportingSiteCode="" fails or returns empty resultset. Query select * from SMS_Identification also fails or returns empty resultset
    [DateTime]:Error: Possible UI connection error code is -2147217389[0x80041013]
  • You find entries that are similar to the following in the driveletter:\Sms\Logs\Smsprov.log file:
    [DateTime]: * * FilePath\SspObjectQuery.cpp(5227) : SQL Connection attempt timed out SQL Error: [28000][18456][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. * *
    [DateTime]: * * SQL Connection attempt timed out [28000][18456][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. -- [28000][18456][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. * *
    [DateTime]:CSspClassManager::SQL query failed and returned quickly so sleeping for 20 seconds...

CAUSE

This problem occurs if the Service Principal Name (SPN) for the site database does not exist or is corrupted.

WORKAROUND

To work around this problem, manually configure an SPN for the site database. To manually configure an SPN for Microsoft SQL Server, follow these steps:
  1. Log on to the SQL Server-based server that is hosting the SMS 2003 site database.
  2. Obtain and install the Setspn.exe utility. For information about how to obtain and install the Setspn.exe utility, visit the following Microsoft Web site:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&displaylang=en

  3. Click Start, click Run, and then type a Setspn.exe command in the Open box using the following syntax:

    setspn -A MSSQLSvc/Host:port domainname\serviceaccount

    For example:
    C:\>setspn -A MSSQLSvc/lphbar2.hemlock.com:1433 hemlock\delegation
    In this example, "lphbar2" is the host name of the server that is running SQL Server, "hemlock" is the Microsoft Windows 2000 domain name, and "delegation" is the domain account under which SQL Server is running.

  4. Click OK to run the Setspn.exe utility.

Note If SQL Server runs under the local system account, you do not have to manually configure an SPN for SQL Server. The SPN is created automatically when SQL Server starts. If SQL Server runs under a domain user account, you must manually configure an SPN.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you manually configure an SPN for the server that is hosting the site database, you can use the SMS Administrator console to manage the SMS 2003 site.
Modification Type:MajorLast Reviewed:1/27/2006
Keywords:kbtshoot kbsmsProvider kbSMSInstall kbSMSDeploy kbwinservperf kbMgmtServices kbprb KB886143 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.