Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Tell us your idea, suggestion, or issue with Update Management!

← Update Management

Upon scheduling an update deployment, message "....virtual machine being configured....", persists forever, no updates actually scheduled

Message "The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes." persists

47 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Ani shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

37 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Jose Angel Rivera commented  ·   ·  Flag as inappropriate

    I am also having the same behavior. At least please display a message like "This feature is not working at the moment", so that we don't waste our time waiting for the updates to appear.

  • Ryan Smith commented  ·   ·  Flag as inappropriate

    As of 12/20/2017 I too am still receiving this on machines I added this to more than 24 hours ago.

  • Mike Binnix commented  ·   ·  Flag as inappropriate

    MIcrosoft - any progress here. Your last update is two weeks old. Can we expect resolution soon or should we abandon our efforts to help you test this out. The error prevents us moving forward with using this feature.

  • Sam commented  ·   ·  Flag as inappropriate

    Any chance of an official message regarding this 'stuck message' on the portal, so that users know why that is there? Or perhaps a service health notification stating that it is a known issue...

  • Safeer Mohammed commented  ·   ·  Flag as inappropriate

    Thanks for feedback. We are looking into improve the experience.

    Meanwhile I am sending troubleshooting article for any registration errors that you see in "Operations Manager" event log of the machine

    https://docs.microsoft.com/en-us/azure/operations-management-suite/oms-solution-update-
    management#troubleshooting

    @Luuk the error message that you included is an indication that proxy/firewall is not configured in your environment to communicate with the service. The above doc will has requirements on the network settings.

  • chris commented  ·   ·  Flag as inappropriate

    same here, 2 vm's configured, 4 hours later -> The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes.

  • Luuk commented  ·   ·  Flag as inappropriate

    Same problem here.

    This is the error I get on the VM that is having the issue.

    The description for Event ID 4502 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    AOI-3db27714-8b73-43b6-abd5-61fc46c04ba7

    Microsoft.IntelligencePacks.AzureAutomation.HybridAgent.Init

    {B9370F8E-9340-9AF3-E1D8-B5CAA89EE205}

    Microsoft.EnterpriseManagement.HealthService.AzureAutomation.HybridAgent

    Microsoft.EnterpriseManagement.HealthService.ModuleException: Unable to Register Machine for Patch Management, Registration Failed with Exception System.InvalidOperationException: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

    at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)

    at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)

    --- End of inner exception stack trace ---

    at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)

    at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)

    --- End of inner exception stack trace ---

    at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)

    at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)

    --- End of inner exception stack trace ---

    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

    at AgentService.HybridRegistration.PowerShell.WebClient.AgentServiceClient.<Put>d__19`2.MoveNext()

    --- End of stack trace from previous location where exception was thrown ---

    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

    at AgentService.HybridRegistration.PowerShell.WebClient.AgentServiceClient.<RegisterV2>d__4.MoveNext()

    --- End of stack trace from previous location where exception was thrown ---

    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

    at AgentService.OmsHybridRegistration.PowerShell.Commandlets.OmsHybridRunbookWorker.<RegisterWithService>d__c.MoveNext()

    at AgentService.OmsHybridRegistration.PowerShell.Commandlets.OmsHybridRunbookWorker.ExtractErrorMessageAndThrow(AggregateException ae)

    at AgentService.OmsHybridRegistration.PowerShell.Commandlets.OmsHybridRunbookWorker.RegisterGroupInDatabase()

    at AgentService.OmsHybridRegistration.PowerShell.Commandlets.OmsHybridRunbookWorker.Register()

    the message resource is present but the message is not found in the string/message table

2 Next →

Update Management: Scheduling

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice