Secondary site does not communicate with parent sites in Systems Management Server 2.0 (889431)
The information in this article applies to:
- Microsoft Systems Management Server 2.0
SYMPTOMSIn a multi-tiered hierarchy, you notice the following symptoms: - SNI files accumulate in the driveletter:\Sms\Inboxes\despoolr.box\receive folder on the secondary site server.
- You find entries that are similar to the following entries in the Despool.Log file:
CPublicKeyLookup::CPublicKeyLookup("SiteCode") $$<SMS_DESPOOLER><DateTime><ThreadID>
Cannot find public key for instruction
D:\SMS\inboxes\despoolr.box\receive\FileName.Ist coming from site SiteCode, retry it
later $$<SMS_DESPOOLER><DateTime><ThreadID>
Will retry instruction D:\SMS\inboxes\despoolr.box\receive\FileName.Ist RetryCount more
times, the next retry is in about 40 minutes $$<SMS_DESPOOLER><DateTime><ThreadID> - Collection membership and other inventory information for secondary site collections is not updated in the parent site database.
CAUSEThis issue occurs if the secondary site server does not have public keys for the parent site that the secondary site server wants to send status information to.RESOLUTIONTo resolve this issue, create the key files for the secondary site server on the parent site server where the secondary site is trying to send status information, and then install the key file on the secondary site. To do this, follow these steps: - On the parent site server, click Start, click Run, type cmd in the Open box, and then click OK.
- Change to the folder that contains the SMS 2.0 Hierarchy Maintenance Utility (Preinst.Exe). To do this, click Start, click Run, type cd \sms\bin\i386 in the Open box, and then click OK.
Note You can install Preinst.exe from the SMS Recovery Tools, or it is installed when you apply SMS 2.0 Service Pack 5 (SP5). If you have applied SMS 2.0 SP5, Preinst.exe is contained in the driveletter:\Sms\Bin\I386 folder. If you have installed the SMS Recovery Tools, PreInst.exe is also located in the driveletter:\Program Files\Sms 2.0 Recovery Tools\Bin\I386 folder. - Type the command to export all parent site public keys into a file that is named SiteCode.Ct7. The command to do this is similar to the preinst /parentkeys command.
- The SiteCode.Ct7 file is created in the root folder of the current drive. Copy the SiteCode.Ct7 file that you just created to the secondary site's driveletter:\Sms\Inboxes\Hman.Box folder.
- Wait until the SMS_Hierarchy_Manager thread of the SMS_EXECUTIVE service on the secondary site server has processed the Ct7 file. To do this, wait until you receive an entry that is similar to the following entry in the driveletter:\Sms\Logs\Hman.Log file:$$<SMS_HIERARCHY_MANAGER><DateTime><ThreadID>
Processing C:\SMS\inboxes\hman.box\ParentSiteCode.CT7 file, containing NumberOfKeys keys. $$<SMS_HIERARCHY_MANAGER><DateTime><ThreadID>
CPublicKeyLookup::UpdateCurrentKey("ParentSiteCode", "PublicKeyData") $$<SMS_HIERARCHY_MANAGER><DateTime><ThreadID>
CPublicKeyLookup::UpdateCurrentKey() Checking C:\SMS\inboxes\hman.box\pubkey\ParentSiteCode.pkp for Key0 $$<SMS_HIERARCHY_MANAGER><DateTime><ThreadID>
CPublicKeyLookup::UpdateCurrentKey() Updating Key0 $$<SMS_HIERARCHY_MANAGER><DateTime><ThreadID>
Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
---|
Keywords: | kbSMSReporting kbtshoot kbSMSPackage kbprb KB889431 kbAudITPRO |
---|
|