@RHC - Yes - last I heard, there is an update coming for Windows Server 2008 R2 to address the WMI issue. There should be a KB article released at some point in the future on this topic.
Oscar
26 Apr 2012 1:06 AM
Kevin, could you pls send me an email when the KB article comes out? oscar.forero@icbc.com
3 May 2012 9:35 PM
Update to original article:
Known issues in this MP:
1. If your ConfigMgr servers are running on the 64bit Server 2008 R2 platform, you might see alerts about failing to read %PROCESSOR_ARCHITECTURE:
ConfigMgr 2007 Software Update Point Health: Script error
[SERVERNAME]
- ConfigMgr 2007 Software Update Point Health: Script error.
The script 'ConfigMgr 2007 Monitor Server Health' running under processing rule '{D52DF5C6-0ECE-4E64-550A-608AD4E4FC02}' encountered a runtime error.
Failed to read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class.
This is an OS issue – with the WMI Win32_Environment class. The scripts will work most of the time but randomly you will see failures of the scripts due to the inability to read from Win32_Environment
There is a hotfix available – you will need to open a support case with Microsoft to request this until it is available externally or included in a service pack. The KB number to request is KB2692929
SCOM <3
27 Jun 2012 3:38 PM
On which systems do i have to install the hotfix?
Only on my SCCM-servers?
Thanks
27 Jun 2012 4:16 PM
Yep - only on SCCM server roles. I cover this on my hotfix page:
From: blogs.technet.com/.../which-hotfixes-should-i-apply.aspx
I recommend this hotfix for Server 2008 R2 machines that also host a ConfigMgr 2007 role, and you are using the ConfigMgr 2006 MP. This fixes an annoying issue
DDog1111
14 Aug 2012 3:27 PM
We have an SCCM 2007 R2 environment running on Windows 2003 Server. In our SCOM 2012 environment, I imported the SCCM MP and immediately got the %Processor_architecture alerts. That hotfix is for Server 2008 R2. Is there a fix for Windows 2003?
EricGS
24 Aug 2012 10:35 AM
I have the same issue as DDog1111, running on a Windows 2003 server. Do you know whether there is a fix for this?
Thanks for your excellent blog posts, they really help.
David Marshall
27 Aug 2012 2:08 AM
We are running Windows 2008 R2 SP1 x64 and receiving this error on all of our SCCM servers but the patch will not install with "This udpate is not applicable to your computer".
I have read through the website support.microsoft.com/.../2692929 and don't see how our OS is not applicable?
11 Sep 2012 11:47 AM
Since I have updated the ConfigMgr MP I got tons of 10706 and 10707 events ( 30 each seconds...)
10706: The following error occurred connecting to the script data source for management group '%5', target computer '%6',and data type '%7' (HRESULT 0x%8).Some data may be lost.Please verify the Data source is running.%n%nOne or more workflows were affected by this.%n%nWorkflow name: %2%nInstance name: %3%nInstance ID: %4%nManagement group: %1
10707 : The following error occurred submitting data to the script data source for management group '%5', target computer '%6',and data type '%7' (HRESULT 0x%8).Some data may be lost.Please verify the Data source is running.%n%nOne or more workflows were affected by this.%n%nWorkflow name: %2%nInstance name: %3%nInstance ID: %4%nManagement group: %1
(example of worklows: SMSv4_Perf_Threshold__MP_DDR_Backlog__10000_over_3_hours_17_Rule
example of instance name: Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Management_Point_Servers_Installation )
I have not found anything about thess events, do you know what is happening?
Regards
Hans
5 Nov 2012 7:02 AM
Great Kevin,
I have the same "%PROCESSOR_ARCHITECHTURE%" issue (on 2008R2 SCCM Server). I will download the hotfix from MS.
Thanks.
Stephen Owen
20 Aug 2013 11:05 PM
This same issue seems to crop up by causing "SMP Free Space < 100" alerts in SCOM as well.