Configuration Changes Initiated at the Current Primary Site

This flowchart describes how changes to site configuration are managed, whether the change is initiated by an administrator using the SMS Administrator console or by an SMS component.

The activity described in this flowchart takes place at primary site servers.

Tracing Information

You can trace the activity described in this flowchart by studying the status messages for the server components listed in the table below. Or, you can enable the log files for these components. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about viewing status messages and enabling logging, see “Status Messages Versus Logging” in Chapter 16, “Introducing the SMS 2.0 Flowcharts.”

Table 18.3 Status Message Components and Log Files for Site Control Manager:Configuration Changes Initiated at the Current Primary Site

Troubleshooting Tips

If site configuration changes are not being written to the site control file:

• Examine the Hman.log file to determine whether Hierarchy Manager can connect to the SMS site database and whether it can read the delta site control files.
  • Verify that this computer can reach the SMS site database server (SQL Server computer).
  • Verify that the SMS site database server services are running.
  • Verify that SMS can access the SMS site database.
  • Verify that the SMS site database, transaction log, and tempdb are not full.
  • Verify that there are at least 50 SQL Server user connections, plus five for each SMS Administrator console.
  • If the problem persists, check the SMS site database server error logs.
• If you are using standard SQL Server security, determine (from the Hman.log file or by contacting your SQL Server administrator) whether the SQL Server sa password has been changed recently.

  If the password has changed, ensure that the change is propagated to SMS. You can explicitly inform SMS of a change in the sa password on the Accounts tab of the Properties dialog box for the site. To open the site Properties dialog box, navigate to <site code - site name> in the SMS Administrator console:

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

  Right click <site code - site name> in the console tree and click Properties.

• If a component initiated the configuration change, determine, from the appropriate component log file whether the *.ct1 file was created and placed in the SMS\Inboxes\SiteCtrl.box\Incoming directory.
• Examine the Sitectrl.log file to determine whether Site Control Manager can do all of the following:
  • Read the *.ct1 file.
  • Copy the *.ct0 file to the SMS\Inboxes\SiteCtrl.box\History directory as a *.ct0 site control file.
  • Create a new Sitectrl.ct0 file by merging the current version with the incoming *.ct1 file.
  • Create a *.ct2 file for Hierarchy Manager to update the SMS site database.
• Hierarchy Manager reads SMS site database information from the site control table and uses it to create a *.ct1 file in the SMS\Inboxes\Sitectrl.box\Incoming directory. Using the Hierarchy Manager status messages or Hman.log, verify that Hierarchy Manager is able to read the SMS site database and create a *.ct1 file. Enable SQL tracing and then examine SMSprov.log and Hman.log to see a report of the SQL commands and responses from SQL Server.
• Hierarchy Manager takes a *.ct2 file from SMS\Inboxes\Hman.box and writes it to the SMS site database. Verify this last step in the update process by examining the Hman.log file.
• Use Windiff to compare site control files in the SMS\Inboxes\Sitectrl.box\History directory to see which configuration changes were made during each cycle.
• When the site control file process spans more than one SMS site, such as a child site reporting to a parent, verify that you have created addresses between the two sites.