Error applying Update 1 for v9

[Aremac]

When applying the patch to v9 I get a return dialog of "Failed to get path to the update package"

Has anyone else seen this? System was rebooted, services stopped, AV stopped. Per support I checked registry to see if non-existing drives were referenced. The veeamcatalog is on the z: drive and while monitoring the location the files are supposed to be placed nothing is ever copied there. (veeam_backup_9.0.0.1491.update1_setup.exe is supposed to be going to z:\veeamcatalog\backup\updates\)

I have opened a support ticket Case# 01745681

Just wanted to see if anyone else has seen this.

Thanks

[foggy]

Sam, try to re-download the package, chances are it was corrupt. This message is also displayed in case the signature check fails.

[Badi55]

Any News on this? Have the exact same issue...

[foggy]

Sam's case was escalated and is still under investigation. I recommend you opening your own case to help support in verifying the issue and be notified about its possible resolution.

[Badi55]

Ok, I have opend a case and one of the sugesstions worked:
I removed the machine temporary from the Domain (and our very restrictive GPOs) and the Installation of the update succeeded.
Thanks for the help!

[foggy]

Thanks for the update! Much appreciated.

[Boris]

Is there another solution already? We have the same Problem. Downloaded the Update twice but always same errror "Failed to get full path to the update package".
Thanks

[foggy]

Boris, if the suggestion mentioned above doesn't work for you, please open a case with technical support to try other things they could recommend.

[pbarrette]

I have the exact same problem.
Case 01772983.

I put our system in a domain OU that contains no GPOs, rebooted and the problem persisted.
I was able to install the update for Veeam One.
I was also able to install the Veeam B&R update on our disaster recovery system using the same EXE, but not on our production box. So that rules out a corrupted download.

[veremin]

The installation logs should shed some light on the experienced behaviour. So, keep working with our support engineer. Thanks.

[Tron04]

Hello,
in my case it turned out to be the fact that the server cannot directly reach the internet to update any missing root certificates. I checked the "Digital Signatures" Tab on the update exe and installed manually all missing root certificates in the veeam servers local certificate store (trusted root). Then the update went through without any problems.

I think Veeam should not count on to the fact that veeam backup servers have direct internet connectivity to update any certificates. Instead the installer should check for missing/necessary certs and install them itself on the installation machine. A out-of-the-box windows server 2012 R2 installation only has a bare minimum of root certificates installed and the ones necessary for this particular update are not part of it...

[pbarrette]

Hi v.Eremin,

I worked with the support engineer and was able to determine that it was a Trusted Root Certificates issue.
The installer is signed with multiple different certificates, which we normally do not have installed on our servers due to tight control over our root certificates.

The certificates we needed to install were:
https://secure.globalsign.net/cacert/Root-R1.crt - GlobalSign Root R1
https://www.digicert.com/CACerts/DigiCe ... RootCA.crt - DigiCert High Assurance EV Root CA
https://www.digicert.com/CACerts/DigiCe ... RootCA.crt - DigiCert Assured ID Root CA

Hopefully this will help someone else out.

[veremin]

It's expected behaviour indeed. When you disable a root certificate auto-update, you'll have to download and install them manually in order to work with files signed with modern digital signatures.

Thanks.

[Tron04]

Hello, in our case it is not expected behaviour, because we did not manually disable root cert updates. Our servers are behind a http/https Proxy with no possibility to directly contact the Internet.
We are using a Proxy.pac file to get Internet connectivity. However root certs are not automatically updated in this scenario on our Windows Servers.

[veremin]

Got it. Even if the conditions are a bit different in your environments, they still lead to the very same result - absence of root certificates' autoupdate. Thus, updates/certificates have be downloaded and installed manually to make everything work.

Based of number appeals, we might think about creating a corresponding KB about that.

Thanks.

[aftbic]

I removed the machine temporary from the Domain and the Installation of the update succeeded. Out of domain only execute "VeeamBackup&Replication_9.0.0.1491_Update1.exe" and after with the machine in the domian execute VeeamBackup9 and finish the installation.

[tcarson]

Hi v.Eremin,

I worked with the support engineer and was able to determine that it was a Trusted Root Certificates issue.
The installer is signed with multiple different certificates, which we normally do not have installed on our servers due to tight control over our root certificates.

The certificates we needed to install were:
https://secure.globalsign.net/cacert/Root-R1.crt - GlobalSign Root R1
https://www.digicert.com/CACerts/DigiCe ... RootCA.crt - DigiCert High Assurance EV Root CA
https://www.digicert.com/CACerts/DigiCe ... RootCA.crt - DigiCert Assured ID Root CA

Hopefully this will help someone else out.

this should be a KB if it isn't already!

Thanks so much, this helped me resolve my issues with updating.

[justin23]

Yes I had the exact issue with the certificates as our environment is secure with no internet access. Add the certificates and the update installed. This definitely needs to be a KB article.

[caryabend]

My organization maintains a number of isolated systems where this applies.
One more vote for a KB. Perhaps even a more clear error message.

[MrMegaVadim]

Oh Yes SIR !
it works like a charm , Thank you pbarrette

1. downloadet THIs certificates
2. installed them to Computer root authorities
3. Got veem Update 1 installed !

VEEAM PLEASE:
my company servers too do NOT have access to internet and nevel will

[RWeiss]

Many thanks also from my side. Exactly the certificates we needed and the update is now installing.

[l.vinokur]

Thanks guys!
I had same issue applying Update 2 on top of Update1 installation in an isolated network. Server is Win2012 R2.
One certificate was missing from Trusted Root Certification Authorities: DigiCertHighAssuranceEVRootCA
Once I imported it, update process was able to launch.

Best,
Leonid