Answered by:
Client Install - Windows Error Reporting

Question
-
We're migrating from SCCM 2007 to SCCM 2012 R2. I'm manually pushing the client install from the console (i.e. right-click, Install Client, specify site code, always install) and I've noticed the errors below. It doesn't seem to impact the functionality of the client, and it only seems to occur once during the initial install. I'm assuming it's nothing to worry about but figured I would ask.
Error 1
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80244015
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Managed
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_74488eaa405d441aa5faf2ea29e0af3b3cf844_cab_d44cb397
Analysis symbol:
Rechecking for solution: 0
Report Id: 74c27bd3-1826-11e4-922e-005056bf27de
Report Status: 4Error 2
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80244015
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Managed
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: 74c27bd3-1826-11e4-922e-005056bf27de
Report Status: 0
Content of Report.wer
Version=1
EventType=WindowsUpdateFailure
EventTime=130512193686220617
Consent=1
ReportIdentifier=4d2df767-1819-11e4-bce9-d8d385e2b360
Response.type=4
Sig[0].Name=ClientVersion
Sig[0].Value=7.6.7600.256
Sig[1].Name=Win32HResult
Sig[1].Value=80244015
Sig[2].Name=UpdateId
Sig[2].Value=00000000-0000-0000-0000-000000000000
Sig[3].Name=Scenario
Sig[3].Value=Scan
Sig[4].Name=SourceId
Sig[4].Value=101
Sig[5].Name=Environment
Sig[5].Value=Managed
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
FriendlyEventName=Windows Update installation problem
ConsentKey=WindowsUpdateFailure
AppName=Host Process for Windows Services
AppPath=C:\Windows\System32\svchost.exe
ReportDescription=A Windows update did not install properly. Sending the following information to Microsoft can help improve the software.
- Edited by Frentic Wednesday, July 30, 2014 9:15 PM
Wednesday, July 30, 2014 9:11 PM
Answers
-
Generally if people do have ideas, they'll respond :-) Forums are free 'support' so there is never a guarantee of an answer. To get guaranteed answers, you would need to engage CSS. We all do our best here to help out, when our time is available to help, but all have jobs that also take our time, so can't be here 100% of our time looking to help (even though it might seem that some of the people do live here 100% of their time :-)
If the errors are around the install/upgrade time (as you indicated) then that is not uncommon to see errors, as services are shutdown, removed, installed, started up, etc. If they repeat on a consistent basis, and you can't track it down to a specific configuration, then CSS would be the route to go.
Wally Mead
- Marked as answer by Joyce L Friday, August 8, 2014 10:19 AM
Thursday, July 31, 2014 6:57 PM
All replies
-
Also, this seems to happen a couple of times actually. It generates those errors after the initial SCCM install from 2007 to 2012, and then again when SCEP is installed. I know Windows Updates are working because SCEP updates with the latest definitions via the ADR I have configured in 2012 R2.Wednesday, July 30, 2014 9:31 PM
-
Where are you pulling those from? The client?
Assuming you ave software updates properly setup and configured, wave you reviewed wuahandler.log on the client?
Jason | http://blog.configmgrftw.com
Wednesday, July 30, 2014 9:36 PM -
Where are you pulling those from? The client?
Assuming you ave software updates properly setup and configured, wave you reviewed wuahandler.log on the client?
Jason | http://blog.configmgrftw.com
Application Event Log on the client
And Windows Updates seem to be configured properly. WSUS is running on a separate 2012 R2 box. I'm able to deploy updates to systems, and like I said, SCEP definitions seem to be working fine as well.
I'll check the wuauhandler.log tomorrow on the client, however I don't recall seeing anything when I looked.
- Edited by Frentic Wednesday, July 30, 2014 11:31 PM
Wednesday, July 30, 2014 11:06 PM -
Hi,
Are there any helpful information in WUAHandler.log or WindowsUpdate.log?
Best Regards,
Joyce
Thursday, July 31, 2014 9:39 AM -
Hi,
Are there any helpful information in WUAHandler.log or WindowsUpdate.log?
Best Regards,
Joyce
Here are some errors from around the time of the initial SCCM upgrade from 2007 -> 2012. They re-occur when SCEP is installed, and again when the Client Upgrade is installed. Other than these errors which line up with the application event log errors, the logs seem fairly clean. Clients are installing Endpoint definitions successfully.
WuAuHandler.log
1)
Unable to read existing resultant WUA policy. Error = 0x80070002. WUAHandler 7/30/2014 4:20:34 PM 2732 (0x0AAC)
2)
OnSearchComplete - Failed to end search job. Error = 0x80244015. WUAHandler 7/30/2014 4:21:17 PM 2732 (0x0AAC)
Scan failed with error = 0x80244015. WUAHandler 7/30/2014 4:21:17 PM 2732 (0x0AAC)
WindowsUpdate.log (around the time of the error in the event log)
2014-07-30 16:21:14:123 948 17d0 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2014-07-30 16:21:14:123 948 17d0 PT WARNING: SOAP Fault: 0x00012c
2014-07-30 16:21:14:123 948 17d0 PT WARNING: faultstring:Fault occurred
2014-07-30 16:21:14:123 948 17d0 PT WARNING: ErrorCode:InvalidCookie(1)
2014-07-30 16:21:14:123 948 17d0 PT WARNING: Message:(null)
2014-07-30 16:21:14:123 948 17d0 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2014-07-30 16:21:14:123 948 17d0 PT WARNING: ID:97262048-3732-4131-8691-5a2feb76a13e
2014-07-30 16:21:14:123 948 17d0 PT WARNING: PTError: 0x80244015
2014-07-30 16:21:14:123 948 17d0 PT WARNING: GetCookie_WithRecovery failed : 0x80244015
2014-07-30 16:21:14:123 948 17d0 PT WARNING: RefreshCookie failed: 0x80244015
2014-07-30 16:21:14:123 948 17d0 PT WARNING: RefreshPTState failed: 0x80244015
2014-07-30 16:21:14:154 948 17d0 PT WARNING: Cached cookie has expired or new PID is available
2014-07-30 16:21:16:806 948 17d0 PT WARNING: StartCategoryScan failed : 0x80244015
2014-07-30 16:21:17:071 948 17d0 Agent * WARNING: Exit code = 0x80244015
- Edited by Frentic Thursday, July 31, 2014 2:10 PM
Thursday, July 31, 2014 2:06 PM -
Anyone have any ideas?Thursday, July 31, 2014 6:29 PM
-
Generally if people do have ideas, they'll respond :-) Forums are free 'support' so there is never a guarantee of an answer. To get guaranteed answers, you would need to engage CSS. We all do our best here to help out, when our time is available to help, but all have jobs that also take our time, so can't be here 100% of our time looking to help (even though it might seem that some of the people do live here 100% of their time :-)
If the errors are around the install/upgrade time (as you indicated) then that is not uncommon to see errors, as services are shutdown, removed, installed, started up, etc. If they repeat on a consistent basis, and you can't track it down to a specific configuration, then CSS would be the route to go.
Wally Mead
- Marked as answer by Joyce L Friday, August 8, 2014 10:19 AM
Thursday, July 31, 2014 6:57 PM