Article ID: 889431
Article Last Modified on 2/8/2007
APPLIES TO
- Microsoft Systems Management Server 2.0 Standard Edition
SYMPTOMS
In 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 siteSiteCode, retry it later $$<SMS_DESPOOLER><DateTime><ThreadID>
Will retry instruction D:\SMS\inboxes\despoolr.box\receive\FileName.IstRetryCountmore 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.
CAUSE
This 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.
RESOLUTION
To 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 thedriveletter:\Sms\Bin\I386 folder. If you have installed the SMS Recovery Tools, PreInst.exe is also located in thedriveletter:\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 theSiteCode.Ct7 file that you just created to the secondary site'sdriveletter:\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:
MORE INFORMATION
A primary site should contain a public key file for each of its children, and a secondary site should contain a public key file for each of its parent sites in the hierarchy. Without these key files, inter-site communication may not succeed. You can use the following syntax of the Preinst.Exe program to create the required public key files for your site hierarchy:
- PREINST.EXE /KEYFORPARENT
- PREINST.EXE /KEYFORCHILD
- PREINST.EXE /CHILDKEYS
- PREINST.EXE /PARENTKEYS
For additional information about the SMS 2.0 Hierarchy Maintenance Utility (Preinst.exe) program and other SMS 2.0 site recovery tools, visit the following Microsoft Web site:
For information about how to obtain the SMS Recovery Tools, visit the following Microsoft Web site:
For additional information about how to obtain the latest SMS 2.0 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
288239 How to obtain the latest Systems Management Server 2.0 service pack
For additional information about related issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:
245579 SMS: Secondary site does not decompress package
889436 Systems Management Server 2.0 secondary site cannot communicate with a parent site in a multi-tiered hierarchy
Keywords: kbsmsreporting kbtshoot kbsmspackage kbprb KB889431
