ARM Templates: StorageAccounts/FileServices ERROR "Status Message: XML specified is not syntactically valid."

Mauro Masucci 6

Getting the following error with my ARM template

17:25:32 - Status Message: XML specified is not syntactically valid.
17:25:32 - RequestId:599711fc-c01a-009b-5b4a-26da63000000
17:25:32 - Time:2021-03-31T16:24:41.9627334Z (Code:InvalidXmlDocument)
17:25:32 -
17:25:32 - CorrelationId: e059d318-89ba-436a-9a21-9a06dc18a09d

Other than parameterising the name for the storage account I havent tweaked them, and I can't find any XML or reference to this issue anywhere.

{
"type": "Microsoft.Storage/storageAccounts/fileServices",
"apiVersion": "2021-01-01",
"name": "[concat(variables('StorAccName'), '/default')]",
"dependsOn": [
"[resourceId('Microsoft.Storage/storageAccounts', variables('StorAccName'))]"
],
"sku": {
"name": "Standard_LRS",
"tier": "Standard"
},
"properties": {
"protocolSettings": {
"smb": {}
},
"cors": {
"corsRules": []
}
}
},

4 answers

Matt Allford 116 Reputation points

2021-04-09T04:11:27.237+00:00

I just came across this as well, and I think it is to do with the apiVersion being used when exporting the template from an already deployed resource.

I changed my templated to use 2019-06-01, instead of the 2021-01-01 that was being used for Microsoft.Storage/storageAccounts/fileServices, and deployment then worked OK.

Edit: Actually, that wasn't it. I removed the following empty sections from the template, and the deployment works. When this is put back in, it fails again regardless of the API version.

"protocolSettings": {
"smb": {}
},
"cors": {
"corsRules": []
},
Please sign in to rate this answer.

23 people found this answer helpful.
Nick Purington 41 Reputation points

2021-04-09T19:12:21.973+00:00

@Matt Allford

I had the same issue and was able to resolve using your approach (Thank you!).

Just to piggyback on your comment - Looking at the Microsoft.Storage/storageAccounts/fileServices template format (https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/storageaccounts/fileservices?tabs=json#template-format), I noticed that the "smb": {} value is not included in the template format so it is most likely the culprit of the error. I left the "cors": {"corsRules": []} values and my test storage account deployment was successful.

Not sure why Azure is creating template exports of existing resources with this value included, but at least we found a solution.

josef-fuerlinger 21 Reputation points

2021-04-10T08:08:06.347+00:00

As @Nick Purington mentioned it's just the not documented protocolSettings section:

"protocolSettings": {
"smb": {}
},

Remove it and the template will deploy successfully.

Saadou Yaye, Abdoulaye 16 Reputation points

2021-08-06T22:23:38.337+00:00

THANK YOU!

Saadou Yaye, Abdoulaye 16 Reputation points

2021-08-06T22:33:11.77+00:00

This definitely worked for me. Thank you!

Dennis Nguyen 11 Reputation points

2021-12-24T22:09:32.95+00:00

This worked like a charm. Thank you so much

Antti Viita 1 Reputation point

2022-02-15T07:00:13.957+00:00

I got bit forward with removal above mentioned smb removal, but got different error regarding "Microsoft.Storage/storageAccounts/fileServices/shares", which of course is not highlighted by az deploy and only visible from deployment in azure portal in resource group's Deployments section. Just started studying ARM templates (again) and thought I give template export a try with this simle example setup and try to replicate the manually done setup to another location.

I also tried setting some default values based on json documentation from following link, which still produced the same error:
https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/2021-06-01/storageaccounts/fileservices?tabs=bicep#smbsetting

The error I got was:

Deployment failed. Correlation ID: 8984b13d-de71-4e6e-bded-e33b10f49dea. {
"error": {
"code": "InvalidHeaderValue",
"message": "The value for one of the HTTP headers is not in the correct format.\nRequestId:162a2ffa-501a-0029-3037-22e5d1000000\nTime:2022-02-15T06:41:33.6780993Z"
}
}

Finally I checked Azure function documentation for storage requirements and since the fileshare does not seem to be a mandatory requirement, I also ended up removing definition for:

"type": "Microsoft.Storage/storageAccounts/fileServices/shares"

Richard Davis 6 Reputation points

2022-05-11T20:14:16.71+00:00

yep worked for me, thanks

na 121 Reputation points

2022-08-04T13:25:49.323+00:00

Currently facing this issue, and durable functions require shares so it cannot be removed in all cases.

gserra 0 Reputation points

2023-07-31T12:57:50.5466667+00:00

I've been able to fix thanks to that
Sign in to comment
deherman-MSFT 33,296 Reputation points Microsoft Employee

2021-04-01T20:24:35.56+00:00

@Mauro Masucci
I believe the issue is that you are specifying the type as Microsoft.Storage/storageAccounts/fileServices. It should simply be Microsoft.Storage/storageAccounts. You can refer to this thread for more information and tips.

Hope this helps! Let us know if you are still facing issues or have further questions.

-------------------------------

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Mauro Masucci 6 Reputation points

2021-04-02T08:55:07.793+00:00

I generated the ARM template from my manually set up storage account, it needs file shares for my azure functions to connect to. Should I not create them? Are they automatically generated by the Azure Function when it connects?

Jan-Jaap Spies 0 Reputation points

2023-03-09T14:39:45.5333333+00:00

@deherman-MSFT

This is a bit old, but still current. I've just exported a resource group and its resources to an ARM template, and this mentions 'Microsoft.Storage/storageAccounts/fileServices'. On re-importing this template Azure complains that there is a bad request and this has somehow to do with the section described by @Matt Alford above. This seems to be a bug to me, not a feature.
Sign in to comment
aleksejsp 1 Reputation point

2021-05-24T09:01:15.253+00:00

Thanks for the post, it helped!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Jesse 1 Reputation point

2021-11-30T07:21:52.473+00:00

@Matt Allford Thanks for your hint, this probably saved me 10 hours or so ;)
Please sign in to rate this answer.
Srinivasa Raju Kosuri 1 Reputation point

2022-09-27T10:06:44.69+00:00

Thanks all. This helped me to deploy successfully. Removed SMB property under properties.
Sign in to comment