Version 6 install fail

[ricklawsha]

Just thought I would share a problem I had trying to upgrade from version 5 to version 6 of Veeam Backup for Microsoft Office 365.

Every time I would try the upgrade it would fail with a popup from Microsoft MSIEXEC explaining the command options. Nothing written in the Veeam logs that we could use to point us to the failing item.

The Windows installer was throwing an error code 1639. I tracked that down to a possible problem with having a space in the install folder name.

The original install folder was located at: C:\Source\Veeam\Veeam O365 6
I changed the folder and install source to: C:\Source\Veeam\Veeam_O365_6

Veeam successfully installed version 6 and after I upgraded the repositories, I have successful backups under Veeam O365 Version 6.

[HannesK]

Hello,
I installed VB365 successfully to "C:\Source\Veeam\Veeam O365 6" right now.

My guess is, the error was caused by something else. If needed, please check with Veeam support.

Best regards,
Hannes

[ProfileX]

I just ran into the same problem with 6.0.0.400, so frustrating to be dealing with issues like this in 2022, spaces have been supported since 1995 but amatuer developers/packagers forget to enclose them in double quotes. I extracted the ISO to a UNC, then tried installing from there but got the same symptom as ricklawsha, no error codes or clues in the log just the syntax window for msiexec.exe. I copied the install source to C: and tried again, but same thing. Renamed the folder to replace spaces with underscores, and it worked. I'm guessing their install wrapper is trying to include the .MSP files in the Patches subfolder in the msiexec command line but it's not enclosing them in double quotes.

[Polina]

Hi Marty,

That's a bit weird to be honest because I cannot recall such issues on previous builds.
Could you please open a support case and share the steps/actions you performed along with the logs?
Also, post your case ID here - this would help me to follow it up and push it to our dev team if needed.

Thanks!

[ricklawsha]

I ran in to this again with version 8. Just don't have a space in the name of the folder you run the setup from.

BAD INSTALL LOCATION: C:\SOURCE\VEEAM M365

GOOD INSTALL: C:\SOURCE\VEEAMM365

It will throw an error code 1639

[karsten123]

its an ISO. just mount it

[ricklawsha]

As a general practice I never do that. I have had problems in the past with reboots in the middle of an install and the just rebooted server can't find the previously mounted ISO.

[karsten123]

i dont get this. so your „problem“ is home made. mount the ISO, as we all do and problem solved.

[ricklawsha]

I would think the Veeam folks would want to know of a problem, even if it only appears in certain situations.