"no such script ......."
This one has me puzzled!
I recently replaced my old antique laptop with a new Acer, and installed ATI2010. I have two valid registered copies of 2010 – for laptop and desktop. I had recently downloaded the latest build (7160) so that is the build I installed on the new laptop. Any task I create works perfectly when run within ATI, however using win7 task scheduler to run the same task always stop immediately, and the first entry in the log says “No such script: C:\Program Data\Acronis\TrueImageHome\scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis!
I use win7 task scheduler on the desktop to run ATI2010, in order to have it wake and run other functions in addition to imaging the system disk. That has worked great on the desktop machine for some time, but the desktop is still using build 7046, and I guess I want to get this issue resolved before putting 7160 on the desktop.
I have deleted and recreated tasks and script files, and reinstalled ATI2010 with no change, so I am eager to hear if anyone can explain this!
Thanks --- Bob Vaughan
Grover,
Many thanks for the reply. Two thoughts:
1) That should also fail when running within ATI.
2) The second of your links above seems to confirm my path to scripts
------------------
Windows 7 x64:
------------------
ATIH 2011, ATIH 2010, ATIH 2009, ATIH 11.0:
Program: "C:\Program Files (x86)\Acronis\TrueImageHome\TrueImage.exe"
Service: "C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeService.exe"
Scripts: "C:\ProgramData\Acronis\TrueImageHome\Scripts"
Am I totally misreading something here??
Thanks for any clairification. ..Bob
Can you physically manually locate the target script?
-
Greetings, Pat. Thanks for your help.
Yes, it is located here:
C:\Program Data\Acronis\TrueImageHome\scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis!
That is where Acronis puts it when I run a task manually. The same location as on the desktop machine, which has worked well running via windows scheduler since first release of ATI2010 (5055 I think??) That desktop still has bld7046, where as the failing laptop has 7160. I am concerned about putting 7160 on the working desktop due to this, and I haven't tested by putting the back level on the laptop. I posted here because I felt this was probably not a unique first time occurence of this, although I found only one other thread in the forum, and it had no reply.
Thanks for any help...... Bob
I am not a deep technical guy, but I would guess this is a Windows user rights problem. It is possible that ATI is not running with the right privileges when invoked through the Windows task scheduler in the new build. You might want to experiment with the user that owns the task in Windows task scheduler...
Another possibility is that the user that is running the task in Windows task scheduler doesn't have read/write access to the scrips folder.
So if I were you, I would tweak the user/security settings of the task and of that folder. Just note down the changes you make so that you can undo them if they don't work and/or backup your system.
If you were using either 2011 or 2012, the TI supplied content for Windows shortcut or Windows task would be totally different like this.
"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:357D2638-713D-4C60-ADCA-64F6AFE4D348
-------------------------------------
However, f I am understanding correctly, your computer is the Windows 7 64bit and using 2010-7046, the 2010 version could look like this
"C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeService.exe" /script:"C:\ProgramData\Acronis\TrueImageHome\Scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
Proof these paths as correct by actual tracking. or use the search function for
TrueImageHomeService.exe
and a new search for
357D2638-713D-4C60-ADCA-64F6AFE4D348
You might try copying and pasting this into a new Windows Task or could work in a desktop shortcut id the script id is correct. Be sure and include all quotation marks. I would get it working as a shortcut first before copying into Windows Scheduled task.
I used cut & Paste from your posting to copy the script id number so my number is whatever you included in your posting.
Grover, Thanks again for the info.
However, the command line you described for 2010-7046 is identical to what I have in windows task that I am trying to run, and is the same as in the windows task on the desktop that is working correctly. As indicated in earlier posts, the locations of the executable file and the script file are where they should be.
The only difference I can lean on is the working desktop machine still has 2010-7046 installed, and the failing laptop has 2010-7160 installed. I suppose my next test should be to down level the laptop to 7046, and see if that works. It will be a couple days before I will have a chance to do that. I can still do image backups of the laptop disk by running the task from the ATI interface -- it only fails when run from windows task scheduler.
Meanwhile, I am open to any other thoughts!!
Thanks to all.....Bob
If I understand correctly, the shortcut works but the Windows task does not. One thing I would try would be to copy the contents of the shortcut into the Windows task. Use the clipboard so no typing is needed.
I would not remove 7160. Let's troubleshoot this until we find the cause. Be sure the two complete set of quotes is used as shown in my example.
Another option would be to put the contents of the shortcut into a cmd (batch) file and have the Windows startup task run the cmd file.
It looks like 7160 has some changes. Try this posting on a desktop shortcut and then a Windows task.
"C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:"C:\ProgramData\Acronis\TrueImageHome\Scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
I installed 7160 on an XP and got both the shortcut and Win Scheduler to run a cmd file. I translated this below for 64Win7.
Try copying and pasting the below into notepad and then save the file onto your desktop as Shortcut-test.cmd
"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /Script:"C:\Users\All Users\Acronis\TrueImageHome\Scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
If you can run the file from the desktop, you should be able to paste the shortcut-test.cmd into Win scheduler but with a full path to the file.
I believe one thing still holds true of working with 2010 shortcuts and scheduler and that is the very first backup must be run from within the program. After the first run, then the shortcut or scheduler should work.
TrueImage has a history of not being able to handle command lines which is why a batch or cmd file works better than having TI messing with the command line.
I hope this will work for you. Keep me updated.
===============================
Edit:
Also, the below seemed to work even better. Wrked as shortcut and also the Win Scheduler ran the cmd file.
"C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeService.exe" /Script:"C:\Users\All Users\Acronis\TrueImageHome\Scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
Grover,
Thanks so much for all the time you've spent on this.
For what it's worth (maybe nothing) this is
just to compare the two computers using ATI-2010......
On the desktop with 2010-7046:
This only opens True Image GUI -- from bat file or windows scheduler.
"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:"C:\ProgramData\Acronis\TrueImageHome\Scripts\95F9A90F-A326-4841-8D09-10FA866C9FA1.tib.tis"
This runs the system backup task -- from desktop, bat file or windows scheduler.
"C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeService.exe" /script:"C:\ProgramData\Acronis\TrueImageHome\Scripts\95F9A90F-A326-4841-8D09-10FA866C9FA1.tib.tis"
On the laptop with 2010-7160:
This only opens the GUI, as on desktop
"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:"C:\Program Data\Acronis\TrueImageHome\scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
This STARTS backup, but stops, logs "no such script",
from desktop, bat file or windows scheduler.
"C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeService.exe" /script:"C:\Program Data\Acronis\TrueImageHome\scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
As I stated in a earlier post, this ATI task works fine when run from the GUI.
There is a difference in the path to the scripts between your notes and the scripts folder on my machines, but I think that is due to user acct defs.
I found in the forum a reference to article #1785 which mentions "no such script". I have not installed the file discussed in the article, due to some confusion on my part. There are some links in the article for registering and unregistering task. however, the links only cycle back to the same article! I am not familiar with "registering" task. Could this download file mentioned in this article relate to my problem, and if so, what is a registered task?? In my 7 or 8 years using acronis, thru 4 release levels, I haven't run into that!!
Again, thanks for your time on my behave. I'm still trying!!
Bob
Using Windows explorer, browse to your script file
"C:\Program Data\Acronis\TrueImageHome\scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
Once you get get there, hold down on the shift key and Right click on the file.
This should bring up the Right click context menu with an option"copy as path"--Select this option.
Now open notepad, and paste the clipboard into Notepad.
What path is shown? This is what should be used inside the path to the script file.
It may look something like this or if TI is not installed for all users, your path may differ. Replace the "all users" with your user name.
"C:\Users\All Users\Acronis\TrueImageHome\Scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
"C:\Users\Bob\Acronis\TrueImageHome\Scripts\357D2638-713D-4C60-ADCA-64F6AFE4D348.tib.tis"
Grover,
Thanks again ever so much for your time and attention to my situation here. Sorry for the delay responding, but I was away a couple days on a family matter.
Meanwhile, I have uninstalled and reinstalled 2010-7160 AGAIN, ran another image save using the ATI windows GUI, which of course created another script file. Here is the path to it:
"C:\ProgramData\Acronis\TrueImageHome\Scripts\FB97F76F-03C0-4A64-BF78-70659549E68B.tib.tis"
Following your instructions in post#13, the "copy as path..." produces the SAME path:
"C:\ProgramData\Acronis\TrueImageHome\Scripts\FB97F76F-03C0-4A64-BF78-70659549E68B.tib.tis"
Browsing the Users folder finds three items -- Default, Public, and Robert. There is no "all users" listed, and no acronis entry under any of the existing user folders. Were you expecting to find the script in BOTH the "ProgramData" location, as well as the "Users" path??
The above info is also true for my desktop machine, which runs image backups nicely from shortcuts and windows task scheduler. Both machines are Win7-64bit, The only difference I can identify is 2010-7160 on the laptop and 2010-7046 on the desktop.
In post#9 you said "I would not remove 7160. Let's troubleshoot this until we find the cause." I agree with that, but at some point I would think about installing 7046, which is working on the desktop, as a diagnostic step. I have not put 7160 on the desktop yet, until this issue is resolved, because the desktop is much more critical (thounds on photos and other data). The archived photos and data exist on multiple disks, but the current "working" photos and data are part of the acronis system disk images (two partitions).
I am certainly willing to act on any suggestions you or anyone else may have, and I don't mind having an “EMBARRASSING RED FACE” if it turns out I have overlooked something simple. Wont be the first time!!
Thanks again...Bob
Bob
Who knows. At this point the red face could end up being mine. I am at a disadvantage as I do not have a 2010 Windows installation--only a 2011 Windows installation. The procedure used by 2011 is not the same as used by 2010 for the creation and running of desktop shortcuts or batch files and may even have changed with the last update to 2010.
Thank you for your very detailed reply. I wasn't sure what I would find which is why I asked to to look further. Based on your response, I mounted a 2011 backup backup and located the scripts folder. Guess what? The scripts folder was found in two different locations. It was in the users folder as I described but it was also in the Program Data folder as you describe. One may be a space holder but nevertheless, I found two copies. Which explains why your path worked as well as my path worked. According to the Acronis posting I referenced, your path is the correct path.
I would appreciate your help in checking this if you would. Open the Control Panel/Folder Options/View/ and make sure the "Show hidden files and folders" is checked.
Maybe, the, real, issue is one of permissions. I want to investigate this a little further and time has run out for tonight. Let me think on this.
If I am understanding you correctly, the desktop shortcut runs without issue. Did you try to put the same command inside a batch(cmd) file and have the Windows Scheduler run the batch(cmd) file? Have you tried to "Run as administrator"?
Bob,
A shot in the dark.
Try using this as the script without the extension. This is the way it appears in 2012 and 2011. Just maybe the last build for 2010 has been changed to this method as well. Not sure if it will work or not.
"C:\ProgramData\Acronis\TrueImageHome\Scripts\FB97F76F-03C0-4A64-BF78-70659549E68B"
Grover,
Greetings, again. Better news this time (I think)!
First off, the suggestion you made in your last post (script file name without the .tib.tis extension) produced no clarification to the situation. Is there a reason TI2011 and TI2012 changed that format? I have not tried either version, and found no reasons to (new features, etc.). I don't use any of the "extra features" of ATI -- just full disk backups weekly, or prior to and following any system change such as software installs, etc. These tasks work very well for me, and I do believe in the theory "If it ain't broke, don't fix it"! I did need to move to 2010 because of windows 7. Also, I know that the new user interface has bothered many posters here. So, I stay with the familiar which works!
Back to the issue at hand, last night I once again uninstalled ATI, erased all scripts, short cuts, bat files, windows task scheduler entries, etc, rebooted, and reinstalled ATI2010-7160. Next, installed the file mentioned in article #1785.
Then ran ATI from windows to create a new script. After that, I created a desk top shortcut, and it worked! Then created a bat file, and IT worked! Then, the ultimate goal, created a windows task scheduler task, and IT worked!!
I have NO further explanation, but of course very interested in your assessment. Are you familiar with the issue discussed in article #1785, and is that likely to explain our recent activity? The article does mention 2010.
Meanwhile, I "hold my breath" while the next few backups run, and look for your comments on any of the above!! I can't thank you enough for all your time and interest on my behalf the last several days!
Bob Vaughan
Bob,
I am as perplexed over the cause as you are. As you have done the re-install before, I am not sure that 1785 had any bearing but since we really do not know the cause, who knows. Was this install any different--all users or single user, etc?
We main that is that you have it working and that is the bottom line.
Good luck and Merry Christmas.
Grover
Grover,
The only difference this time was the addition of 1785. That is why I ask you if you were familiar with the issue discussed in article #1785, in hopes you may know why that made a difference. Other than that, I have no clue!
After a few more backups on this laptop, I may go ahead with 7160 on my desktop, which currently still has 7046 installed. If it behaves as this laptop did, then I will run the 1785 file there also. I could get no clue from the article as to when that file is needed, except for the "no such script..." error, which is what we have been experenceing since installing 7160 on this laptop.
I guess we can close this chat, but still interested in any additional thoughts you may have.
Thanks again... Bob
The program downloaded via the 1785 KB article was a new scheduler. This is very much involved in all parts of the program so it is possible that was the fix but we are only guessing.