KB4033015 Provisioning not completed when creating a Cloud Management Gateway in SCCM 1702.
Consider that you have the Update rollup for Configuration Manager current branch version 1702 installed. When you try to create a new Cloud Management Gateway (CMG) in the Configuration Manager console, the provisioning cannot be completed. The status in the console remains displayed as “Provisioning.”
If you check the cloud service status from the Azure Portal, you find that the service keeps being provisioned. You will also see an error message for the cloud service assembly that resembles the following:
Waiting for role to start... Unhandled Exception: Could not load file or assembly
'interop.COMAdmin, Version=5.0.8498.1711, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
or one of its dependencies. The located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040) at Microsoft.ConfigurationManager.
AzureRoles.ProxyService.WebRole.ConfigureBGBServer() at Microsoft.ConfigurationManager.
AzureRoles.ProxyService.WebRole.OnStart() at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.
InitializeRoleInternal(RoleType roleTypeEnum) at Microsoft.WindowsAzure.ServiceRuntime.Implementation.
Loader.RoleRuntimeBridge.b__0() 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.Threading.
ThreadHelper.ThreadStart() [<em>date time</em>] Last exit time: <em>date time</em>]. Last exit code: 0.
This hotfix is available for download from the Microsoft Download Center:
For installation instructions, see the following article:
Then, follow these steps:
- For the remote SCP (Service Connection Point) role, make sure that the new Cloudproxyservice.cab file was copied over by the post-update actions performed by the site component manager.
- Delete the failed Cloud Management Gateway that was created after the rollup in the Configuration Manager console.
- For the old CMG, run the following SQL script on the top-most site database to update all of the CMGs:
1EXEC dbo.spInsertAzureCloudServiceUpgradeTask N'CloudProxyService'
- Now create the new Cloud Management Gateway.