Skip to main content

Hello,

 

Just getting into Veeam. Trying to install VeeamOne agent on my Veeam B&R box from my standalone VeeamOne server. However, it keeps failing out. I’ve tried unloading any anti-virus, disabling firewall. I’m running it using administrator credentials. It is not domain joined so it does not have any odd security policies. I’m using ComputerName\Administrator for the installation account. I looked at errors 1639 and 1708 but it provided little help. has anyone seen this or know a workaround?


=== Verbose logging started: 3/24/2023 15:57:11 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\OneAgent\Veeam.One.Agent.Deployment.Service.exe ===
MSI (c) (20:A0) 215:57:11:775]: Resetting cached policy values
MSI (c) (20:A0) 215:57:11:775]: Machine policy value 'Debug' is 0
MSI (c) (20:A0) 215:57:11:775]: ******* RunEngine:
******* Product: C:\Windows\OneAgent\OneAgent.x64.msi
******* Action:
******* CommandLine: **********
MSI (c) (20:A0) 215:57:11:775]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (20:A0) 215:57:11:775]: Grabbed execution mutex.
MSI (c) (20:A0) 215:57:11:775]: Cloaking enabled.
MSI (c) (20:A0) 215:57:11:775]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (20:A0) 215:57:11:775]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:D8) 115:57:11:791]: Running installation inside multi-package transaction C:\Windows\OneAgent\OneAgent.x64.msi
MSI (s) (18:D8) 115:57:11:791]: Grabbed execution mutex.
MSI (s) (18:44) 115:57:11:791]: Resetting cached policy values
MSI (s) (18:44) 115:57:11:791]: Machine policy value 'Debug' is 0
MSI (s) (18:44) 115:57:11:791]: ******* RunEngine:
******* Product: C:\Windows\OneAgent\OneAgent.x64.msi
******* Action:
******* CommandLine: **********
MSI (s) (18:44) 115:57:11:791]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (18:44) 115:57:11:791]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (18:44) 115:57:11:791]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (18:44) 115:57:11:791]: File will have security applied from OpCode.
MSI (s) (18:44) 115:57:11:791]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Windows\OneAgent\OneAgent.x64.msi' against software restriction policy
MSI (s) (18:44) 115:57:11:806]: SOFTWARE RESTRICTION POLICY: C:\Windows\OneAgent\OneAgent.x64.msi has a digital signature
MSI (s) (18:44) 115:57:11:806]: SOFTWARE RESTRICTION POLICY: C:\Windows\OneAgent\OneAgent.x64.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (18:44) 115:57:11:806]: MSCOREE not loaded loading copy from system32
MSI (s) (18:44) 115:57:11:806]: End dialog not enabled
MSI (s) (18:44) 115:57:11:806]: Original package ==> C:\Windows\OneAgent\OneAgent.x64.msi
MSI (s) (18:44) 115:57:11:806]: Package we're running from ==> C:\Windows\Installer\4d0d09.msi
MSI (s) (18:44) 115:57:11:806]: APPCOMPAT: Compatibility mode property overrides found.
MSI (s) (18:44) 115:57:11:806]: APPCOMPAT: looking for appcompat database entry with ProductCode '{BADC833F-04B8-47B5-AC53-265729D3690C}'.
MSI (s) (18:44) 115:57:11:806]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'TransformsSecure' is 0
MSI (s) (18:44) 115:57:11:806]: User policy value 'TransformsAtSource' is 0
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'DisablePatch' is 0
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (18:44) 115:57:11:806]: APPCOMPAT: looking for appcompat database entry with ProductCode '{BADC833F-04B8-47B5-AC53-265729D3690C}'.
MSI (s) (18:44) 115:57:11:806]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (18:44) 115:57:11:806]: Transforms are not secure.
MSI (s) (18:44) 115:57:11:806]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Windows\OneAgent\Install.log.txt'.
MSI (s) (18:44) 115:57:11:806]: Command Line: VO_AGENT_SERVICE_ACCOUNT_NAME=ComputerName\Administrator VO_AGENT_SERVICE_ACCOUNT_PASSWORD=**********
MSI (s) (18:44) 115:57:11:806]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{818C0C0F-4BA2-45C9-85A4-2FD55AC8FE9A}'.
MSI (s) (18:44) 115:57:11:806]: Product Code passed to Engine.Initialize: ''
MSI (s) (18:44) 115:57:11:806]: Product Code from property table before transforms: '{BADC833F-04B8-47B5-AC53-265729D3690C}'
MSI (s) (18:44) 115:57:11:806]: Product Code from property table after transforms: '{BADC833F-04B8-47B5-AC53-265729D3690C}'
MSI (s) (18:44) 115:57:11:806]: Product not registered: beginning first-time install
MSI (s) (18:44) 115:57:11:806]: Product {BADC833F-04B8-47B5-AC53-265729D3690C} is not managed.
MSI (s) (18:44) 115:57:11:806]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (18:44) 115:57:11:806]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (18:44) 115:57:11:806]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (18:44) 115:57:11:806]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (18:44) 115:57:11:806]: Adding new sources is allowed.
MSI (s) (18:44) 115:57:11:806]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (18:44) 115:57:11:806]: Package name extracted from package path: 'OneAgent.x64.msi'
MSI (s) (18:44) 115:57:11:806]: Package to be registered: 'OneAgent.x64.msi'
MSI (s) (18:44) 115:57:11:806]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'DisableMsi' is 0
MSI (s) (18:44) 115:57:11:806]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (18:44) 115:57:11:806]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (18:44) 115:57:11:806]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (18:44) 115:57:11:806]: Running product '{BADC833F-04B8-47B5-AC53-265729D3690C}' with elevated privileges: Product is assigned.
MSI (s) (18:44) 115:57:11:806]: PROPERTY CHANGE: Adding VO_AGENT_SERVICE_ACCOUNT_NAME property. Its value is 'ComputerName\Administrator'.
MSI (s) (18:44) 115:57:11:806]: PROPERTY CHANGE: Adding VO_AGENT_SERVICE_ACCOUNT_PASSWORD property. Its value is '**********'.
MSI (s) (18:44) 115:57:11:806]: Note: 1: 1708
MSI (s) (18:44) 115:57:11:806]: Product: Veeam ONE Agent -- Installation failed.

