#1 Global Leader in Data Protection & Ransomware Recovery

Task fails with error: Application is Shutting Down

KB ID: 2121
Product: Veeam Backup & Replication
Veeam Agent for Microsoft Windows
Published: 2016-04-06
Last Modified: 2022-04-27
Languages: 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

Jobs of any type fail with the error, “Application is shutting down.” For example:
Application is shutting down. Failed to download disk. Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}
BackupSynthesizedStorageToTape failed Application is shutting down. Unable to receive file. Application is shutting down.

In Event Viewer on the Veeam Backup & Replication server, a time change of several minutes is recorded in the System log a few minutes before the error occurs:

SEVERITY:Informational
SOURCE:Microsoft-Windows-Kernel-General
 EVENT ID:1
 DESCRIPTION:System time changed from 2016-03-31T12:06:22.375327200Z to 2016-03-31T12:12:23.623952000Z.

Cause

The Veeam Backup Service uses a system of timed leases to monitor the many processes it manages. Usually, this error involves a five minute lease for the VeeamAgent processes (Data Movers). When the Veeam Backup Service is operating normally, this lease is continually renewed. If the lease expires, the associated process is shut down.
 
Typically the lease will expire either because the system time has changed by several minutes, or because a problem communicating with the Veeam Backup Configuration Database has prevented the Veeam Backup Service from renewing the lease.

Solution

On VMware virtual machines, the VMware Tools will periodically synchronize the system time with the ESXi host. If the time on the host differs from the NTP server used by the Guest OS, the system time will repeatedly shift between the two different times. The best solution is to synchronize the time between the ESXi host, the Veeam Backup & Replication server and/or the domain controllers with the same source. If this is not possible, you could disable VMware Tools time synchronization on the Veeam Backup & Replication server.

If time synchronization is not the problem, please create a 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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.