Silent update asks to CLICK Ignore Cancel or Retry

[Elemer.gazda]

Hi,

I have tried to install the Veeam backup and replication 9.5 Update 3 with

Code: Select all

VEEAM-U3.exe /silent /noreboot /log C:\Logs\veeam.log VBR_AUTO_UPGRADE=1

And this is shown in the Logs file:

12:09:24.3656 Add property '/packedpath'.
12:09:24.3656 Silent mode detected.
12:09:24.3656 NoReboot mode detected.
12:09:24.3656 Log redirection detected:
'C:\Logs\VeeamUpdate-20180622_1207.log'.
12:09:24.3656 Add property 'VBR_AUTO_UPGRADE'.
12:09:24.3656 Add property '/sync'.
12:09:25.0253 Checking wizard mutex...
12:09:25.0283 Mutex doesn't exist.
12:09:25.0824 Running HotFix in silent mode..
*
*
*
*
12:16:48.2348 *** WARNING *** The following files are locked by
PowerShell_ISE.exe process:
veComLic.dll.
Click Abort to exit the setup, Retry to re-check file locks, or Ignore to
continue (server reboot will be required).
12:16:48.2348 *** WARNING *** Answer: Abort.

An unattended install should be unattended I thought.

VEEAM Ticket ID is 03067305

Thank you,
Ele

[Dima P.]

Hello Ele,

Checking with RnD. Thanks for sharing.

[Dima P.]

Hi Ele,

Can you confirm that you actually saw the dialog and not referring to the pure log output? Log represents the dialog but it was automatically closed by setup itself in abort state (after several milliseconds of waiting)? Thank you in advance.

12:16:48.2348 Failed to access process 'Idle' (id: 0) modules.
12:16:48.2348 *** WARNING *** Answer: Abort.

[Elemer.gazda]

Hi Dima,

No, there was no dialog.
Just the log saying to click here or there.

Regards,
Ele

[Dima P.]

So you are good to go with this silecnt install senario (as it's only a log note and no user interaction was required). Thanks!

[Elemer.gazda]

Sorry, but you are wrong:

12:16:48.2348 *** WARNING *** Answer: Abort.

The silent installer expects an input from the user.
But because it is silent no user can input anything.
And it thinks the Abort was clicked.
I would rather like it would think the Ignore was clicked, even though this would than require a server reboot.

[Elemer.gazda]

I would mention that this silent installer is triggered by a Powershell script
I was using PowerShell_ISE.exe and that is the program which has the lock on this .dll file.

[Elemer.gazda]

Just as an update.
I managed to get this issue fixed:

basically I have created a script which disables all running jobs in VEEAM and then triggers the update process,
And when it is finished it re-enables the disabled jobs (this last part is still work in progress).

My script has:

Code: Select all

Add-PSSnapin VeeamPsSnapin
Connect-VBRServer -Server localhost

-- Checking and disabling running jobs --

Disconnect-VbrServer
Remove-PsSnapin VeeamPsSnapin

running the installer

I believe the file in question is related to the VEEAM powershell SnapIn as after I included remove-PSSnapin it stopped throwing me this same error.

As an idea:
It would be nice for the VEEAM installer to disable/stop running jobs and after install finishes re-enable running jobs.
This would provide a much more seamless experience especially for the silent option.

[Dima P.]

Hello Elemer.

Your request makes total sense, thanks a lot. I'll pass it to the setup team. Cheers!

[ITP-Stan]

I always stop all veeam services and kill remaining processes before running setup.

[Elemer.gazda]

Hi ITP-Stan ,

In our case we would have to disable the VEEAM services as well, not just stop it, because our monitoring software would restart the veeam services if it picks up that the service is stopped.
But maybe that's a solution for the next version of my update script.