Jump to content

Windows Event Log: Execution Terminated Unexpectedly - But it did not?

Recommended Posts

Windows 10 Pro x64 build 1803 with all current updates applied, Retrospect

Every time Retrospect starts based on a schedule task it produces the following Windows Event Log entries:

1/3/2019 2:00:04 AM Retrospect version - Automatically launched at 1/3/2019 2:00 AM

1/3/2019 2:00:16 AM Execution terminated unexpectedly, possibly due to a power failure or system crash.

1/3/2019 2:07:06 AM Script "JHG" completed successfully

1/3/2019 2:07:06 AM Normal backup using JHG at 1/3/2019 2:00 AM (Execution unit 1)
        1/3/2019 2:00:16 AM: Finished scanning backup set data files
    To Backup Set HD Set 012...
    ... [uninteresting message content deleted]
    1/3/2019 2:01:08 AM: Comparing Backups on STORAGE (D:)
    1/3/2019 2:01:27 AM: Execution completed successfully

I believe that Retrospect logs the error (2nd message) because it believes a previous invocation of the script failed, which did happen over a week ago. 

I think Retrospect is failing to clear some indicator of a previous failure when a backup is successful.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now