Skip to main content

I keep getting the error when with the Windows Backup Agent:

“Veeam Endpoint Backup is already running for user *MyUsernameImCurrentlyLoggetInWith* “

When I try to edit the job currently running. 

But no other users are logged in or accessing the app. 

I have tried deleting the job. Now I can’t make a new one. Rebooting, of course. Shutting down the App and the Service. Uninstalling and reinstalling. Resetting the DB. Deleting the config folders in ProgramData and Windows Program Files. 

And I keep getting the error. Like something is still left on the machine, with a setting that is causing he fault. 

Ideas?? 

How do I completely remove everything from the Veeam Agent from the machine and start over?

 

 

Hi ​@koraltop,

Does any VBR (Veeam Backup & Replication) instance manage your workstation backup or do you use the standalone mode with the Windows Agent?

 

My suggestions would be a reboot and a re-installation. Deleting the software via control panel and manually deleting folders (maybe regkey structures as well) should do the job.

 

You should at this point consider involving Veeam Support (even possible if you run the free edition, based on best effort).

 

Best

Lukas


Hi Lukas. 
Yes, it is the stand-alone version. No Veeam-server is involved. 
I have tried uninstalling and deleting any and all Veeam files I could find, and reinstalling. 
The error persists. 
When I try to create a new job, I get the same error. 
I have tried creating a support ticket (yes, it is the free version). So far no response. 

Best regards,

Allan


Yep...agree with Lukas here. Uninistall via Programs and Features. After uninstall, go into Program Files, Program Files (x86), and ProgramData folders and if you see any leftover Veeam folders of any kind, manually delete. Go into services.msc and if you see any Veeam services still there, open a cmd prompt and type in: sc delete <service-name> for each Veeam service listed. Lastly, open up the registry editor (regedit) and go into HKey Local Machine (HKLM) > Software, and any Veeam keys...delete.

Then, try a reinstall of VAW and see if you still get the error. Also as Lukas stated..you can contact Veeam Support..even with Community/Free Edition, so recommend doing so.

Best.


Hi Coolsport00
I have tried e.g. uninstalling the agent, deleting the folder in windows data, and programfiles - and the reg-edit parts in software. When I reinstall the newest version, I can not start the program, as the error is back stating that there is already an instance running of the program. But there surely was not. 

THe only work-around I have found so far, is uninstalling, and reinstalling an older version (approx 2 years old). Then I can make a new job - but again: I can not edit it. 

I can then upgrade to the newest version, and the job is still working. But again: I can not edit it. 

It is really strange and frustrating. Something is still stuck (or just not working right on this version of windows (server 2022). 

 

 


I only can offer a couple other suggestions...if Support can’t help. But use them at your own risk:

  • Try some form of Windows program removal tool to hopefully uninstall what may have been missed. See this link for tools you can try: https://www.techradar.com/best/best-free-software-uninstallers ; then either reattempt VAW install or download/use VBR Community Edition
  • If you have a backup of your files, completely wipe your computer and just reinstall Windows; then download the latest VAW and attempt install. Or, instead of using VAW...and though it’s a little bit of overkill...as mentioned above, download Veeam Backup Community Edition. You have a little bit more flexibility using it with regards to amount of Jobs & workloads to backup, as well as functionality

Hopefully something there will work.

Best.


Hi Coolsport.
A complete windows reinstall is not an option currently, as the server runs very sensitive processes. 
And the community edition requires a second server to make sense - which we don’t have - it is the server we are trying to protect by making a daily image. 
Br.
Allan


Below steps remove Veeam Agent and all its settings
Uninstall Veeam Agent from Control Panel.
Delete C:\ProgramData\Veeam\ and C:\Program Files\Veeam\.
Remove HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\ from the registry.
Uninstall Microsoft SQL Server LocalDB (if present).
Delete leftover LocalDB files from C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint.
Reboot your system.
 


Hi SanjivK
I have deleted those things (the stand-alone agent does not have a SQL database). Still get same error and can not make new jobs or edit old ones. So something is still missing and messing with the program. 
Best regards, 
Allan


@koraltop - I would also take a look at the Windows Event Logs, specifically System and Application and see if there are any errors for service starting or Veeam related


Hi Dips. 
I have checked. There is nothing unusual. And the jobs run as normal - I just can’t edit them.
Best regards,

Allan


Hi Coolsport.
A complete windows reinstall is not an option currently, as the server runs very sensitive processes. 
And the community edition requires a second server to make sense - which we don’t have - it is the server we are trying to protect by making a daily image. 
Br.
Allan

@koraltop - yep...understood; was just offering only other possible suggestions. Again..at this point, Support is your only best bet. We’ve offered all suggestions we’re aware of to try. Sorry we couldn’t get you sorted.

Best.


Thanx. I have sent in two support-requests. So far no response. 

Allan


Are there any Veeam services that are still running? Then to disable them and to keep deleting Veeam components. Adding to VBR and uninstalling from there.

Veeam supports discourages to manually delete registry keys and running 3rd party uninstallers, since it has already been done, reinstalling the OS might be the only choice. 


Hi Kira

Im working on a Veeam reinstalled image of the original server. Not the live one. So no need to reinstall. And we can test whatever needed.

The problem of not being able to edit jobs persists with the service running as well as stopped. 

If I end the tray application, I also can not restart it except if I restart the entire server. 

Allan