BatchPatch Forums Home › Forums › BatchPatch Support Forum › Error:1073741819
- This topic has 4 replies, 2 voices, and was last updated 8 years, 11 months ago by doug.
-
AuthorPosts
-
October 3, 2013 at 9:37 am #8617marwinpParticipant
We have this error just on 2 windows 2012 server. Any ideas to resolve it?
this was in error log:
hr=0xC004F074
RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=f0f5ec41-0d55-4732-af02-440a44a3cf0f;NotificationInterval=1440;Trigger=UserLogon;SessionId=2
October 3, 2013 at 2:33 pm #9617dougModeratormarwinp –
First, it’s hard for me to understand this error without providing any context. It would be helpful to know what action you executed to produce this error, and which error log you are pulling this error text from. Also, what does the BatchPatchError.log show from the target server’s working directory (usually c:program filesbatchpatch) and what does the BatchPatch interface show/report? Lastly, when does the error occur? Before or after the BatchPatch action completes?
I just did some quick google searching on 0xC004F074, and all the results imply that the issue is with the KMS Windows Activation status of those 2012 servers, so that’s a good first place to start.
From just one of many pages found when searching google, implying an issue with License Activation:
“License Activation (slui.exe) failed with the following error code: hr=0xC004F074 Command-line arguments: RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=f0f5ec41-0d55-4732-af02-440a44a3cf0f;NotificationInterval=1440;Trigger=UserLogon;SessionId=2”
October 3, 2013 at 8:01 pm #9616marwinpParticipantHello Doug We have many 2012 server and it happens just on 2 of them.One of them was restored from backup.
Here is sequence from Batchpatch log:
Windows Update: Establishing connection…
Windows Update: Attempting to initiate Windows update…
Windows Update: Executing BatchPatchRemoteAgent.exe…
Windows Update: Error: -1073741819
In wsus log is this:
748 744 AU >>## RESUMED ## AU: Search for updates [CallId = {4876739C-15C5-4885-ADE4-E6A3CFFAB817} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
748 744 AU # 77 updates detected
748 744 AU #########
748 744 AU ## END ## AU: Search for updates [CallId = {4876739C-15C5-4885-ADE4-E6A3CFFAB817} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
748 744 AU #############
748 744 AU All AU searches complete.
748 b80 Report CWERReporter finishing event handling. (00000000)
748 b80 EP Got WSUS Client/Server URL: “http://wsus1.ice.corp/ClientWebService/client.asmx”
748 b80 PT WARNING: Cached cookie has expired or new PID is available
748 b80 EP Got WSUS SimpleTargeting URL: “http://wsus1.ice.corp”
748 b80 PT Server URL = http://wsus1.ice.corp/SimpleAuthWebService/SimpleAuth.asmx
748 b80 EP Got WSUS Reporting URL: “http://wsus1.ice.corp/ReportingWebService/ReportingWebService.asmx”
748 b80 Report Uploading 2 events using cached cookie, reporting URL = http://trbwsus1.ice.corp/ReportingWebService/ReportingWebService.asmx
748 b80 Report Reporter successfully uploaded 2 events.
748 ec0 AU ########### AU: Uninitializing Automatic Updates ###########
748 ec0 WuTask Uninit WU Task Manager
748 ec0 Service *********
748 ec0 Service ** END ** Service: Service exit [Exit code = 0x240001]
748 ec0 Service *************
October 4, 2013 at 12:25 am #9615dougModeratorWhat does the BatchPatchError.log show from the target server’s working directory (usually c:program filesbatchpatch) ? That might give us a bit more information to work with.
However, it really sounds like this issue has nothing to do with BatchPatch per se, but is rather something going on with Windows or possibly caused by third-party app like anti-virus or other software. Are you able to update these computers manually without using BatchPatch? I suspect that a manual update will fail too, which would confirm that BatchPatch is not related to the problem.
-Doug
December 14, 2015 at 5:54 pm #11032dougModeratorAnother user who was experiencing this error determined that the source of the problem was his WSUS server:
-
AuthorPosts
- You must be logged in to reply to this topic.