#1 Global Leader in Data Resilience

Veeam Agent for Microsoft Windows: Service suddenly stopped working.

KB ID: 1959
Product: Veeam Agent for Microsoft Windows | 2.0 | 2.1 | 2.2 | 3.0.2 | 4.0 | 5.0 | 6.0 | 6.1 | 6.2
Published: 2014-11-28
Last Modified: 2024-06-14
Languages: DE | JP | FR
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

While running Veeam Agent for Microsoft Windows (VAW), the Control Panel displays the error:

Services suddenly stopped working.
vaw error

Cause

The Veeam Agent for Microsoft Windows Control Panel has lost contact with the Veeam Agent for Microsoft Windows service on the local machine.

Possible causes include:

  • The Veeam Agent for Microsoft Windows service is not running.
  • The Veeam Agent for Microsoft Windows service is running but has locked up.
  • The Veeam Agent for Microsoft Windows service is missing.

Solution

Before you Begin

If possible, reboot the computer and check if the Veeam Agent for Microsoft Windows Control Panel still displays the error.

Troubleshooting Workflow

Open Services (services.msc), and check if the Veeam Agent for Microsoft Windows service exists.

  • If the Veeam Agent for Microsoft Windows service is not present, re-install Veeam Agent for Microsoft Windows and check again.
  • If the Veeam Agent for Microsoft Windows service is present, determine if it is running:
    • If the service is running, restart the service and check the Veeam Agent for Microsoft Windows Control Panel to see if it regains connection to the service.
    • If the service is stopped, start it.
    • If the service fails to start, review the properties of the Veeam Agent for Microsoft Windows service:
      • Set to Automatic start.
      • On the Log On tab, the Log on as should be set to Local System Account.
  • If the service is present, the settings match what was listed above, and the service still won't start, confirm antivirus exclusions have been configured as described in KB2034: Antivirus Exclusions for Veeam Agent for Microsoft Windows.
  • If the methods described in this article do not resolve the issue:
    1. Collect Logs's using the PowerShell script found here: KB2404: How to collect logs for Veeam Agent for Microsoft Windows
    2. Then attach the generated log package to a new Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.