Veeam Backup Service does not (re-)start? -> Failed to create desktop VeeamBackupServiceDesktop (ERROR_ACCESS_DENIED)

[DaStivi]

hi,
i just had some strange issue... after restarting the veeam services (get-service veeam* | stop-service and get-service veeam* | start-service) the "Veeam Backup Service" (VeeamBackupSvc) doesn't start anymore!

Eventlog showed me following error:
The service cannot be started. System.Exception: Failed to create desktop VeeamBackupServiceDesktop (ERROR_ACCESS_DENIED)
bei Veeam.Backup.Common.WinAPIWrappers.CWinDesktop.Create(String name, Int32 heapSizeKb)
bei Veeam.Backup.ServiceLib.CVbEnvironment.InitDesktop()
bei Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)
bei System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

after a quick google search i found nothing that really looked promising... and i was right before retarting the server (that would also have fixed it)
so what happend is, that i still had the Veem Console open, that tried to reconnect to the Server... i'm pretty sure i had done this in the past, and after the Service is restarted the console would reconnect...

i just canceld the reconnect window and closed the console and voila right after that the service just started fine! so for some reason the server service didn't start because the console was open? why? one thing i suspect, i've MFA enabled on this server, so maybe this sent something upon reconnect, directly when the service is starting that it just crashes it again?

[Gostev]

Hi, kindly do not bring environment-specific issues here and always work with our Customer Support directly as the first step. Many thanks!

[DaStivi]

Case #07638750

[david23267]

I can see both sides of this, but since I'm staring at this error in my environment, I sure wish the answer could have been posted, instead of him being reprimanded.

[DaStivi]

i've got some information from Support, that it might be also related to "heapSize" issues... it is even stated in the eventlog error...

so check this KB Article:
https://www.veeam.com/kb1909

it might have been just coincidence that after closing the vbr console the service started again...