Troubleshooting Tips

If client status messages are not being written to the SMS site database:

• Verify that the Status Reporting settings are configured in the SMS Administrator console at the site server to report status messages to Status Manager.
• Refer to Figure 23.4, “Status Manager,” to verify that Status Manager at the site server is processing status messages from clients.

If the status message that is not being written is a package status message for software distribution:

• Verify that the package settings include compression, because status is only returned for compressed packages.

  Advertisement status is returned from the client only when a package is successfully run. Status MIF files cannot be used in SMS 2.0.

If client status messages are not being written to the SMS site database:

• If a particular SMS client component’s messages are not being written to the SMS site database, examine the client component’s log file to verify that the SMS client component:
  • Generates a status message that is written to the *.svf file in a temporary directory on the client.
  • Notifies Copy Queue to transfer the message to the CAP. Copy Queue writes error messages to Cqmgr32.log (32-bit clients) or Clearque.log (16-bit clients) if it encounters a problem at the CAP (for example, if the share is not present, the CAP is offline, or the disk that the *.svf file should be written to is full).

If status messages are not appearing in the Application Log of the NT Event Viewer:

• Check filter rule configuration in the SMS Administrator console. Navigate to Status Filter Rules to make sure that they have been configured correctly.

  Systems Management Server   Site Database (site code - site name)      Site Hierarchy         site code - site name            Site Settings               Status Filter Rules

Right-click Status Filter Rules, select the Actions tab, and then verify that Report to the Windows NT Event Log is selected.

---

Note   SMS writes status messages to the Application Event Log, so messages relating to security problems do not appear in the Windows NT Event Viewer Security Log.

---

If no client in the site is generating Status Messages:

• Check Status Reporting in the SMS Administrator console. Navigate to Status Reporting.

  Systems Management Server   Site Database (site code - site name)      Site Hierarchy         site code - site name            Site Settings               Component Configuration                  Status Reporting 

  Make sure the Report check boxes have been checked. If not, Copy Queue will delete the client’s status messages instead of moving them to the CAP.

If some clients are not generating status messages on the site, or if there are *.svf files backing up on the client:

• Check Copy Queue to see if it is moving status messages from the client to the CAP. Check Cqmgr32.log (32-bit clients) or Clearque.log (16-bit clients) on the client for any errors. Also make sure the specific SMS client agent is running and that there are no errors in its log file.