Maintain control of your Microsoft 365 data
Post Reply
dave.moreland
Service Provider
Posts: 7
Liked: 3 times
Joined: Sep 10, 2020 7:29 pm
Full Name: dave moreland
Contact:

Proxy upgrade failing

Post by dave.moreland »

Hello,
I have case 07211444 open for my issue. No one is available from the support team and I was hopping someone might have a quicker answer here.

I have been trying to upgrade my environment and 2 proxies will not upgrade, they timeout stopping the veeam.archiver.proxy service. If I try to restart the upgrade while the service is stopping or stopped, after a hour or so I get an error that the service is not reachable.

What are the steps to manually install the new veeam.archiver.porxy service?

The proxies are currently on version 7.0.0.4388 and I'm trying to upgrade to 7.1.0.1501

Thank you for your time,
Dave
rtheseeker
Enthusiast
Posts: 75
Liked: 4 times
Joined: Sep 26, 2022 9:13 pm
Full Name: Rajeev Mehta
Contact:

Re: Proxy upgrade failing

Post by rtheseeker »

never ran into this issue; what does the event log on the proxy say; usually proxy is just a service; I had even manually upgraded the dll files on office365 server (private fix) and upgraded the proxies.
dave.moreland
Service Provider
Posts: 7
Liked: 3 times
Joined: Sep 10, 2020 7:29 pm
Full Name: dave moreland
Contact:

Re: Proxy upgrade failing

Post by dave.moreland »

The logs showed it flipping between versions, it would run on the new version then stop and go back to the old. It did that multiple times and started a new log file each time the service restarted so there is a mess of log files.

I ended up grabbing the binaries from the Archiver Server in the C:\Program Files\Veeam\Backup365\Packages\Proxy and copying them into a blank C:\Windows\Veeam\Backup365Proxy folder on the proxy servers.

This got me back online with some anomalies in the console gui like the incorrect version showing and a status of "update failed". I did confirm in both the Archiver logs and the Proxy logs that the version was correct and all the errors about mismatched versions disappeared.

The jobs ran fine through the night and the version is showing correctly this am in the console gui with only the "update failed" status remaining now. I suspect that will clear with time.
Post Reply

Who is online

Users browsing this forum: No registered users and 69 guests