Skip to main content

Build new windows (2022) server for Veeam B7R 12.3.2.4165 and imported the config from older server.

Since then every backup job has a warning “Sending e-mail report Details: Failed to wait mutex VeeamMailServiceAzureToken: timeout 00:01:00 sec exceeded”  

Opening options takes sometimes 10 min or more, but when it does I can send test mails successfully.

After saving the first backups work with email, after a day its the same error.

When opening options sometimes this message appears: 

I don't know what's wrong here server has plenty of power.

Grtz.

Bart

 

P.s. old server did not have this problem.

 

Hmmm...interesting behavior ​@HbvdH . Sounds like you’re using M365 auth for email? Can you just re-token it and see if it works more consistently?


I suggest you open a support case. I had the same problem a few months ago, and support solved it.


I also assume that you have to re-token it since the footprints may not be included (consistently) in the config backup file.

Please also check your FW policies to avoid any kind of block actions.


I have seen when restoring configuration backups depending on what you are using for email (in your case M365) you need to click that Authorize now link to fix things.  Many above have mentioned this as well and I have seen it recently.  Otherwise Support should be able to assist.


When I re-authorize it works for about a day, then the same warnings.

 

Well I did re-authorize today, test mail went fine and showing Token is valid, we wil see tomorrow.


Ah ok...so you did re-auth. Yeah...then probably Support is your best route ​@HbvdH . Keep us posted how it goes.

Best.


I suggest you open a support case. I had the same problem a few months ago, and support solved it.

Do you know what support did?


I suggest you open a support case. I had the same problem a few months ago, and support solved it.

Do you know what support did?

You will need to contact support as each case would be slightly different.  Let us know what they say.


Today the same as yesterday, token authorization required, now switched to smtp email, and everything is responsive now. Will wait if this breaks too tomorrow.


Today the same as yesterday, token authorization required, now switched to smtp email, and everything is responsive now. Will wait if this breaks too tomorrow.

What did support say about the issue?  Hopefully SMTP works well.


Thanks for the update ​@HbvdH