Troubleshooting Tips

If the hourglass icon on the secondary site icon persists and the site does not become active:

• Verify that the secondary site server has never been an SMS client. If it was once an SMS client, remove the SMS client software and restart the secondary site installation.

---

Tip   You can use the Systems Management Installation Wizard to remove the SMS 2.0 client software. For wizard usage instructions and command-line parameters, see Chapter 12, “Upgrading Clients from SMS 1.2 to SMS 2.0.”

---

• Ensure that the primary site contains an address for the proposed secondary site. Check under:

  Systems Management Server   Site Database (site code - site name)      Site Hierarchy         site code - site name            Site Settings               Addresses

• Ensure that the appropriate trust relationships are in place if the site is in a different domain. If the site is in a different domain, ensure that the SMS Service account is specified in the other domain. Ensure that the SMS service account has the Log On as a Service right.
• Verify that the installation drive on the secondary site server has sufficient free disk space and that it is an NTFS partition.
• Verify that a Sitepkg.p* file was created in the primary site server’s SMS\Inboxes\Hman.box directory. If not, check SMS\Logs\Hman.log to see what error messages were generated.
• Check the \\<SecondarySiteName>\SMS\Logs\SMS_bootstrap.log file for error messages.
• Check the \\<SecondarySiteName>\SMS\Logs\Replmgr.log file for error messages.
• Check the SMS\Logs\Sender.log on the primary site server to determine whether the connection account that is specified in the Create Secondary Site Wizard:
  • Was unable to connect to the destination server.
  • Has full administrative rights to the destination server.
• Check the status messages generated by SMS Provider, Hierarchy Manager, Scheduler, Sender, Despooler, and Replication Manager for possible causes of failure to install the secondary site.

If the secondary site is installed, but the status is not updated at the primary site:

• Verify that the SMS Bootstrap service at the secondary site server has been removed.
• Verify that Site Component Manager is installed and running at the secondary site.
• Verify that SMS Executive is installed and running at the secondary site.