SharePoint HA farm - deployment template parse failed.

[mrjadez]

Sharepoint-server-farm-ha

Issue Details

On deploying via the deploy button or via downloading the ARM template, the deployment fails with UI showing the following on the Deploy screen: "Deployment template parse failed: 'After parsing a value an unexpected character was encountered: ". Path 'resources[2].properties.settings.modulesURL', line 260, position 11.'. (Code: InvalidTemplate)"

No changes were made to the template. Deploy button from the github template itself was used.

[arroyc]

looking into it

[arroyc]

pull request #2328

[mrjadez]

Hi Arjun,

Tried another deployment after the dscv2 folder was put back in, the initial deployment starts but fails on Resource "Configuring SQL Always On Cluster" with the following message:

\"message\": \"VM has reported a failure when processing extension 'CreateCluster'. Error message: \"DSC Configuration 'ConfigureFailoverCluster' completed with error(s). Following are the first few: Cannot add computer 'sql-1' to domain 'wahrgsuat.local' because it is already in that domain. The PowerShell DSC resource '[xComputer]DomainJoin' with SourceInfo 'C:\Packages\Plugins\Microsoft.Powershell.DSC\2.20.0.0\DSCWork\ConfigureFailoverCluster.ps1.1\ConfigureFailoverCluster.ps1::85::9::xComputer' threw one or more non-terminating errors while running the Set-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details. The SendConfigurationApply function did not succeed.\".\"\r\n }\r\n ]\r\n }\r\n}

Thanks.

[arroyc]

this happens usually when you have a failed deployment earlier and you try to redeploy again. I would suggest you to 1. delete all the resourcegroups you have used earlier for sharepoint deployment or 2. change the names in the parameter file wherever you see GEn-unique

[mrjadez]

Cool thanks, I made sure the resource groups were deleted. It must be some unquie name, I'll check the parameters as you suggested.

Thanks.

On Friday, 12 August 2016, Arjun Roy Chaudhuri notifications@github.com wrote:

this happens usually when you have a failed deployment earlier and you try to redeploy again. I would suggest you to 1. delete all the resourcegroups you have used earlier for sharepoint deployment or 2. change the names in the parameter file wherever you see GEn-unique

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-quickstart-templates/issues/2326#issuecomment-239220536, or mute the thread https://github.com/notifications/unsubscribe-auth/AT7eprq7lMkw2r6CP0uaNhdaxnHEWZMCks5qe1LPgaJpZM4Jesn5 .

J.

[mrjadez]

Hi Arjun,

Changed all the parameters, domain name etc. Again fails at SQL Cluster setup with the following error:

Error message: \"DSC Configuration 'ConfigureFailoverCluster' completed with error(s). Following are the first few: PowerShell DSC resource MicrosoftAzure_xCluster failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable \"ErrorActionPreference\" or common parameter is set to Stop: An error occurred while performing the operation.\n An error occurred while creating the cluster 'wahrgsfarm-fc'.\n An error occurred creating cluster 'wahrgsfarm-fc'.\n The object identifier does not represent a valid object The following exception occurred while trying to enumerate the collection: \"Failed to connect to server wahrgs-sql-0.\". The PowerShell DSC resource '[xSqlEndpoint]SqlSecondaryAlwaysOnEndpoint' with SourceInfo 'C:\Packages\Plugins\Microsoft.Powershell.DSC\2.20.0.0\DSCWork\ConfigureFailoverCluster.ps1.1\ConfigureFailoverCluster.ps1::198::9::xSqlEndpoint' threw one or more non-terminating errors while running the Test-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.\"."

Thanks.

On Fri, Aug 12, 2016 at 2:49 AM, Javed Asghar javed.asghar@gmail.com wrote:

Cool thanks, I made sure the resource groups were deleted. It must be some unquie name, I'll check the parameters as you suggested.

Thanks.

On Friday, 12 August 2016, Arjun Roy Chaudhuri notifications@github.com wrote:

this happens usually when you have a failed deployment earlier and you try to redeploy again. I would suggest you to 1. delete all the resourcegroups you have used earlier for sharepoint deployment or 2. change the names in the parameter file wherever you see GEn-unique

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-quickstart-templates/issues/2326#issuecomment-239220536, or mute the thread https://github.com/notifications/unsubscribe-auth/AT7eprq7lMkw2r6CP0uaNhdaxnHEWZMCks5qe1LPgaJpZM4Jesn5 .

J.

J

[mrjadez]

Also the notes say that the template uses the latest SharePoint 2013 trial image, however the actual product installed on the SharePoint VMs is Sharepoint 2016. Has this been upgraded and notes not reflecting this?

On Fri, Aug 12, 2016 at 1:47 PM, Javed Asghar javed.asghar@gmail.com wrote:

Hi Arjun,

