Failed to process tag 'script' in script
Hi
I have a task which after running for months without issue started to fail.
I decided to recreate the task anew rather than clone it.
The new task has run succesfully a few times but has now started to fail.
I ran the log viewer and saw...
"Wed 27 Mar 19 13:35:41: +00:00 19644 W00010064: Failed to process tag 'script' in script '6286C14F-9A35-47CA-8AEC-1C99F74D307C' "
Any suggestions on what I can do to remedy this?
Thanks for your time.
BR


- Accedi per poter commentare

Hi Steve
If I understand what youre asking correctly, the log file name is the same script ref with the error.
C:\ProgramData\Acronis\TrueImageHome\Logs\ti_demon\ti_demon_6286C14F-9A35-47CA-8AEC-1C99F74D307C_7CFC12D0-C986-4093-8683-916E021FFA90_2019-03-27-14-02-17.log
Wed 27 Mar 19 14:02:17: +00:00 16984 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
Wed 27 Mar 19 14:02:17: +00:00 16984 I00640002: Operation AppData Only started by schedule.
Wed 27 Mar 19 14:02:24: +00:00 16984 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
Wed 27 Mar 19 14:02:24: +00:00 16984 I013C0000: Operation: Backup
Wed 27 Mar 19 14:02:24: +00:00 16984 E000B0069: Error 0xb0069
| trace level: error
| line: 0x25c43ad22fb160a0
| file: c:\bs_hudson\workspace\723\products\imager\archive\impl\operations\script.cpp:1909
| function: TrueImage::Archive::FillBatch
| line: 0x25c43ad22fb160a0, c:\bs_hudson\workspace\723\products\imager\archive\impl\operations\script.cpp:1909, TrueImage::Archive::FillBatch
| $module: ti_demon_vs_15470
Wed 27 Mar 19 14:02:24: +00:00 16984 W00010064: Failed to process tag 'script' in script '6286C14F-9A35-47CA-8AEC-1C99F74D307C'.
Wed 27 Mar 19 14:02:24: +00:00 16984 I0064000B: Priority changed to High.
Wed 27 Mar 19 14:02:24: +00:00 16984 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_15470
Start: Wed 27 Mar 19 14:02:17
Stop: Wed 27 Mar 19 14:02:24
Total Time: 00:00:07
The same is task is failing repeatedly with a different error. e.g on another attempt a few minutes later the log file says the backup completed successfully but upon trying to validate it the error says "decompression failed".
Thanks.
B R
- Accedi per poter commentare

BR, can you try uncoupling any validation action from this backup task and see if this error is still being given (that is assuming you have selected to validate after the backup in the Advanced Options settings).
- Accedi per poter commentare

Hi Steve
I turned off the validation option. The task completed succesfully and I could view files in the recovery window. SO it was looking good. But I then ran the validation 15 mins after it completed and it failed with "Error occurred while searching in the file", a decompression error and incorrect data check.
Here's the log following the validation attempt...
Wed 27 Mar 19 22:13:51: +00:00 22032 I00640002: Operation Backup validation started manually.
Wed 27 Mar 19 22:13:58: +00:00 22032 I0064000B: Priority changed to Low.
Wed 27 Mar 19 22:13:59: +00:00 22032 I000B0402: Validate Backup Archive Location: T:\App Data T_full_b2_s1_v11.tib
Wed 27 Mar 19 22:14:48: +00:00 22032 E00040005: Error 0x40005: Error occurred while searching in the file.
| trace level: error
| line: 0xa92e3420176087dc
| file: c:\bs_hudson\workspace\723\archive\verify.cpp:488
| function: `anonymous-namespace'::ArchiveVerifyOperation::Execute
| line: 0xa92e3420176087dc, c:\bs_hudson\workspace\723\archive\verify.cpp:488, `anonymous-namespace'::ArchiveVerifyOperation::Execute
| $module: ti_demon_vs_15470
|
| error 0x170026: Decompression has failed.
| line: 0x675e03a7d2d4eb0e
| file: c:\bs_hudson\workspace\723\archive\decompress.cpp:52
| function: Archive::Decompressor::GetError
| line: 0x675e03a7d2d4eb0e, c:\bs_hudson\workspace\723\archive\decompress.cpp:52, Archive::Decompressor::GetError
| $module: ti_demon_vs_15470
|
| error 0x170018: incorrect data check
| line: 0x675e03a7d2d4eb0d
| file: c:\bs_hudson\workspace\723\archive\decompress.cpp:51
| function: Archive::Decompressor::GetError
| line: 0x675e03a7d2d4eb0d, c:\bs_hudson\workspace\723\archive\decompress.cpp:51, Archive::Decompressor::GetError
| code: 0xfffffffffffffffd
| $module: ti_demon_vs_15470
Wed 27 Mar 19 22:14:48: +00:00 22032 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_15470
Start: Wed 27 Mar 19 22:13:51
Stop: Wed 27 Mar 19 22:14:48
Total Time: 00:00:57
Thanks for your time.
BR
- Accedi per poter commentare

