You try to install a secondary site in Systems Management Server 2003, but the secondary site remains in the "Install Pending" state (915386)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

When you try to install a secondary site in System Management Server (SMS) 2003, the secondary site remains in the "Install Pending" state. Additionally, the secondary site cannot communicate with the primary site.

Moreover, when you try to view the Sender.log file, you receive error messages that are similar to the following error message:
There is no existing connection, Win32 error = 5 DateTime 3548 (0x0DDC)
Error during connection to \\ComputerName.DomainName.com\SMS_SITE (5). DateTime 3548 (0x0DDC)
Error is considered fatal. DateTime 3548 (0x0DDC)
FQDN for server ComputerName is ComputerName.DomainName.comDateTime 3136 (0x0C40)
There is no existing connection, Win32 error = 5 DateTime 5852 (0x16DC)
There is no existing connection, Win32 error = 53 DateTime 3136 (0x0C40)
There is no existing connection, Win32 error = 53
Note You can view the Sender.log file by using the SMS Tracer tool. To do this, click View, click Filter, and then click Filter by Component. This will let you selectively view the log output that is produced by a particular sender type.

CAUSE

This problem usually involves the Domain Name System (DNS) suffix search order. The DNS suffix seach order is located in the TCP/IP properties of the secondary site server. The fully qualified domain name (FQDN) for the target domain must be listed at the top of the suffix search list on the secondary site server. If the FQDN for the target domain is not at the top of the search list, the Kerberos authentication of the secondary site computer account will fail. When the secondary site computer account fails authentication, the secondary site cannot be installed into the SMS hierarchy.

RESOLUTION

The FQDN for the target domain must be listed at the top of the suffix search list on the secondary site server. To change the suffix search list, follow these steps:
  1. Click Start, click Run, type ncpa.cpl, and then click OK.
  2. Right-click the connection that you want to change, and then click Properties.
  3. In the Connection Name Properties dialog box, select Internet Protocol (TCP/IP) under This connection uses the following items, and then click Properties.
  4. On the General tab, click Advanced, and then click the DNS tab.
  5. Click Append these DNS suffixes (in order), click the target domain, and then move the target domain to the top of the list by clicking the UP ARROW.
  6. Click OK two times, and then click Close.

STATUS

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

MORE INFORMATION

For more information about how to configure domain suffix search lists, click the following article numbers to view the articles in the Microsoft Knowledge Base:

275553 How to configure a domain suffix search list on the Domain Name System clients

294785 New group policies for DNS in Windows Server 2003

Modification Type:MinorLast Reviewed:6/20/2006
Keywords:kbExpertiseAdvanced kbtshoot kbDirServices kbSMSSender kbSMSInstall kbprb KB915386 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.