Cant update to VBR8.0 update3

[hyvokar]

Hi!

I have a problem updating to update3.

"Error
Update cannot be installed, because some processes are active. Please finish all the restore processes, stop and disable all jobs, close the user interface and try again. If you still get this message, restart the server and wait for few minutes before trying again."

I have disabled all the jobs (none of them is running), stopped all the services, closed UI, restarted the server, stopped the services again, but still get this message.

Any idea what's blocking the update?

Code: Select all

PS C:\Windows\system32> Get-Service veeam* |Stop-Service
WARNING: Waiting for service 'Veeam Backup Service (Veeam Backup and Replication Service)' to stop...
PS C:\Windows\system32> Get-Service veeam*

Status   Name               DisplayName
------   ----               -----------
Stopped  Veeam Backup an... Veeam Backup Service
Stopped  Veeam Backup Ca... Veeam Backup Catalog Data Service
Stopped  VeeamCloudSvc      Veeam Cloud Connect Service
Stopped  VeeamDeployment... Veeam Installer Service
Stopped  VeeamNFSSvc        Veeam vPower NFS Service
Stopped  VeeamTapeSvc       Veeam Remote Tape Access Service
Stopped  VeeamTransportSvc  Veeam Data Mover Service


PS C:\Windows\system32> Get-Process vbr*
PS C:\Windows\system32> Get-Process veeam*

[hyvokar]

I have this problem on two servers now.. Trying to find similatiries.

[veremin]

Might be worth restarting the server again, and for some time before proceeding with the installation. Sometimes it helps.

Otherwise, if that doesn't help, please reach our support engineer to check what might be blocking the process.

Thanks.

[hyvokar]

Waited for good half of an hour and had several restarts, didnt help. However, when I stop the services manually from the from the services mmc (gui) and not from the powershell the update installs.
This is now confirmed for both servers (one running Server2012, other Server 2012 R2).

Any idea if this is a Windows or Veeam issue?

[veremin]

Have you tried to find any differences in what is reported in PS and what is in Windows Services? I mean could it happen that commands issued via PS didn't take any effect on those services? If this behaviour can be confirmed only for Veeam-specific services, then, it will look like our issue. Otherwise, more like general Windows one. Thanks.

[hyvokar]

After stopping the services from PS i confirmed that the services actually were stopped from PS and from Windows services. If i had to take a guess, backup and replication service stopped faster from PS than from gui.

[bulletlynn]

After stopping services manually I was able to run update 3 successfully.

Not sure exactly what Veeam does not like about the below powershell command.
Get-service -displayname veeam* | stop-service

[veremin]

Might be a temporary problem or something, as everything appears to be ok with the script. All VB&R specific services should have "Veeam" in their names and, thus, should be properly gotten and then stopped via the referenced script.

Thanks.

[timmi2704]

I can confirm that for me this is one of the most stubborn updates
Even after several reboots and service stops it didn't work.

I did the following the last times:
- get-service Veeam* | set-service -startuptype disabled
- Reboot
- Execute update
- get-service Veeam* | set-service -startuptype automatic (The delayed option was still set for some of the services)
- get-service Veeam* | start-service

Until now, that worked in all of the cases.

[veremin]

Did you also catch the same pattern as Nick did? I mean VB&R specific services stopped via PS don't allow you to proceed with update any further, while manual stop of the given services does help. Is this the case? Thanks.

[timmi2704]

Hmm. I never tried using the GUI to be honest. I always used PowerShell CMDlets.

[JohnnyW]

I've the same trouble installing Update 3. But used the service-GUI to stop the Veeam services. After checking there were no Veeam processes running anymore I started the update... and got the same message and couldn't install the update.
I didn't do a reboot at this time (never needed one before). I will do that after working-hours and see what happens.

[Gostev]

I have heard about this issue a few times with the previous updates, too. I hope we can nail this down to be able to prevent this issue with future updates once and for all, so if anyone cares to open a support case and have our engineers take a look at this in live - this will be most appreciated. I am beginning to suspect this is caused by some 3rd party software (like antivirus) locking some essential files, otherwise we would encounter this in our QA labs as well...

[loganbest]

Happened with me too. Reboot fixed it for me. I have no additional services or applications installed on mine except WindirStat. No Antivirus except Windows defender stuff that's built in.

The server is behind an ACL an only accessible from a specified internal subnet.

[tony.grilley]

In support (and in our lab), we have seen updates for Veeam being prevented by simply having a powershell window open.

[loganbest]

In support (and in our lab), we have seen updates for Veeam being prevented by simply having a powershell window open.

Also was not the case for me. Had nothing open except the explorer window where the exe was.

[veremin]

As to stopping VB&R services via PS, in Update 2 we added additional verification to our setup. It checks whether there is PowerShell.exe process running. In case of positive answer, wizard doesn't proceed any further until you stop the said process. The reason is that PowerShell.exe might execute some VB&R commandlets that in their turn can affect update operation.

Therefore, as Tony's pointed out, PowerShell.exe must be stopped in order for the upgrade process to proceed.

Thanks.

[ian0x0r]

I've had this before, on various updates even with services stopped, if backup copy jobs were not disabled. Might be worth a look.

[ITP-Stan]

I usually stop any jobs, then stop the services, then kill all remaining Veeam processes.

[cmaier]

Maybe you could check this:
1. Stop all Veeam services
2: Run the patch
3: Once patch is running go to %temp% and get the IXP000.TMP directory, and copy it to the desktop.
4: Close the patch
5: Open BackupSettings.xml from the IXP000.TMP directory in notepad.
6: Look at the processes under <processestocheck> to </processestocheck> and check if one of them is running on your machine

I had this issue last time and the problem was a running powershell.exe

[Fiskepudding]

I got this message as well during the update yesterday.
No jobs were running. However the console was open, so I closed it and tried again, then i it worked.
Just though the message was a bit missleading, and thought nothing more about it.

Another observation, probably nothing, but there were windows updates pending.

[Delo123]

Maybe it's time to enable PowerShell Hardcore mode
http://deploymentresearch.com/Research/ ... dcore-Mode

Ps. of course please DON'T

[michaelryancook]

I was getting this error and when I looked in task manager Veeam.backup.shell was still active even though all jobs and services had been stopped. After killing that process I was able to install.

[sullivas]

In support (and in our lab), we have seen updates for Veeam being prevented by simply having a powershell window open.

This was the fix for me! Thanks Tony!