I was running the Community Edition ver. 8.2.0.2202 on my Windows Server 2025 when a notice appeared to install the latest update for Veeam Backup for Microsoft 365 8.3. (Community Edition)
I did that upgrade but it jacked up my system. I got an "Installation Failure" with no useful information in the log. After much searching, I found this https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/unable-to-install-vbo365-on-a-fresh-windows-11-system-t101611.html
I used some of the suggestions there and I finally got 8.3.0.2201 installed.
But now I get the "No connection could be made b/c the target machine refused it." I briefly saw something about a installation issue with multi-homed servers, but I cannot find that page again.
Solved
Veeam Backup for Microsoft 365 8.3 Apparently has problems with Windows server 2025
Best answer by MicoolPaul
Are your services running? Are the ports open on windows firewall? What logs do you get when it starts.
+21I would contact support about this and have them assist as there could be something as you have noted.
I edited my original post to clarify that I am running the Community Edition for a few mailboxes only.
Veeam technical support for the Community Edition not a priority.
I would contact support about this and have them assist as there could be something as you have noted.
I edited my original post to clarify that I am running the Community Edition for a few mailboxes only.
Veeam technical support for the Community Edition not a priority.
+21I would contact support about this and have them assist as there could be something as you have noted.
I edited my original post to clarify that I am running the Community Edition for a few mailboxes only.
Veeam technical support for the Community Edition not a priority.
Well I would still try or downgrade your OS.
I would contact support about this and have them assist as there could be something as you have noted.
I edited my original post to clarify that I am running the Community Edition for a few mailboxes only.
Veeam technical support for the Community Edition not a priority.
Well I would still try or downgrade your OS.
I know you are trying to be helpful, but “downgrade your OS is probably the worst idea I’ve heard of. I’m a one-server installation, and I’m not going through that grief.
What makes sense is to actually roll back to Veeam Backup for Microsoft 365 8.2.0.2202. I can’t find where the previous versions are posted.
+23Are your services running? Are the ports open on windows firewall? What logs do you get when it starts.
I would contact support about this and have them assist as there could be something as you have noted.
I edited my original post to clarify that I am running the Community Edition for a few mailboxes only.
Veeam technical support for the Community Edition not a priority.
Well I would still try or downgrade your OS.
Downgrading the O/S is a non starter. What I would do bnefore that would be to uninstall 8.3 and reinstall 8.2. But it appears that Veeam has hidden the previous version from download.
+21I would contact support about this and have them assist as there could be something as you have noted.
I edited my original post to clarify that I am running the Community Edition for a few mailboxes only.
Veeam technical support for the Community Edition not a priority.
Well I would still try or downgrade your OS.
Downgrading the O/S is a non starter. What I would do bnefore that would be to uninstall 8.3 and reinstall 8.2. But it appears that Veeam has hidden the previous version from download.
The previous version is there under other downloads section.
Are your services running? Are the ports open on windows firewall? What logs do you get when it starts.
I rechecked the services. Veeam Backup for Microsoft 365 Service had originally been registered as “Local System Account” and when that did not function, I had changed it to specific account with "Log on as a service" user permissions. That had failed also.
But reading your piece reminded me to set the radio button back to “Local System Account” where it started. And on a hunch, I tried starting the service again and it and now Veeam for O365 functions. I just never thought of flipping that switch twice!
This issue is closed.
+21Glad it was just a service that sorted it out.
Glad it was just a service that sorted it out.
I might have, or might not. I rebooted the server this morning after applying some MS updates. The server restarted, but Veeam Backup for Microsoft 365 Service did not.
Once again, I had to change “Local System Account” to "Log on as a service" user permissions and set the radio button back to “Local System Account.” I tried starting the service again and it and now Veeam for O365 functions.
That is very troubling behavior. Have you encountered anything similar?
+21Glad it was just a service that sorted it out.
I might have, or might not. I rebooted the server this morning after applying some MS updates. The server restarted, but Veeam Backup for Microsoft 365 Service did not.
Once again, I had to change “Local System Account” to "Log on as a service" user permissions and set the radio button back to “Local System Account.” I tried starting the service again and it and now Veeam for O365 functions.
That is very troubling behavior. Have you encountered anything similar?
Have not seen that one yet. We are not on 8.3 just yet as there are other issues with it, we found during testing, so have an open ticket with Veeam to figure things out. I do think this might be one of the issues we have seen, come to think of it.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.