Skip to main content
  • EN

I’ve spent two days on this and still cant get the console to upgrade / install.

 

I initially tried an inplace upgrade from 12.3.1 to 12.3.3, that failed to complete and when I next tried to run it I kept comming up against the installer codes issue as it thought it was already installed.

So I was in limbo, it wasnt installed, it wouldnt ‘uninstall’ either though add/remove programs and the installer wouldn’t offer the install option.

 

Using sysinternals process montitor , I setup two filters one to watch for veeam.setup.wizard.exe and a second one to watch for the path HKCU then ran setup again. the process monitor then shows the registry keys it finds for the products it things are installed. using regedit, I removed the Installer\UpgradeCodes , its a slow process as setup bombs out at the first failure so it need to be kept running to bring up the next code to remove.

Next I removed the veeam folders left behind in the program files & program data dirs etc.

Eventually I got back to the point where the ‘install’ button presented its self and I could again select the “Install Veeam Backup & Replication Console” again.

Now each time I try and install, it fails. from the VbrConsole.log :

***Veeam***  Get active database...
***Veeam***  Selecting upgrade codes from `Upgrade` table...
***Veeam***  Processing selected upgrade codes...
***Veeam***  Checking '{244542A1-3758-44A6-B443-3FC60BA12807}' upgrade code...
***Veeam***  Get 'Veeam.Backup.PowerShell.dll' component state...
***Veeam***  Exception occurred while while executing .Net assembly. Error code: 0x00000645.
CustomAction VmaPowerShellConfig_CollectInfo64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:13:31: VmaPowerShellConfig_CollectInfo64. Return value 3.
Action ended 11:13:31: INSTALL. Return value 3.

 

This seems to suggest powershell or someting related ? , another thread suggested it was permissions - all the permissions on 

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.conf

C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe.conf 

matach another machine we have that upgraded and runs fine. So its not permissions it seems.

 

.NET has been repaired and didnt find anything. windows is all upto date and the various DISM & SFC scans have completed without error.

 

Has anyone got any suggestions please? - reinstalling windows is not an option.

 

 

 

 

 

 

 

Hi ​@steveb  -

You've performed a lot of suggestions we would offer you. Unless someone else has another idea of what to do, I recommend getting ahold of Veeam Support. 

Try manually upgrading.NET and then see what happens.  I know you said it was repaired but Veeam needs a specific version.  If that fails then contact support as suggested.

.NET is currly 8.0.18 , which version does it need if “ Veeam needs a specific version”

.NET is currly 8.0.18 , which version does it need if “ Veeam needs a specific version”

That version should work.  Only suggestion is try downloading the install again from the web and install you might find a new dot release and then see.  Otherwise support.

I did, thats how it was checked to see if it needed repairing. 

 

Support case has been filed, waiting in line for contact.

Ah ok.  Hopefully support will get it sorted for you.  Let us know what happens.

Ah ok.  Hopefully support will get it sorted for you.  Let us know what happens.

 

We’ll do.

​@steveb -

I found another similar post on here suggesting folder permissions for powershell.exe.config should be Full Control for local Admin’s.

And here’s another post with currently no resolution:

You can try a few suggestions from the comments in those, if you haven’t already and see if any work. Let us know.

Thanks, I had already found that thread and much of that is the same as I’ve experianced.

None of those things specifically address the issue I’m having sadly.

I’m installing the console on a machine to talk to the server on another machine. I already have another machine that this upgrade worked fine on and went without a hitch. 

Ah, ok. 👍🏻

Well..hopefully Support has a suggestion Steve. Keep us posted.

Did you check the free space on C: ?

The console needs 5 GB free space to install, plus 4.5 GB for the .NET framework.

So you should have some more free space on C:

Looks like the installer is still trying to perform an upgrade and is checking the old UpgradeCode  (244542A1-3758-44A6-B443-3FC60BA12807).  Since this is only the console component, I suggest doing a clean uninstallation (using like CCleaner) and attempt to do fresh install again? 

 

 

Is Veeam running on PostgreSQL? I had a similar update issue when I ran the installer using a different user instead of the local Administrator. You can try running it as Administrator, or log into Windows with the Administrator account and run the update again.

Also, you can try repairing the .NET Framework using the Microsoft repair tool or by running sfc /scannow.

Comment


Terms & Conditions