MSI (s) (18:44) 115:57:11:806]: Windows Installer installed the product. Product Name: Veeam ONE Agent. Product Version: 12.0.1.2591. Product Language: 1033. Manufacturer: Veeam Software Group GmbH. Installation success or error status: 1639.

MSI (s) (18:44) 115:57:11:806]: MainEngineThread is returning 1639
Info 1639. Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
LIKE
MSI (s) (18:D8) 115:57:11:806]: User policy value 'DisableRollback' is 0
MSI (s) (18:D8) 115:57:11:806]: Machine policy value 'DisableRollback' is 0
MSI (s) (18:D8) 115:57:11:806]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:D8) 115:57:11:806]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (18:D8) 115:57:11:806]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (18:D8) 115:57:11:806]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (20:A0) 215:57:11:806]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (20:A0) 215:57:11:806]: MainEngineThread is returning 1639
=== Verbose logging stopped: 3/24/2023 15:57:11 ===

 

Has you Veeam server in the past been added to a different Veeam ONE instance? And is the server domain joined?

 


The VeeamOne Server is new, the entire server itself is less than a week old. The Veeam V&R is also brand new, it has not been associated with another VeeamOne server or ever domain joined.


Maybe you can try to manually install the msi package on your VBR server. The command line is described in this article: https://www.veeam.com/kb3130

By the way did you mark my post as the best answer by accident?


I will give it a try, and not intentionally — no offense. I appreciate the help so far.


No problem at all 😉

@Madi.Cristil Can you reset the best answer for this topic?


Comment