Monitoring and reporting for Veeam Data Platform
Post Reply
dpal
Novice
Posts: 9
Liked: 2 times
Joined: Feb 15, 2017 2:01 pm
Contact:

After Migrating VeeamOne to a new host, cannot install\update VeeamOne agent on BnR server

Post by dpal »

Hello All,
I migrated our VeeamOne installation to a new host today by using this guide, and everything seemed to go smoothly until I got to step 10. I went to the VeeamOne Agents tab and saw my BnR server listed, but the Agent Status said Installation Failed. There were no available options to repair or remove(greyed out). When I tried to install, I got the same Installation failed status with a message saying "Bad Net Path." I have already opened a case on this(Case 07281455), but hoping to get some guidance from you fine folks as well.

Thanks,
David
jorgedlcruz
Veeam Software
Posts: 1441
Liked: 635 times
Joined: Jul 17, 2015 6:54 pm
Full Name: Jorge de la Cruz
Contact:

Re: After Migrating VeeamOne to a new host, cannot install\update VeeamOne agent on BnR server

Post by jorgedlcruz »

Hello dpal,
Usually is quite tricky to troubleshoot such issues over the forum, because that error most likely is something regarding domain joined, perhaps some firewall, of some other SSL or network problems.

It is a bit generic in the interface, but surely our Support Engineers will see the correct error in the logs, and provide with a deeper analysis and steps to fix it.

Keep us posted!

Thanks a lot, and great work doing the whole migration, I tried a few times and it surely takes its time.
Jorge de la Cruz
Senior Product Manager | Veeam ONE @ Veeam Software

@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2024 / InfluxAce / Grafana Champion
dpal
Novice
Posts: 9
Liked: 2 times
Joined: Feb 15, 2017 2:01 pm
Contact:

Re: After Migrating VeeamOne to a new host, cannot install\update VeeamOne agent on BnR server

Post by dpal » 1 person likes this post

Looks like we got it fixed. I started searching the logs for the servername of our BnR server and saw where VeeamOne was trying to talk to it on port 2805. It looks like NSX wasn't allowing that communication through. Once that was opened up, I was able to push the agent to our server.

Thanks!
David
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests