Following the install of SCCM 2012 SP1 in our environment we've noticed that every 2003 server has a wmiprvse crash weekly on Friday which corresponds to when Software/Hardware inventory is run.   This is only happening on 2003 servers and not 2008 or 2008 R2.  Is this a known issue?  Is there a fix?

My Org is having the same issue worldwide on all 2003 servers. I am not sure its Hardware or Software inventory though as when I run those each manually I do not seem to be able to get WMI to crash. However Microsoft please take notice this is happening. My Server Mgmt teams are not very happy about it.

I am experiencing this issue as well. I've narrowed the issue down to the hardware inventory cycle, at least in my case.

Checking the InventoryAgent.log log in CMTrace shows a single unknown error that appears for each crash:

Unknown error encountered processing an instance of class CCM_RecentlyUsedApps: 800706BE    InventoryAgent    2/18/2013 4:09:36 PM    5092 (0x13E4)

If I run a hardware inventory cycle while logged into the server, I don't get a notification that WMI has crashed until I log off and back on again. I can, however, see the crash in the Application event log.

Are either of you seeing this entry in your InventoryAgent.log files?

Given the lack of responses, your best bet is to contact CSS.

Mike,

We are seeing the exact same error about 2 seconds after the timing of the screenshot above, so yea, I think you are on to something.

Gotta ask the the question... Do you need ccm_recently used apps on those servers to be reported? My guess is no.  In default client agent settings, hardware inventory, uncheck the box for ccm_recentlyusedapps.  

Create a custom client agent setting, with the only enabled option is in hardware inventory, ccm_recentlyusedapps.

Create a collection of every other machine...except these failing ones.  Deploy the custom client agent setting to those machines that do not fail to report on ccm_recentlyusedapps.

Sit back and wait and see if that works around the issue.  If a workaround is not acceptable, then like Jason, I recommend you open a call to CSS.

Hi John,

We're experiencing the exact same problem. We can see the same problem with CCM_RecentlyUsedAPPS in the inventoryagent.log on any server 2003 server at preceisely the same time we get a WMIPRVSE.exe crash.

It only happens on our 2003 servers as well and appeared shortly after upgrading to SCCM 2012 SP1 from SCCM 2012.

I just came across this thread which states that a fix for this issue should be coming in CU1 for SP1:

http://social.technet.microsoft.com/Forums/en-US/configmanagerdeployment/thread/aeec488e-2030-4e6a-83da-5796174ebd

CU1 has been released:

http://support.microsoft.com/kb/2817245/en-us

I did what you suggested (so I thought) of unchecking "ccm_recentlyusedapps" from the default client settings.  I already had a general Server Hardware Inventory Client Settings deployed so I set that to inventory "ccm_recentlyusedapps".  I then created a Collection and deployed a unique Client Setting for all my Windows 2003 Servers and made sure that "ccm_recentlyusedapps" was not selected.  After I went back in though, it was selected again.  No matter what, if "ccm_recentlyusedapps" is enabled in any client setting, I cannot uncheck it from the client setting I specifically made for the 2003 Servers.  If I do, it is back when I go back into the Class setting.

Right now, I have removed "ccm_recentlyusedapps" from all client settings

I'm wondering if I'm not understanding something about how client settings work

Hi,

This issue was resolved in CU1. You may just want to apply CU2 instead of creating different client settings. Here's a link with information:

http://blogs.technet.com/b/configmgrteam/archive/2013/06/21/now-available-cumulative-update-2-for-system-center-2012-configuration-manager-service-pack-1.aspx

FYI:

http://blogs.technet.com/b/configmgrteam/archive/2013/07/02/known-issue-secondary-site-installation-failure-with-cumulative-update-2.aspx

Good installation walkthrough:

http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/

Hi,

This issue was resolved in CU1. You may just want to apply CU2 instead of creating different client settings. Here's a link with information:

http://blogs.technet.com/b/configmgrteam/archive/2013/06/21/now-available-cumulative-update-2-for-system-center-2012-configuration-manager-service-pack-1.aspx

FYI:

http://blogs.technet.com/b/configmgrteam/archive/2013/07/02/known-issue-secondary-site-installation-failure-with-cumulative-update-2.aspx

Good installation walkthrough:

http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/