Failed to retrieve licenses for users

[Talom]

Hello,

Veeam keeps telling me it cannot retrieve licenses.
10.05.2022 16:28:35 :: Failed to retrieve licenses for 1 users

I am using the community edition. I have 9 Users in my organization.
Get-VBOLicensedUser creates no output at all.

I think it started after i installed v6.

[Mildur]

Hi Talom

I'm running version 6 and have no issues to get the licensed user.
Can you please open a support case and post your Case Number?

Thank you
Fabian

PS: support can only help if you export and upload logs

[ddasal]

Did you find a resolution to this? I am having a similar issue. Case ID is 05449428

[Mike Resseler]

@ddasal

Most likely you will connect to a user in M365 and we fail to check if that specific user has an M365 license connect to it.

[ddasal]

We have a M365 G3 GCC licensing model (and it is assigned via inheritance). Any issues with that?

[ddasal]

Here is what I see in the logs (which was uploaded to Support):

Found: <omitted user full name>, SMTP: <omitted user email address>, mailbox ID: <omitted>-294170f03b03
Obtaining license for: <omitted user login@domain>...
Failed to obtain license
Error: The open operation did not complete within the allotted timeout of 00:00:00. The time allotted to this operation may have been a portion of a longer timeout.

[ddasal]

Support had me re-deploy the organization (open and restart the wizard) letting it re-create the application in Azure. I tried this once before without any success. This time around the application name did not include any spaces (may or may not be relevant), and it was able to process the mailboxes and find licensing accordingly. Odd, but it is working.

[Polina]

Hi Dustin,

I'm glad that your issue has been finally resolved.
Can't be sure without seeing your logs and case details, but I'd assume that some of the app permissions were missing and that's why re-creating an app helped.

Cheers!

[Talom]

Our problem was, we changed the hostname of our server. This is not supported yet.
We had to reset our configuration.

[Mike Resseler]

Changing the hostname of the server gets you into problems with the name in the certificate. Indeed resetting the configuration should do the trick then

[HangTen]

Hello! I am following up on this and have a few questions. In the case of changing the hostname of the server, does changing it back to the original fix the issue? Also, is there a link to a KB which outlines the process for resetting the configuration? Does anyone have any quick workarounds for this issue?

[Mildur]

Hi Hin Tang

Changing it back will solve the issue.
Migration to a new hostname requires a reset of the VB365 configuration. We have documented both options in our KB article: https://www.veeam.com/kb4296

Best,
Fabian