Unable to deploy SQL Always on to existing vnet

[IanMoroney]

sql-server-2014-alwayson-existing-vnet-and-ad

Issue Details

The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041033

https://gist.github.com/IanMoroney/5675fabe8f9bdcad8af24b17c608b077

Repro steps (if necessary, delete otherwise)

1. deploy template
2. wait for error 3. 4. 5.

[Jungle1990]

I met the same issue when run the "sqlvm-alwayson-cluster" and "sql-server-2014-alwayson-dsc", hopefully there are someone can quickly fix this problem

[singhkays]

@robotechredmond Can you take a look at this?

[robotechredmond]

Yes - reviewing it now ...

[robotechredmond]

Looks like it's an issue occurring with the DSC configuration for CreateFailoverCluster and WMF 5.0 (which is now preinstalled on the latest SQL Server VM images). I've tested a fix and will be submitting a pull request later today.

[robotechredmond]

Submitted Pull Request #2185 to correct issues with DSC Extension v2.17 and WMF 5.0 when processing DSC configuration.

[IanMoroney]

Did this PR get approved?

[dewolfs]

Tried this template with DSC extension v2.17 but it's still failing

Resource Microsoft.Resources/deployments 'deploySqlCluster' failed with message "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "DeploymentFailed", "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.", "details": [ { "code": "Conflict", "message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\ n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.\",\r\n \"details\": [\r\n
{\r\n \"code\": \"Conflict\",\r\n \"message\": \"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation compl eted with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'sqlAOPrepar e'. Error message: \\"DSC Configuration 'PrepareAlwaysOnSqlServer' completed with error(s). Following are the first few: The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x8004 1033 \

[robotechredmond]

I'm not able to repro this issue. Two questions:

• Which Azure region are you attempting to deploy to?
• Can you include a link to a full copy of the DSC extension log in the Logs folder on the VM?

[GArionMSFT]

Hello,

I can repro this very consistently. I'm currently trying to deploy to WestUS2.

The SQL Witness machine seems to deploy fine and gets domain-joined as expected, however, when it gets to the other SQL machines it fails (and they do not get domain-joined).

Portal Error message:

deploySqlAlwaysOn | Failed | (Error details) | 06/05/2017, 18:36:21 | 2 minutes 18 seconds

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'sqlAOPrepare'. Error message: \\"DSC Configuration 'PrepareAlwaysOnSqlServer' completed with error(s). Following are the first few: The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041033 \\".\"\r\n }\r\n ]\r\n }\r\n}"}]}

Logs attached: 2.24.0.0.zip

Seems related to: #1951

[cmptscpeacock]

This is still happening. Is anyone able to look into it? As above, the FSW domain-joins but fails when it gets to SQL-0 and SQL-1 with the above error:

The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041033

Deploying to UK South / West Europe.

[loothood]

This is still happening. Is anyone able to look into it?

[loothood]

@robotechredmond could you take a look this? From logs:

VERBOSE: [2019-01-30 17:01:51Z] Executing Start-DscConfiguration... VERBOSE: [2019-01-30 17:01:52Z] Settings handler status to 'transitioning' (C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\Status\0.status) VERBOSE: [2019-01-30 17:01:55Z] [VERBOSE] Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'. VERBOSE: [2019-01-30 17:01:55Z] [VERBOSE] An LCM method call arrived from computer 14-sql-0 with user sid S-1-5-18. VERBOSE: [2019-01-30 17:01:55Z] [VERBOSE] [14-sql-0]: LCM: [ Start Set
] VERBOSE: [2019-01-30 17:02:14Z] [ERROR] The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041033 VERBOSE: [2019-01-30 17:02:14Z] [VERBOSE] Operation 'Invoke CimMethod' complete. VERBOSE: [2019-01-30 17:02:14Z] [VERBOSE] Time taken for configuration job to complete is 19.039 seconds

if you need additional info, please ask me