Changed all the parameters, domain name etc. Again fails at SQL Cluster setup with the following error:

Error message: \"DSC Configuration 'ConfigureFailoverCluster' completed with error(s). Following are the first few: PowerShell DSC resource MicrosoftAzure_xCluster failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable \"ErrorActionPreference\" or common parameter is set to Stop: An error occurred while performing the operation.\n An error occurred while creating the cluster 'wahrgsfarm-fc'.\n An error occurred creating cluster 'wahrgsfarm-fc'.\n The object identifier does not represent a valid object The following exception occurred while trying to enumerate the collection: \"Failed to connect to server wahrgs-sql-0.\". The PowerShell DSC resource '[xSqlEndpoint]SqlSecondaryAlwaysOnEndpoint' with SourceInfo 'C:\Packages\Plugins\Microsoft.Powershell.DSC\2.20.0.0\DSCWork\ ConfigureFailoverCluster.ps1.1\ConfigureFailoverCluster.ps1::198::9::xSqlEndpoint' threw one or more non-terminating errors while running the Test-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.\"."

Thanks.

On Fri, Aug 12, 2016 at 2:49 AM, Javed Asghar javed.asghar@gmail.com wrote:

Cool thanks, I made sure the resource groups were deleted. It must be some unquie name, I'll check the parameters as you suggested.

Thanks.

On Friday, 12 August 2016, Arjun Roy Chaudhuri notifications@github.com wrote:

this happens usually when you have a failed deployment earlier and you try to redeploy again. I would suggest you to 1. delete all the resourcegroups you have used earlier for sharepoint deployment or 2. change the names in the parameter file wherever you see GEn-unique

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-quickstart-templates/issues/2326#issuecomment-239220536, or mute the thread https://github.com/notifications/unsubscribe-auth/AT7eprq7lMkw2r6CP0uaNhdaxnHEWZMCks5qe1LPgaJpZM4Jesn5 .

J.

J

J

[mrjadez]

Found that the variable for SharePoint SKU has now been defaulted to "2016" can we please change readme to reflect this and let others know to change this to revert back to 2013 please. Thanks.

On Fri, Aug 12, 2016 at 2:06 PM, Javed Asghar javed.asghar@gmail.com wrote:

Also the notes say that the template uses the latest SharePoint 2013 trial image, however the actual product installed on the SharePoint VMs is Sharepoint 2016. Has this been upgraded and notes not reflecting this?

On Fri, Aug 12, 2016 at 1:47 PM, Javed Asghar javed.asghar@gmail.com wrote:

Hi Arjun,

Changed all the parameters, domain name etc. Again fails at SQL Cluster setup with the following error:

Error message: \"DSC Configuration 'ConfigureFailoverCluster' completed with error(s). Following are the first few: PowerShell DSC resource MicrosoftAzure_xCluster failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable \"ErrorActionPreference\" or common parameter is set to Stop: An error occurred while performing the operation.\n An error occurred while creating the cluster 'wahrgsfarm-fc'.\n An error occurred creating cluster 'wahrgsfarm-fc'.\n The object identifier does not represent a valid object The following exception occurred while trying to enumerate the collection: \"Failed to connect to server wahrgs-sql-0.\". The PowerShell DSC resource '[xSqlEndpoint]SqlSecondaryAlwaysOnEndpoint' with SourceInfo 'C:\Packages\Plugins\Microsoft.Powershell.DSC\2.20.0.0\ DSCWork\ConfigureFailoverCluster.ps1.1\ConfigureFailoverCluster.ps1::198::9::xSqlEndpoint' threw one or more non-terminating errors while running the Test-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.\"."

Thanks.

On Fri, Aug 12, 2016 at 2:49 AM, Javed Asghar javed.asghar@gmail.com wrote:

Cool thanks, I made sure the resource groups were deleted. It must be some unquie name, I'll check the parameters as you suggested.

Thanks.

On Friday, 12 August 2016, Arjun Roy Chaudhuri notifications@github.com wrote:

this happens usually when you have a failed deployment earlier and you try to redeploy again. I would suggest you to 1. delete all the resourcegroups you have used earlier for sharepoint deployment or 2. change the names in the parameter file wherever you see GEn-unique

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-quickstart-templates/issues/2326#issuecomment-239220536, or mute the thread https://github.com/notifications/unsubscribe-auth/AT7eprq7lMkw2r6CP0uaNhdaxnHEWZMCks5qe1LPgaJpZM4Jesn5 .

J.

J

J

J

[arroyc]

looking into it ..

[arroyc]

still looking into it ... will update once find the fix... sorry for the inconvenience

[mrjadez]

Thanks, I think the readme also need to be updated to show that the variable inside the script has now defaulted to SharePoint 2016 not 2013 as the readme suggests.