BR, the obvious conclusion here is that there is a problem with the target drive where your backup file(s) are being stored.
Please try the same task to a different target drive to see if that gives any of the same issues and/or run CHKDSK /R against the target drive.
The only other possible factor here would be a memory module failing under stress.
- Accedi per poter commentare

Hi Steve
Just a quick update
chkdsk /r found no errors and HD Sentinel says the drive is 100% healthy.
I ran the windows mem diag which found no erros either.
My system runs fine overall so would have been surprised if there was a memory error. Using the target drive to save and open files has no issues either.
I'll create a new task and try a different destination and report back.
Thanks again.
B R
- Accedi per poter commentare

B R, are you overclocking this system as that has been known to contribute to some strange problems?
- Accedi per poter commentare

Hi Steve,
Thanks for asking. My system is plain vanilla i.e no overclocking.
Any attempt to use the ASUS AI auto overclocking features are short lived and quickly result in "overclock settings failed" at boot up so I stopped bothering with them. But my PC is fast enough without them anyway.
Cheers
B R
- Accedi per poter commentare

Because of the varying nature of the errors, it may be worth looking in the Event Viewer to see if there are any system and/or hardware errors reported which coincide with the time of the ATI failures. I can't say exactly which log to check, so I think you'd need to mosey about in the logs.
If the target drive is USB, have you tried using a different USB port or cable? Best if it's plugged directly into a port on the PC and not through an extender.
Have you checked the source disk as well as the target disk? The first error report occurred so quickly that I'm not so sure it even got around to writing to the target disk yet.
- Accedi per poter commentare

Hi Bruno
Thanks for the suggestion.
Rather a lot of things to trawl through but taking a quick look didnt reveal any events occuring that correlated to the time of the backup failures.
B R
.
- Accedi per poter commentare

Hi Steve
I'm pleased to say that when using a different destination the backup completed and vaildated succesfully.
The original detination drive seems to function fine for regular use but for some reason Acronis doesnt like it. From memory I think that drive is connected to a PCI-E SATA controller rather than a port on the system board (ASUS X99 Deluxe). Maybe that has something to do with it?
Cheers
B R
- Accedi per poter commentare

BR, thanks for the update and results of your testing. Would you be able to connect the problem drive via a USB dock or adapter to isolate the drive from the eSATA controller?
- Accedi per poter commentare

Some generic PCIe SATA cards can be unreliable; many use AsMedia chips. Ones with only two ports OK ones with 4 ports are unreliable.
Also, I have had reliability issues with on-board SATA controllers that share a port between internal and eSATA connection; with nothing attached to the eSATA port the system would decide that there was causing the drive attached to the mainboard port to stop working. This happens with the secondary controller (AsMedia) on my AsRock Z77 Extreme MB.
Ian
- Accedi per poter commentare

Steve/Ian
Thanks for your help and suggestions. In the next few weeks I'll try the drive on another port and see it how goes.
I now have green ticks on my all my current tasks which is a great relief.
However I seem to have a ghost task/script which keeps running and failing. It seems to be set to retry several times after a failure.
I dont see any failures in the list of my current taks.
Using the log viewer I see the same "Failed to process tag 'script' in script '6286C14F-9A35-47CA-8AEC-1C99F74D307C." on each fail.
How do I identify this ghost script that keeps running and failing and remove it?
Thanks.
B R
- Accedi per poter commentare

Board room, see if there is a file in C:\ProgramData\Acronis\TrueImageHome\Scripts that matches 6286C14F-9A35-47CA-8AEC-1C99F74D307C or not.
If not, you can use task scheduler to remove it from the database.
https://kb.acronis.com/SchedulerManager
Managing scheduled tasks
Acronis Scheduler Manager allows to manage scheduled tasks as well. See the examples below.
To get a list of scheduled tasks:
get list
To delete a single task:
task [task number]
task delete
For example:
task 1-12
task delete
- Accedi per poter commentare

Thanks very much Bobbo.
Yes it was there as task 1-133 and have since deleted it.
Ran get list again and its no longer there. Phew!
However I noticed that the corresponding tis file is still in the scripts folder. Can I now manually delete it using file manager?
Cheers
B R
- Accedi per poter commentare

Yeah, so long as it's not actually in the backup console still, should be fine. You may need to stop the acronis scheduler services in computer management if you get access denied.
- Accedi per poter commentare