Troubleshooting Tips

If client hardware inventory is not being reported to the site server, and you cannot tell whether it has been collected on the client:

Verify that the Hardware Inventory Agent is enabled at the site level, from the SMS Administrator console. If the agent has just been enabled, wait at least 30 minutes so that inventory can start.
Verify that the Hardware Inventory Agent was successfully installed, and check its state by checking the Hinv32.log in the %Windir%\MS\SMS\Logs directory on the client. Check the Clisvc.log to verify that the Hardware Inventory Agent is being launched at specified intervals.
To repair an installation, double-click the Systems Management icon in Control Panel. Click the Components tab, select Hardware Inventory Agent, and then click Repair Installation.
Make sure that at least 30 minutes have elapsed since the Hardware Inventory Agent was installed on the client. The initial hardware inventory takes place 15 minutes after the SMS client software is installed. If more than one hour has passed, examine the Hinv32.log file on the client to determine whether hardware inventory has begun.
To force a Client Component Installation Manager (CCIM) cycle, which will install the Hardware 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.
If the Hardware 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.
To repair an installation, double-click the Systems Management icon in Control Panel. Click the Components tab, select Hardware Inventory Agent, and then click Repair Installation.
Verify that the Windows Management Instrumentation (WMI) service is running.
To verify that the server component is operational, double-click the Systems Management icon in Control Panel. Click the Components tab, and then click Refresh Status. You can verify that WMI is installed correctly by selecting Windows Management, then clicking Repair Installation.
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.
Verify that the client has been discovered and that its discovery data is in the SMS site database. If Inventory Processor receives inventory from a client that is not listed in the SMS site database, 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.

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

Force an immediate hardware inventory by double-clicking the Systems Management icon in Control Panel. Click the Components tab, select Hardware Inventory Agent, and then click Start Component. Trace the process by checking logs and status messages.
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 hardware inventory files.
Verify that the *.inv file is moved to the CAP and renamed to *.nhm by checking the Cqmgr32.log on the client. Verify that the *.inv file is deleted.
Check the Inboxast.log on the CAP to verify that the CAP received the *nhm files and moved them to the site server’s SMS\Inboxes\Inventry.Box directory.

If hardware inventory is being collected at the client and you can verify that the files have been processed at the CAP, check the following at the site server:

Examine the Invproc.log to determine whether Inventory Processor successfully processed the *.nhm file, moved it to the Dataldr.box directory, and renamed it to a *.mif file.
Examine the Dataldr.log file to determine whether the MIF files are being processed and written to the SMS site database and whether there have been any SQL Server connectivity problems. Enable SQL Tracing to improve reporting of SQL Server connectivity issues in the Dataldr.log file.
Check the \Badmifs directory for invalid MIF files.

If hardware inventory is being reported, but MIF files are not being correctly processed, try the following:

Verify that the MIF file is not larger than the “Maximum MIF Size” which defaults to 5,000,000 bytes (4.7MB). If the MIF file is larger than the size indicated in the client’s or the site server’s registry key, it will be rejected and placed in the \Badmifs directory.
The “Maximum MIF Size” can be increased by editing the registry at the site server. The registry key is HKEY_LOCAL_MACHINE/SOFTWARE/
Microsoft/SMS/Components/SMS_Inventory_Dataloader/Max MIF Size.
Verify that the MIF file does not target the System Architecture using an ArchitectureName of “System” or “Personal Computer.”
Verify that the MIF file does not reference an Architecture MIF Group.

If hardware 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. Sender will not attempt to make this connection unless Replication Manager has sent a request to Scheduler. Scheduler then transfers the request to Sender to make the connection.

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

Review the immediately preceding status messages for Inventory Data Loader about SQL Server errors.
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.

Hardware inventory: 32-Bit client flowchart