Backup Windows Agents results in Error Managed Session

[George_Washington]

Hello,

I've tried using Google and the search-function in the Community Forums, but till this day I haven't found the answer to our problem.

We are currently trying to backup a Windows Server using the Veeam Agent for Windows (2.1 / v9.5u3) and everytime the job fails with the following message:



I've searched for logs (couldn't find any logs. Where are they stored?), I've wiresharked, I've disabled/removed all firewalls, ACL and UAC, but couldn't still find the culprit. Other agent-backups (mostly Linux-systems) are working like clockwork, but when it gets to Windows..

Does anyone have a possible idea what it might be or point me in the right direction where to look for?

Thank you.


George.

[Vitaliy S.]

All the logs are located over here. Also please open a support case if you need help troubleshooting the issue as it is advised by our forum rules when you click New Topic. Thanks!

[George_Washington]

Hi Vitaly,

I've managed to export all the logs that are relevant to this case due to the URL you provided. I thank you for that.

Regarding creating a Veeam Support-ticket; I'm not a Veeam customer (yet) and we're still testing Veeam on a trial-basis/licence. Don't know it that grants me the right to create a support ticket and that's why I've created a topic on the Community Forum

[Dima P.]

George_Washington,

We provide support for both trial and free edition, so you are welcome to open a support case directly via customer support portal.

[Dmitry1]

George, was you able to solve this problem?

[Dima P.]

Hi Dmitry1,

If you faced the same problem please open a support case and do not forget to share the case ID. Thank you in advance.

[ronnmartin61]

Ran into the same issue. Turned out it was due to lack of name resolution support in my test cloud environment. Looks like the VBR server sends its FQDN to the target agent during setup. If the agent cannot then resolve the FQDN successfully it results in this error (at least in my test environment). Adding an appropriated hosts file entry and restarting the Veeam endpoint service cleared the issue.

[Dima P.]

Hi Ronn,

That's correct. Host name should be resolvable from the VBR side and agent should also be capable of resolving the VBR host name.

[gurneetech]

Just wanted to mention the solution helped me out this morning. I had converted a couple of Windows agents from unmanaged to centrally managed and the new jobs were failing with this error.

Turns out there was a DNS issue for the VBR server - it wasn't resolvable both directions from the clients. Not being part of the domain, I didn't have all of the manual records in place.

Anyway, thanks to those that confirmed the solution.

[dw432948jkk]

It took us hours to see a connection between the error message and the cause. Perhaps veeam should improve the description of error messages here , since these often do not establish a connection to the actual cause.

Thanks to this post, it now works for us too.

By the way, it only occurred in workgroup environments.

[Dima P.]

Peter,

Thanks for the heads up! Completely agree, I'll check with RnD folks is we can make it more 'human readable'. Cheers!