Worker deployment failed

[gtelnet]

Hey all, haven't created a ticket yet but will do so if no one else from the community has any input on this error. I didn't find any of the keywords in the forum either so thought it would be good to post here to make the resolution easy for others to find.

Repository backup of prodservername to blobstoragename has failed (Cannot find any workers. Worker deployment failed, see logs for details (eventID: -1792320529) (waiting ticket: 4))

This is a brand new deployment of Azure VBA. The snapshot runs successfully but the backup to blob portion of the job fails. The account that was used to deploy the vba has the Owner and Key Vault Crypto User roles for the subscription. The default worker configuration looks correct on the vba but there are 0 worker instances showing so it seems that the vba cannot spawn a worker when needed. I also see that the 'waiting ticket:' number keeps increasing every time the jobs runs. Thank you!

[nielsengelen]

It may be an issue with resource availability within the region but it is a guess at this point. I would advise to just open a ticket so you can get help via our support. Can you let us know the ID once you made the case?

[AlexLudwig-ITDienst]

Hi gTelnet,

did you try to register the Microsoft.ServiceBus Ressource Provider manualy in your Azure Subscription?
In my case this was the solution, because veeam vba did't activate it itself.

[gtelnet]

Thank you! @AL-TD-ITS - couldn't find any steps online on how to create the ServiceBus resource provider manually and have never done that before.

Will open the ticket now. thanks!

[gtelnet]

Update - I manually created the Microsoft.ServiceBus Ressource Provider through the Service Bus interface in Azure and backup worked! Thank you for pointing me to that @AL-TD-ITS !!

[nielsengelen]

Great news and thanks a lot Alex for sharing this with the community!

[AlexLudwig-ITDienst]

Thank you very much. It's just a small configuration with a big impact.
It can also be registrated through powershell:
Register-AzResourceProvider -ProviderNamespace Microsoft.ServiceBus

Because of this simple fix, @nielsengelen could veeam integrate this and enable it itself ?

[nielsengelen]

We will pass the information on and will try to find the root cause of the issue. It could be this is a bug or potentially something specific to certain regions.

[pgazo@yesonsite.com]

Just adding that the same issue happened to us with a new install, and the same PowerShell command resolved it.

Our region is Canada Central, if that's helpful.

[AlexLudwig-ITDienst]

This issue will occur for all customers who don't have this resource provider enabled in their subscriptions. For this reason I asked nielsengelen to implement the registration in Veeam itself.

[Vitaliy S.]

Thanks for the heads up, guys! While enabling this automatically sounds good, this will require permissions for VB to have access to other service management which I guess is not ideal. We will implement the proper validation of the missing service in our next update.

[ITP-Stan]

Ran in to the same problem just now.
Thanks for this post with the answer.

In Azure activity log i could finally see the error.

The subscription is not registered to use namespace 'Microsoft.ServiceBus'. See https://aka.ms/rps-not-found for how to register subscriptions.

Installing Az powershell module and running the "Register-AzResourceProvider -ProviderNamespace Microsoft.ServiceBus" command now.

[nielsengelen]

Hi Stan,

Thanks for letting us know. Please update us if it then works for you.

[ITP-Stan]

I had to wait for at least 10 minutes after the command to get it to work.
I then had different errors, about permissions on the storage account. But because of my earlier trying this and that, I decided to create a new storage account and blob container and it finally worked.