Is your console on a different system than the VBR server?

No, they are on the same machine.

Do you see the Veeam services in the Windows services snapin?

Services are running fine on the VBR server:

Whilst some other services are also running on the Hyper-V host:

I can’t see the Veeam distribution service on neither machines.

If you go to Backup Infrastructure in the Veeam Console, are there any servers with warnings/errors under the managed servers? If so, try to rescan those, and/or edit them and click through all the steps without changing anything.

I’ve tried to edit, then rescan servers, and encountered the warning: one or more veeam components is not up to date. Skipping host.

I’ve tried to edit, then rescan servers, and encountered the warning: one or more veeam components is not up to date. Skipping host.

 

 

This means the software on this server is not the current version.  Try updating it to see if that helps.

You can run the update on the server from within the console. Go to that out of date section of the tree.

Dear Chris,

when I try to do so, I have an error:

failed to upgrade host components error veeam distribution service is not installed

I’m stuck here...

Depending on what version you are using @Jrousset.VERA if you mount the Veeam ISO file on this server - go under Packages folder and run the VeeamDistributionSVC.msi -- this will install the service that Veeam is looking for and will hopefully let you upgrade at that point.

You also might have to remove any outdated components as well on the server if there is a much older version installed via Add/Remove Programs.

Thank you Chris, as the Veeamdistribution package was definitly the missing one. After installing this, I could upgrade my host, and launch the backup.

Have to put that one in my back pocket.  I probably would have uninstalled all the components and removed it from the configuration and then added it back in...assuming that it didn’t yell at me about jobs being dependent on that component.

I had a different experience after upgrading, where I could not run the console. During install it said it could start the Veeam backup service, and gave an option to continue without starting it (retrying did not help). Then when I started the Veeam Backup and Replication Console, it wouldnt start with an error of actively refused the connection. I looked in the error logs and saw an error code 110 in the Windows error logs saying the below two errors.

After googl'ing, I came across this post and looked at the Packages folder and the install failed to copy some packages to the folder. I then grabbed all the packes from the ISO and pasted them into the packages folder on the server, and the backup server was able to start the service. All good now. 

Hope this helps as well. And while running the VeeamDistributionsSVC.msi did not help me (the services were there), it did lead me in the right direction. Thanks Chris Childerhose.

Service cannot be started. System.Exception: Failed to open MSI database 'C:\Program Files\Veeam\Backup and Replication\Backup\Packages\VeeamTape.msi'. Error code: 110.
   at Veeam.Backup.ProxyProvider.CMsiDatabase.Open(String msiFilePath)
   at Veeam.Backup.ProxyProvider.CMsiHelper.GetVersion(String msiFilePath)
   at Veeam.Backup.Core.CHostComponentsHelper.ResolvePkgDistribInfos()
   at Veeam.Backup.Core.SDistribsInfo.ResolveImpl()
   at Veeam.Backup.Core.SDistribsInfo.get_Info()
   at Veeam.Backup.Core.CHostComponentsHelper.UpdateUpgradeStatus()
   at Veeam.Backup.ServiceLib.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)
   at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(Stringv] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state) 

And...

Service cannot be started. System.Exception: Failed to open MSI database 'C:\Program Files\Veeam\Backup and Replication\Backup\Packages\VeeamHvIntegration.msi'. Error code: 110.
   at Veeam.Backup.ProxyProvider.CMsiDatabase.Open(String msiFilePath)
   at Veeam.Backup.ProxyProvider.CMsiHelper.GetVersion(String msiFilePath)
   at Veeam.Backup.Core.CHostComponentsHelper.ResolvePkgDistribInfos()
   at Veeam.Backup.Core.SDistribsInfo.ResolveImpl()
   at Veeam.Backup.Core.SDistribsInfo.get_Info()
   at Veeam.Backup.Core.CHostComponentsHelper.UpdateUpgradeStatus()
   at Veeam.Backup.ServiceLib.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)
   at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(Stringr] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Glad I was of assistance

Hi

I fixed the issue by replacing files on this folders

C:\Program Files\Veeam\Backup and Replication\Backup\Packages

from packages folders on installation packages

i hope this help :)

This Worked for me! Thanks

Glad to hear of a resolution to this issue.  Great work.