Skip to main content

[Quicktip] Licensing error during backup


vNote42
Forum|alt.badge.img+13
  • On the path to Greatness
  • 1246 comments

These days I saw a strange error that makes every backup failed. I thought this would be interesting to share. 

Situation

There were a few jobs running each day. From a point in time all jobs failed. Error that was shown in console was:

 

[Error Unhandled exception was thrown during licensing process]

 

I checked licensing of course. All hosts were licensed using perpetual licensing. No instances were licensed separately.

Solution

It turned out to be no license problem at all. What happened was, password of the user that was used for connecting to VMware vCenter was changed. After updating the new password in Veeam Manage Credentials too, everything works fine again.

15 comments

wolff.mateus
Forum|alt.badge.img+11
  • Veeam Vanguard
  • 529 comments
  • February 10, 2021

Rise your hand for who passed for this problem too!

:raised_hands_tone1:

 

Thanks for this post @vNote42.


JMeixner
Forum|alt.badge.img+17
  • Veeam Legend, Veeam Vanguard
  • 2641 comments
  • February 10, 2021

When I remember correct, I have seen this error as I have used VEEAM for the first two weeks.

But as nothing else was working I suspected that the connection to the vCenter was faulty at first place.

So I did not take too much notice at this error… I was glad to get the whole thing working again.


gulzarshaikhveeam
Forum|alt.badge.img+1

It will be nice to have a more relevant error, roll up your sleeves developers.. :grinning:


gulzarshaikhveeam
Forum|alt.badge.img+1

Thanks for sharing mate


ProfessionalITPerson

@vNote42 absolute life saver mate. Was scratching my head for ages trying to figure this out. 


Mildur
Forum|alt.badge.img+12
  • Influencer
  • 1033 comments
  • April 13, 2021

@vNote42 Thank you. You helped me with this one :)


  • New Here
  • 1 comment
  • December 6, 2021

Thx for that.


vNote42
Forum|alt.badge.img+13
  • Author
  • On the path to Greatness
  • 1246 comments
  • December 6, 2021
TechINFO wrote:

Thx for that.

with pleasure! 


  • New Here
  • 1 comment
  • August 22, 2022

Perfeito! 

Muito obrigado, @vNote42 . 


vmJoe
Forum|alt.badge.img+8
  • Veeam MVP
  • 66 comments
  • August 23, 2022

Great observation! Thanks for sharing!


  • New Here
  • 1 comment
  • October 14, 2022

I got the same Veeam error too, but for me the problem was situated in the VMWare environment and not in Veeam. There was a problem with the VSphere VCS appliance and the VSphere website gave a "no healthy upstream” error message. After repairing the VCS appliance everything worked OK again in VEEAM.


HunterLAFR
Forum|alt.badge.img+8
  • Veeam Legend
  • 420 comments
  • October 14, 2022

🙋🏽

I also went through the issue when you re-add machines for a failure, or new datastore migration or something, and we run out of vms licenses, and needed to go to veeam console, unassigned all vms to their licenses, and when the tests were re-launched, all vms were having licenses again.

It is a bit awkward the first time you see it, after that, you check it like a robot!

cheers.


Michael Melter
Forum|alt.badge.img+12

Just faced the issue with a SAP HANA plugin job. No PW changes at all here.

But it went away in the next cycle. Quite misleading message.


  • New Here
  • 1 comment
  • May 22, 2023

I know this thread has been long and may not be relevant to the newer Veeam BS version. The more interesting because I first got this error on version 12.0.0.1420. Unlike the first comment, I did not have to do anything to solve, the account to VCS was OK, VCS worked, after about 10min I made rescan at VCS and again launched a backup .... developers Veeam “This is not a good business card”


  • New Here
  • 1 comment
  • December 31, 2024

Spot on, thanks for helping me avoid going round in circles.


Comment