I'm try to add local servers in my Azure Update Management from WAC. When I arrive to Automation Account, it stuck at loading. No error message, just looping. We already have 10 local (physical and VM) servers in my Azure Update Management. Anybody have this issue ?

RHarrisTSNo but I found that we have some UI error in the event log : msft.sme.windows-updatesource : appErrorHandlertimestamp : 1631024859385message : ajax error 400or msft.sme.packetmon!main: RemoteException: The term 'pktmon' is not recognized as the name of a cmdletand in the dev tool of the browser (Firefox or Edge) we have this : {"error":{"code":"AuthenticationFailed","message":"Authentication failed. The 'Authorization' header is missing."}}

Hi Guys, I just received this from Windows-Admin-Center-Ideas-and-Feedbackhttps://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/40"This has been fixed. We will push out an update to the extension soon."

Hello,i have wait long time for the update. Today i update Admin Center to:Version21101.3.2111.01001But same error with the Automation Account I have try to create new "Automation Account" but the button to create is only grey and cannot proceed.

I'm having this same exact issue. I was able to add the first server fine through the initial wizard. All additional server hang at loading on when selecting existing Azure automation account.Were you able to resolve this?

Ah so maybe have to use Powershell to register with Azure Update. Hopefully they fix that soon.

Automation account stuck at loading | Microsoft Community Hub

15 Replies

Alex Ignatenko
MCT
Apr 09, 2022
same issue when adding Update management from ARC.
cheapscotsman1320
Copper Contributor
Mar 15, 2022
Still happening
Marc Laflamme
Brass Contributor
Feb 21, 2022
Still experiencing this issue as well.
jmacb
Copper Contributor
Oct 04, 2021
I'm also having this issue, so assume it hasn't been fixed yet.
- RHarrisTS
  Copper Contributor
  Oct 04, 2021
  jmacb I have a ticket open with MS but they haven't given me an update in over a week. I just manually ran all the updates in the mean time.
  - Hans_S
    Copper Contributor
    Oct 15, 2021
    RHarrisTS same Error in my application. Have you found a workaround?
RHarrisTS
Copper Contributor
Sep 07, 2021
I'm having this same exact issue. I was able to add the first server fine through the initial wizard. All additional server hang at loading on when selecting existing Azure automation account.

Were you able to resolve this?
- Guillaume Bélanger
  Copper Contributor
  Sep 07, 2021
  RHarrisTSNo but I found that we have some UI error in the event log : msft.sme.windows-update
  source : appErrorHandler
  timestamp : 1631024859385
  message : ajax error 400
  or
  msft.sme.packetmon!main: RemoteException: The term 'pktmon' is not recognized as the name of a cmdlet
  and in the dev tool of the browser (Firefox or Edge) we have this :
  {"error":{"code":"AuthenticationFailed","message":"Authentication failed. The 'Authorization' header is missing."}}
  - RHarrisTS
    Copper Contributor
    Sep 07, 2021
    Ah so maybe have to use Powershell to register with Azure Update. Hopefully they fix that soon.

Forum Discussion

Automation account stuck at loading

15 Replies

Resources