Cloud Management Gateway Stuck on Starting

Jorge Carranco 0 Reputation points
2025-11-07T16:16:30.81+00:00

My Cloud Management Gateway is stuck on starting on it's status. My cmg is still deployed as Cloud Service (Classic). At first I suspected the Secret had expired and it had, and that has been renewed, but it still on stuck with the following errors from the CloudMgr.log

This also prevents me from upgrading to a newer version of Configuration Manager and we are on 2303.

ERROR: Exception occured for service XXXcmg1 : Microsoft.WindowsAzure.Storage.StorageException: The underlying connection was closed: An unexpected error occurred on a send. ---> 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.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~ --- End of inner exception stack trace ---~~ at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~ at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)~~ at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)~~ at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)~~ at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)~~ at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)~~ at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)~~ at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)~~ at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)~~ at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)~~ at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~ at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~ at System.Net.ConnectStream.WriteHeaders(Boolean async)~~ --- End of inner exception stack trace ---~~ at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)~~ at System.Net.HttpWebRequest.GetRequestStream()~~ at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSyncT~~ --- End of inner exception stack trace ---~~ at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSyncT~~ at Microsoft.ConfigurationManager.AzureManagement.AzureStorageOperation.GetTableOperationClient(StorageRetryPolicy storageRetryPolicy, StorageSettings storageSettings)~~ at Microsoft.ConfigurationManager.CloudServicesManager.AnalyticsCollectionTask.GetMetricsTransactionsEntities(AzureStorageOperation azureStorageOperation, String metricsTableName, DateTime startDate, DateTime endDate)~~ at Microsoft.ConfigurationManager.CloudServicesManager.AnalyticsCollecti

Microsoft Security | Intune | Configuration Manager | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2025-11-07T16:16:44.5433333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems that your Cloud Management Gateway (CMG) is experiencing issues due to a connection problem, as indicated by the errors in the CloudMgr.log. Here are a few steps you can take to troubleshoot the issue:

    1. Check Azure Service Health: Ensure that there are no ongoing issues with Azure services that could affect connectivity.
    2. Verify Network Configuration: Check the network settings and ensure that there are no firewall rules or network security groups blocking the necessary ports for the CMG.
    3. Review the Secret Key: Since you mentioned that the secret has been renewed, ensure that the new secret is correctly configured in the Azure portal and that it matches what is set in your Configuration Manager.
    4. TLS Configuration: Make sure that TLS 1.2 is enforced, as required by the CMG. This can be configured in the CMG setup wizard and may need to be verified in your Azure settings.
    5. Logs for Further Insights: Besides the CloudMgr.log, you may want to check the CMGSetup.log and CMGService.log for additional details on the deployment and service health.
    6. Redeploy CMG: If the issue persists, consider redeploying the CMG using the Azure Resource Manager deployment method, as the Cloud Service (Classic) is deprecated and may lead to issues in the future.
    7. Contact Support: If none of the above steps resolve the issue, it may be necessary to contact Microsoft Product Support Services for further assistance.

    Following these steps should help you identify and resolve the issue with your CMG being stuck on starting.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.