SMS_SOFTWARE_INVENTORY_PROCESSOR 3701

Thursday, November 06, 2008 6:19 PMbrotha

0
Sign In to Vote
experts, I need you to help me, I get the following error ....

SMS Software Inventory Processor failed to process software inventory file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\ZTBT7G0B.SID," and has moved it to "C:\Program Files\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\pf10s1qd.SID."

Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax.
Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the subsequent message 3703, which indicates the resynchronization has begun.

my English is not very good, hopefully I understand and can help me.

thanks.
- Reply
- Quote

Answers

Thursday, November 06, 2008 6:59 PMSherry KissingerMVP, Moderator

0
Sign In to Vote
Find this file on your server:

C:\Program Files\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\pf10s1qd.SID

Using Notepad, open the file, and look for the computer name that sent the file.

Then, determine if one of the two possible causes are the reason:

Cause #1: [Computer] that does not already exist [in the database]

How to tell; look for the computer in Collections, All Systems, and check to see if it has Software Inventory information. If so, then this is not the cause.

Cause #2: the file contains invalid syntax

--------------------

In general, unless you are getting these messages for a high number of your clients, the automatic resynchronization is all you need to do (basically, the "Please wait" answer!)
- Marked As Answer bySherry KissingerMVP, ModeratorSaturday, December 20, 2008 1:34 PM
- Reply
- Quote

All Replies

Thursday, November 06, 2008 6:59 PMSherry KissingerMVP, Moderator

0
Sign In to Vote
Find this file on your server:

C:\Program Files\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\pf10s1qd.SID

Using Notepad, open the file, and look for the computer name that sent the file.

Then, determine if one of the two possible causes are the reason:

Cause #1: [Computer] that does not already exist [in the database]

How to tell; look for the computer in Collections, All Systems, and check to see if it has Software Inventory information. If so, then this is not the cause.

Cause #2: the file contains invalid syntax

--------------------

In general, unless you are getting these messages for a high number of your clients, the automatic resynchronization is all you need to do (basically, the "Please wait" answer!)
- Marked As Answer bySherry KissingerMVP, ModeratorSaturday, December 20, 2008 1:34 PM
- Reply
- Quote
Friday, December 12, 2008 7:07 AMveday001

0
Sign In to Vote
One of the SCCM expert advice me to create filter rules for following process. He advice that it will keep triggering and not of much importance. remember to priorotize this rules over default ones.
Do not replicate Inventory Data Loader Status message 2702
Source: ConfigMgr Server

Component: SMS_INVENTORY_DATA_LOADER

Message type: Milestone

Severity: Informational

Message ID: 2702

Next
Tick do not forward to status summarizers
Tick Do not process lower-priority status filter rules

Do not replicate Inventory Data Loader Status message 2703

Source: ConfigMgr Server

Component: SMS_INVENTORY_DATA_LOADER

Message type: Milestone

Severity: Informational

Message ID: 2702

Next
Tick do not forward to status summarizers
Tick Do not process lower-priority status filter rules

Do not replicate Software Inventory Processor Status Message 3707
Source: ConfigMgr Server
Component: SMS_INVENTORY_PROCESSOR
Message type: Milestone
Severity: Informational
Message ID: 3707

Next
Tick Do not forward to status summarizers
Tick Do not process lower-priority status filter rules
Do not replicate Software Inventory Processor Status Message 3701
Source: ConfigMgr Server
Component: SMS_SOFTWARE_INVENTORY_PROCESSOR
Message type: Milestone
Severity: Informational
Message ID: 3701
Next

Tick DDo not forward to status summarizers
Tick Do not process lower-priority status filter rules
Server Engineer
- Reply
- Quote
Friday, December 12, 2008 8:08 AMTorsten [MVP]MVP

0
Sign In to Vote
veday001 said:
One of the SCCM expert advice me to create filter rules for following process. He advice that it will keep triggering and not of much importance. remember to priorotize this rules over default ones [...]

This makes no sense, because that filter rule just filters out the resulting status messages, but does not solve the underlying problem at all. I highly recommend Sherry's way of troubleshooting!
- Reply
- Quote
Friday, March 20, 2009 11:20 AMLMichel

0
Sign In to Vote
I've got this error message for a lot of computers (10% of the total)

Where can I find a sample of valid syntax for .SID file ?

Is the problem at client side or at server side ?
- Reply
- Quote
Friday, March 20, 2009 11:45 AMLMichel

0
Sign In to Vote
Additional information !

I've found these error a lot of time in sinvproc.log :

