The Last/Next 'run time' is incorrect (outdated) when viewing the status of client machines using Backup Exec System Recovery Management Solution (BESR-MS).

Article:TECH140310  |  Created: 2010-09-20  |  Updated: 2011-09-20  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


When viewing the backup status via the 'Manage Tasks' section of Backup Exec System Recovery Management Solution (BESR-MS), some client machines will intermittently show an incorrect (outdated) status.

Backups are running successfully and recovery points are created at the backup destination as per the policy schedule but some client machines do not report their status back to the BESR-MS server. In some cases, the last/next run time will show 14 days ago even when the most recent backup was the previous day.


It is currently believed that this issue is caused by an intermittent crash in VProSvc.exe on the client machines.

You may see entries in the application event log on the client machine(s) similar to:

Faulting application VProSvc.exe, version, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x0001bd02.


A temporary workaround is to schedule a regular restart of the 'Symantec Management Agent' service on the client machines that are experiencing this problem. NOTE: older versions of the agent will list the service as 'Altiris Agent'.


This issue is resolved in SP1 (10.0.1) for Symantec System Recovery (SSR) or in SP3 (9.0.3) for Backup Exec System Recovery 2010 Management Solution, both of which are available via SIM, LiveUpdate and here:

Supplemental Materials


SSR-MS/BESR-MS: Last/Next run time incorrect (outdated) in 'Manage Tasks' section of console.

Article URL

Terms of use for this information are found in Legal Notices