"Service Suddenly Stopped Working", nothing is fixing it...

[voyager529]

Hello, Veeam friends!

I've got a problem with VEB on my laptop: It refuses to work...

The service in services.msc will start, and then stop within 2-4 seconds of starting. This prevents my laptop from either backing up or restoring data.

Event log says this:

Code: Select all

Faulting application name: Veeam.EndPoint.Service.exe, version: 1.5.0.306, time stamp: 0x56e0f779
Faulting module name: KERNELBASE.dll, version: 10.0.14393.321, time stamp: 0x57f4c4f0
Exception code: 0xe0434352
Fault offset: 0x0000000000017788
Faulting process id: 0x1ec4
Faulting application start time: 0x01d2766168ecc12f
Faulting application path: C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Service.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 35bce2a1-d27e-47da-bd2f-9a04c1bd8a30
Faulting package full name: 
Faulting package-relative application ID: 

The RebuildDatabase registry fix didn't work.
Uninstall/reinstall - including all the SQL components and individual folders and registry entries where I could find them - didn't work.
removing the databases from c:\windows\system32\config\systemprofile didn't work.
I can't send in a ticket from the application because the main window closes within ten seconds of opening it.

I appreciate whatever help is available.


Joey

[Dima P.]

Hi Joey,

Please let me know your contact email address. I'll ask support guys to reach you.

[voyager529]

The e-mail address in my user profile is valid and accurate.

[Dima P.]

Thanks. Passed to support team.

[voyager529]

I'm sorry I've neglected to report back on this topic. Props to Konstantin over in the support department for figuring this out...

I'm one of those paranoid Windows 10 people who does everything practical to avoid the telemetry and updates (yeah, I know, less secure...spare me the lecture). In addition to disabling the update service, I'd disabled the BITS (Background Intelligent Transfer Service), which is a requirement for VEB to run properly. Re-enabling it resolved the issue and backups and restore operations have resumed properly.

Hope this helps someone!!

Joey

[Mike Resseler]

Thanks for the heads up and coming back with the solution Joey! I'll make sure to send the props to Konstantin and Dima!