Processing file: E:\Apps\Microsoft Configuration Manager\inboxes\auth\sinv.box\EXVKIO8N.SIC SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:09 89736 (0x15E88)
Processing Inventory for Machine: PC060029797 ResId: 45230 [OpCode=17 Sinv=1 FC=0 Resync=1] Generated: 03/20/2009 12:40:07 SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
WARNING: Exception Detected: The parameter is incorrect.~~ !! SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
Moved file E:\Apps\Microsoft Configuration Manager\inboxes\auth\sinv.box\EXVKIO8N.SIC to E:\Apps\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\sgx65l4q.SIC in BADSINV Directory !!! SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
STATMSG: ID=3701 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_SOFTWARE_INVENTORY_PROCESSOR" SYS=HICTATRIUSM003 SITE=CS1 PID=91668 TID=89736 GMTDATE=Fri Mar 20 11:42:16.578 2009 ISTR0="E:\Apps\Microsoft Configuration Manager\inboxes\auth\sinv.box\EXVKIO8N.SIC" ISTR1="E:\Apps\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\sgx65l4q.SIC" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
Send resync request to local site for client GUID:101EBEF9-A887-49C1-AF28-747020A18B00 (45230). SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
Remote client software inventory resync generated for client GUID:101EBEF9-A887-49C1-AF28-747020A18B00; update/insert result = 1 SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
Remote client software inventory dependent resync for file collection generated for client GUID:101EBEF9-A887-49C1-AF28-747020A18B00; update/insert result = 1 SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
Resync generated successfully for client. SMS_SOFTWARE_INVENTORY_PROCESSOR 20/03/2009 12:42:16 89736 (0x15E88)
- Reply
- Quote
Friday, March 20, 2009 1:41 PMLMichel

0
Sign In to Vote
Ok, found an explanation !

This error was due to files that have illegal attributes

msrepl35.dll Microsoft Replication Library 3.51.2404.0 01/02/2099 18:12:36
msjet35.dll Microsoft Jet Engine Library 3.51.2723.0 01/02/2099 18:12:36

I've also found a hotfix but it's not metioned if it is compatible with SCCM 2007 SP1

http://support.microsoft.com/kb/950653/en-us
- Reply
- Quote
Monday, March 23, 2009 9:33 PMWallyMSFT, Owner

0
Sign In to Vote
No, that hotfix is only for RTM, not SP1. According to what I can see, that fix is included in SP1 (see http://support.microsoft.com/default.aspx/kb/953649/en-us). If it is not working, contact customer support.
Wally Mead
- Reply
- Quote
Tuesday, March 24, 2009 8:14 AMLMichel

0
Sign In to Vote
It seems that this hotfix has not been included in SCCM 2007 SP1. Please, have a look at this post:

http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/690e2cd3-0276-49a2-a642-e0c4ba9bc945/
- Reply
- Quote
Tuesday, March 24, 2009 9:09 AMTorsten [MVP]MVP

0
Sign In to Vote
That hotfix IS included in SP1 (as Wally already said). In http://support.microsoft.com/default.aspx/kb/953649/en-us ("List of fixes that are included in System Center Configuration Manager Service Pack 1") it says:

http://support.microsoft.com/kb/950653/: "A software inventory operation does not work correctly in System Center Configuration Manager 2007 if the inventoried file has invalid time attributes"
- Proposed As Answer byLMichel Tuesday, March 24, 2009 9:14 AM
- Reply
- Quote
Tuesday, March 24, 2009 9:15 AMLMichel

0
Sign In to Vote
If the hotfix is included, it's not working !

Sinvproc.dll is at version 4.0.6221.1000. Is that the right version ?
- Reply
- Quote
Tuesday, March 24, 2009 3:51 PMWallyMSFT, Owner

0
Sign In to Vote
Yes, 4.00.6221.1000 is SP1. As I already stated, if it is not working, you need to contact CSS regarding it and request a new fix.

But it is included in SP1, check the KB I posted. It may be some other issue you are experiencing that was not fixed in SP1. However CSS is the way to go for this.
Wally Mead
- Reply
- Quote
Monday, March 30, 2009 2:23 PMLMichel

0
Sign In to Vote
Got an answer from Microsoft support. A hotfix exists that address this issue. So contact Microsoft support to get the hotfix if you are experiencing this issue.
- Proposed As Answer byLMichel Monday, March 30, 2009 2:23 PM
- Reply
- Quote
Tuesday, October 27, 2009 3:13 PMPeteris

0
Sign In to Vote
Can You please give the hotfix number? Is it available pulbically? I have a similar issue with ConfigMgr 2007 SP1.

Regards,
Peteris
- Reply
- Quote
Tuesday, October 27, 2009 3:46 PMSherry KissingerMVP, Moderator

1
Sign In to Vote
The hotfix is included in SP2; so either upgrade to SP2, or contact CSS to get this hotfix separately: http://support.microsoft.com/default.aspx/kb/968594

(Personally, I'd just upgrade to SP2, you know you want to anyway) :-)
Standardize. Simplify. Automate.
- Reply
- Quote