none
Keep getting transient network errors (0X80072EE2) when an ADR runs RRS feed

  • Question

  • Every time I run one ADR I get the following 0X80072EE2 error: 

    Network connection: Windows Update Agent encountered transient network connection-related errors

    I have seen errors like this during deployment package distributions to remote DPs, but I have not seen this before when running an ADR. I have looked at both the ruleengine.log and the patchdownloader.log and I see absolutely nothing in them that identifies the issue. 

    Can someone please provide some help here?

    I don't mind opening up a PSS ticket with Microsoft, but just wanted to check here in the forums first before I escalate. 

    Thanks

    Thursday, August 15, 2019 5:33 PM

All replies

  • Where exactly are you getting that message at/in?

    Also, what do you mean "run one ADR"? Do  you mean evaluate the ADR in the ConfigMgr console?

    ADRs don't have any direct interaction with or make use of the Windows Update Agent so what you have above is a bit confusing.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, August 15, 2019 7:55 PM
  • When I go to \Software Library\Overview\Software Updates\Automatic Deployment Rules, under the "Last Error Description", is where I see the error. When I say, "run one ADR", I am just letting you know that other ADRs are not running so other ADRs are not conflicting or causing server resources to be used up which some may attribute to this error. 

    I know that ADRs don't have any direct interaction with the WUA, which is why I am a bit confused why this error is showing up. 

    Thursday, August 15, 2019 9:19 PM
  • GRRRR!

    I just now realized that the updated patchdownloader.log is not located in the common SCCM logs location, but rather in my local user profile AppData temp location. 

    I am looking it over now. 

    Thursday, August 15, 2019 9:45 PM
  • Okay, that new patchdownloader.log did not help at all either. 
    Thursday, August 15, 2019 10:32 PM
  • Have you manually initiated the the ADR evaluation and watched ruleengine.log?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, August 16, 2019 2:19 AM
  • Yes sir and didn't see anything. 

    The Site Server is pending a reboot though and not sure if that could help anything, but it would be great to restart it and then retry. 

    I am rerunning ADRs again and currently monitoring the ruleengine.log. 

    Friday, August 16, 2019 2:50 AM
  • Okay, I re-ran an ADR and the ruleengine.log showed absolutely NO errors, yet, here is what I am seeing after the rule runs on the ADR itself:

    Why would an error like this keep displaying, but not showing in the log?

    Is this a bug you think?

    Friday, August 16, 2019 2:55 AM
  • I spoke too soon, here is what I am seeing in the ruleengine.log now which does have some errors, but the ADR seemed to complete successfully and content downloaded to the package and the SUG and deployments were created:

    SQL written back is: update Rules set Data = N'<AutoDeploymentRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DeploymentId></DeploymentId> <DeploymentName>_RAR - 2019 - ADR - Semi-Annual - 2 - Workstations - Required - Third Party Updates</DeploymentName> <UpdateGroupId>ScopeId_EB2528A0-9517-4FC8-9546-5B943AB3BE03/AuthList_ebe31c6f-a91c-40d0-81c3-914cb6b90e4b</UpdateGroupId> <UpdateGroupName></UpdateGroupName> <LocaleId>1033</LocaleId> <UseSameDeployment>false</UseSameDeployment> <AlignWithSyncSchedule>false</AlignWithSyncSchedule> <NoEULAUpdates>false</NoEULAUpdates> <EnableAfterCreate>false</EnableAfterCreate> <ScopeIDs><ScopeID>SMS00UNA</ScopeID> <ScopeID>WOR00001</ScopeID> <ScopeID>WOR00005</ScopeID> <ScopeID>WOR00006</ScopeID> <ScopeID>WOR00007</ScopeID> </ScopeIDs> <EnableFailureAlert>true</EnableFailureAlert> <IsServicingPlan>false</IsServicingPlan> </AutoDeploymentRule>' where RuleID = 30	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    SQL written back is: update RuleActions set Data = N'<DeploymentCreationActionXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DeploymentId>{636ffb57-026c-4afc-90fb-6b4ff8765b29}</DeploymentId> <DeploymentNumber>7</DeploymentNumber> <CollectionId>WOR00CBE</CollectionId> <IncludeSub>true</IncludeSub> <Utc>false</Utc> <Duration>10</Duration> <DurationUnits>Days</DurationUnits> <AvailableDeltaDuration>9</AvailableDeltaDuration> <AvailableDeltaDurationUnits>Days</AvailableDeltaDurationUnits> <SoftDeadlineEnabled>false</SoftDeadlineEnabled> <SuppressServers>Checked</SuppressServers> <SuppressWorkstations>Unchecked</SuppressWorkstations> <PersistOnWriteFilterDevices>Unchecked</PersistOnWriteFilterDevices> <AllowRestart>false</AllowRestart> <DisableMomAlert>false</DisableMomAlert> <GenerateMomAlert>false</GenerateMomAlert> <UseRemoteDP>true</UseRemoteDP> <UseUnprotectedDP>true</UseUnprotectedDP> <UseBranchCache>true</UseBranchCache> <RequirePostRebootFullScan>Unchecked</RequirePostRebootFullScan> <EnableDeployment>false</EnableDeployment> <EnableWakeOnLan>false</EnableWakeOnLan> <AllowDownloadOutSW>false</AllowDownloadOutSW> <AllowInstallOutSW>false</AllowInstallOutSW> <EnableAlert>true</EnableAlert> <AlertThresholdPercentage>95</AlertThresholdPercentage> <AlertDuration>7</AlertDuration> <AlertDurationUnits>Days</AlertDurationUnits> <EnableNAPEnforcement>false</EnableNAPEnforcement> <UserNotificationOption>DisplaySoftwareCenterOnly</UserNotificationOption> <LimitStateMessageVerbosity>true</LimitStateMessageVerbosity> <StateMessageVerbosity>5</StateMessageVerbosity> <AllowWUMU>false</AllowWUMU> <AllowUseMeteredNetwork>false</AllowUseMeteredNetwork> </DeploymentCreationActionXML>' where RuleID = 30 and ActionID = 108	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    CRuleHandler: Enforcing Actions for Rule 30 failed!	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    CRuleHandler: ResetRulesAndCleanUp()	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    Rule result is: 0	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    CRuleHandler::CreateFailureAlert - Alert ID = 16777349	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    Updated Failure Information for Rule: 30	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    CRuleHandler: Deleting Rule 30	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    Found notification file D:\Program Files\Microsoft Configuration Manager\inboxes\RuleEngine.box\30.RUL	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    RuleSchedulerThread: Change in Rules Object Signalled.	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (4) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (7) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (11) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (12) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (13) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (14) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (17) from schedule string (8EEE9C0000331440) with next occurence (9/11/2019 11:35:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (18) from schedule string (B6FA9C0000331440) with next occurence (9/11/2019 11:45:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (19) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (20) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (21) from schedule string (955EAC00001000F0) with next occurence (8/26/2019 10:37:00 AM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (22) from schedule string (0DBFAC00001000F0) with next occurence (8/27/2019 1:03:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (24) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (28) from schedule string (02C98C4000331440) with next occurence (9/11/2019 10:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (29) from schedule string (02C98C4000331440) with next occurence (9/11/2019 10:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (30) from schedule string (02E98C4000331440) with next occurence (9/11/2019 11:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (31) from schedule string (004F8C4000331480) with next occurence (9/12/2019 2:00:00 AM)	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    FindNextEventTime found next event for RuleID 21 as :8/26/2019 10:37:00 AM	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    RuleEngine: Got next rule execution time successfully. Next event is in  15105 minutes	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    Sleeping for 15 minutes	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	35496 (0x8AA8)
    CRuleHandler: Need to Process 0 rules	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    CRuleHandler: ResetRulesAndCleanUp()	SMS_RULE_ENGINE	8/15/2019 10:51:29 PM	21608 (0x5468)
    Found notification file D:\Program Files\Microsoft Configuration Manager\inboxes\RuleEngine.box\30.RUL	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	21608 (0x5468)
    RuleSchedulerThread: Change in Rules Object Signalled.	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (4) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (7) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (11) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (12) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (13) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (14) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (17) from schedule string (8EEE9C0000331440) with next occurence (9/11/2019 11:35:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (18) from schedule string (B6FA9C0000331440) with next occurence (9/11/2019 11:45:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (19) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (20) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (21) from schedule string (955EAC00001000F0) with next occurence (8/26/2019 10:37:00 AM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (22) from schedule string (0DBFAC00001000F0) with next occurence (8/27/2019 1:03:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (24) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (28) from schedule string (02C98C4000331440) with next occurence (9/11/2019 10:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (29) from schedule string (02C98C4000331440) with next occurence (9/11/2019 10:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (30) from schedule string (02E98C4000331440) with next occurence (9/11/2019 11:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (31) from schedule string (004F8C4000331480) with next occurence (9/12/2019 2:00:00 AM)	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    FindNextEventTime found next event for RuleID 21 as :8/26/2019 10:37:00 AM	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    RuleEngine: Got next rule execution time successfully. Next event is in  15105 minutes	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    Sleeping for 15 minutes	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	35496 (0x8AA8)
    CRuleHandler: Need to Process 0 rules	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	21608 (0x5468)
    CRuleHandler: ResetRulesAndCleanUp()	SMS_RULE_ENGINE	8/15/2019 10:51:34 PM	21608 (0x5468)
    Found notification file D:\Program Files\Microsoft Configuration Manager\inboxes\RuleEngine.box\30.RUL	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	21608 (0x5468)
    RuleSchedulerThread: Change in Rules Object Signalled.	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (4) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (7) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (11) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (12) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (13) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (14) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (17) from schedule string (8EEE9C0000331440) with next occurence (9/11/2019 11:35:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (18) from schedule string (B6FA9C0000331440) with next occurence (9/11/2019 11:45:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (19) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (20) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (21) from schedule string (955EAC00001000F0) with next occurence (8/26/2019 10:37:00 AM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (22) from schedule string (0DBFAC00001000F0) with next occurence (8/27/2019 1:03:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (24) from schedule string () with next occurence (12/31/1969 7:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (28) from schedule string (02C98C4000331440) with next occurence (9/11/2019 10:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (29) from schedule string (02C98C4000331440) with next occurence (9/11/2019 10:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (30) from schedule string (02E98C4000331440) with next occurence (9/11/2019 11:00:00 PM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Refreshed ScheduleList instance for Rule (31) from schedule string (004F8C4000331480) with next occurence (9/12/2019 2:00:00 AM)	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    FindNextEventTime found next event for RuleID 21 as :8/26/2019 10:37:00 AM	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    RuleEngine: Got next rule execution time successfully. Next event is in  15105 minutes	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    Sleeping for 15 minutes	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	35496 (0x8AA8)
    CRuleHandler: Need to Process 0 rules	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	21608 (0x5468)
    CRuleHandler: ResetRulesAndCleanUp()	SMS_RULE_ENGINE	8/15/2019 10:51:40 PM	21608 (0x5468)


    Friday, August 16, 2019 3:02 AM
  • Not everything in red in CMTrace is actually an error; lines with the words fail or error in them are marked in red as well.

    As for the error itself, that's strange. What update criteria is configured on the ADR?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, August 16, 2019 4:01 AM
  • I know, anything that has a "false" in it is marked red, so I use it with a grain of salt in some instances. 

    Anyway, I submitted a PSS request with Microsoft to get this resolved. 

    Thanks

    Friday, August 16, 2019 5:18 PM