This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 10%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Hi,
Been trying to deploy a marketplace VM image, tried for both ubuntu and sql2017 VM
Keep getting status conflict error when provisioning the VMs.
Error code: FabricVMCreationError
Not sure how to go about troubleshooting it, any specific log that we can see to narrow it down?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Sincere apologies on the delay. I am reaching out to the right team to help with Azure stack expertise and will get back to you as soon as I have an update. Thanks.
Are you using the ASDK or a full Azure Stack Hub Multi-node installation?
This error is typically an issue with Azure Stack, so lets start by checking to see if a role is functioning properly by using test-azurestack on the PEP. If there is a role that is not functioning properly and is preventing deployment, it should show up there. If any roles come up with an issue, please post them here.
Hi TravisCragg,
Thanks for the follow up. I am working on ASDK. Previously I did come across an error during test-Azure, "Failed - fabric management application services". Any follow up I can work on regarding this?
I am currently not able to access the ASDK, will post back more detail on Monday.
Thanks again!
Hi all,
I have rerun the "test-Azurestack" command. There is this 1 failed error: "FAIL Azure Stack Fabric Management Controller Service Fabric Applications" as shown in the screenshot below. Any guidance on this? Any logs or actions to narrow down the issue? Thank you.
Manage to get passed all test cases after restarting the fabrichostSvc service in AzS-XRP01 using the PS command below:
(Get-Service -ComputerName AzS-XRP01 -Name
"FabricHostSvc").stop()/start()
However the VM deployment still have the same conflict error, with code "FabricVMcreationError"
Please advise.
Hi,
Bump. Any support on this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 56.00000000000001%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
Hi, have you opened a case with Azure Support? They can perform debug operations from the PEP, from my experience is better to work with them. May I ask which version of Azure Stack hub are you running? As far as I remember, there is a well known issue on deploying some sizes of VMs on specific versions of the stack.
Have you tried to change the VM size before reruning the template? There are other errors or alerts on your stamp?
Hi,
This is an ASDK setup. Will there be Azure support for it?
Able to provide the link on the known issue pertaining to VM deployment using certain size?
There wasn't any additional errors or alerts on the portal. Possibly from azure stack logs which i need guidance on which logs to see as there just too many logs generated using get-azurestacklog
Thank you
In the case of a failed role, the best bet is to stop and start the ASDK.
Your true best bet is to use the most recent ASDK version. Version 2008 just released, and we highly recommend using the most up-to-date version.
Hi,
The SDK doesn't have the support from Microsoft, and should not be used for productive environments. About the SDK, it is pretty different to an Azure Stack Hub. The know issue I refered to corresponds to the Stack Hub version 2002 (https://learn.microsoft.com/es-es/azure-stack/operator/known-issues?view=azs-2002#compute)
About your sdk, it's the first VM you're deploying? Are you sure there is enough capacity (cores, memory and storage) to deploy it?
I don't know if this can help you: https://social.msdn.microsoft.com/Forums/azure/en-US/db94c1f2-ba0d-49c9-b518-c34e2873d7bb/asdk-new-install-unable-to-deploy-a-vm-timeouts?forum=AzureStack
After the official documentation, restarting the VMs of the SDK (especially AzS-Xrp01) can cause instability of the SDK.
Hope this helps you in the right direction