Troubleshooting Tips

If software inventory is not being reported to the site server:

• Verify that you have configured software inventory for this site. To do so, navigate to Client Agents in the SMS Administrator console.

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

  In the details pane, right-click Software Inventory Agent and click Properties. If, on the General tab, Enable software inventory on clients is selected, then software inventory is configured for this site.

• Make sure that at least 30 minutes have elapsed since the Software Inventory Agent was installed on the client. The initial software inventory takes place 20 minutes after the SMS client software is installed. If more than one hour has passed, examine the Sinv32.log file on the client to determine whether software inventory has begun.

  To force a Client Component Installation Manager (CCIM) cycle, which will install the Software Inventory Agent if it is enabled but not yet installed, double-click the Systems Management icon in Control Panel. Click the Sites tab and then click Update Configuration.

  To repair an installation, double-click the Systems Management icon in Control Panel. Click the Components tab, and then click Repair Installation.

• Verify that the client has been discovered and that its discovery data is in the SMS site database. If Software Inventory Processor receives inventory from a client that is not listed in the SMS site database, Software Inventory Processor:
  • Creates a *.ddr file for Discovery Data Manager to process (so that the client’s discovery data can be added to the SMS site database).
  • Moves the inventory file to the SMS\Inboxes\Sinv.box\Orphans directory on the site server.
  • Retries processing the inventory files in the \Orphans directory every ten minutes.

Until the client’s discovery data is in the SMS site database, the inventory information for that client cannot be processed.

• Verify that the client is within the site boundaries by comparing the client’s IP address or IPX network number to the site boundaries. To view the site boundaries in the SMS Administrator console, navigate to
  <site code - site name> in the console tree.

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

  Right-click <site code - site name> and click Properties. Click the Boundaries tab to view or modify the site boundaries.

• If the Software Inventory Agent is not installed on the client, check the Ccim32.log to determine if the agent is marked for de-install or if the initial install was launched.

If client software inventory has been completed on the client but is not being reported to the site server:

• Check the Cqmgr32.log file on the client to verify that the client has network connectivity to the CAP so that Copy Queue can transfer the software inventory files.
• Verify that the *.sic or *.sid file is moved to the CAP by checking the Cqmgr32.log on the client.
• On the CAP, verify that the *.sic or *.sid files were received and moved to the site server’s SMS\Inboxes\Inventry.Box directory by checking the Inboxast.log file.

If software inventory is not being reported from a child to a parent site:

• Verify that there is connectivity between the parent site and child site.
• Verify that Sender can communicate between the parent site and child site using the SMSservice account that you specified during installation (or the sender connection account specified in the Sender address properties dialog box in the Addresses node of Site properties in the SMS Administrator console). Sender will not attempt to make this connection unless Replication Manager has created a mini-job for Scheduler. Scheduler then creates a send request for Sender to connect to the destination site and transfer the inventory files.

Verify that the problems are not being caused by SQL Server connectivity errors:

• Review the immediately preceding status messages about SQL Server errors from the server components listed in Table 25.5.
• Verify that SQL 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 SQL Server error logs.