Direkt zum Inhalt

Bug - SystemTimeToFileTime: > error=87

Thread needs solution

Up until 3 days ago, my machine ran 24/7 and acronis ran at 2am every night. For the last 3 nights I've turned the machine off; I have discovered that the backup does not run in the morning even though the option to run at startup if it missed the last scheduled run is turned on.

Trying to run manually fails, and the log contains the error in the title. That suggests to me that the software is making a windows API call with invalid parameters. If there's anything else in the log that points out a problem, I wouldn't have the knowledge to determine. I have run chkdsk /f but no change.

I've attached the log, which shows windows morning startup behaviour and manual attempt.

Any hint to get automated backups going again appreciated.

0 Users found this helpful

I'd try leaving the machine in standby instead of off and see if tht makes a diff. Ifg so, then possibly ati is trying to run before all the necessary system dlls have been loaded in the boot up. In which case iirc, you can set a delay for skipped tasks running at start up.

I have a single user license and do backups using LInux. But the time stamp is incorrect. How do I change this?

Bruce Roberts wrote:

I have a single user license and do backups using LInux. But the time stamp is incorrect. How do I change this?

In my time zone (EDT) I find that backups made with the bootable Rescue Media are time stamped one hour earlier than my local time. AFAIK, it's not possible to change that.

You can't change what's in the ati database. You can change the actual timed stamp on the file -- there's lots of free progs that can do this -- but that should be correct already as it's put on by the file system

Scott Hieber wrote:

You can't change what's in the ati database. You can change the actual timed stamp on the file -- there's lots of free progs that can do this -- but that should be correct already as it's put on by the file system

The @time@ option inserted by True Image into the filename is always an hour off for me. I'm not sure if that's what you meant, or if you meant Windows' Date Modified or Date Created metadata.

ati backups have been an hour off going many versions back. I believe there is no allowance for local Daylight Saving Time, which would more appropriately be called Daylight Shifting Time since nothing is saved but that's another issue ;)