TI9 weird behaviour...

error message running a task created with TI9....
see attached bitmap

 

Hello jbrevoord,

Thank you for choosing Acronis Disk Backup Software.

I'm really sorry for your inconvenience.

Could you pease do the following?

- Delete all the scheduled tasks;

- Delete all the files (scripts) from the \Documents and Settings\[User]\Application Data\Acronis\TrueImage\Scripts\ folder;

- Re-create scheduled tasks and see if the problem still persists.

If the problem still persists then please do the following:

- Download and run schedmgr.exe application;

- Issue the following commands:

service stop
service uninstall

- Close schedmgr;

- Replace schedhlp.exe and schedul2.exe files in the C:\Program Files\Common Files\Acronis\Schedule2 folder with the files from this ZIP archive.

- Run schedmgr application once again;

- Issue the following commands:

service install
service start

- Close schedmgr;

If the problem still persists then please do the following:

- Open the command prompt (Start -> Run -> cmd);

- Run the following command in the folder the schedmgr.exe file was saved to:

schedmgr get report > schedreport.txt

- Collect schedreport.txt;

- Run Acronis Schedule Manager program (schedmgr.exe) one more;

- Issue the following command:

set logflags support

- Schedule backup creation once again;

- Reproduce the scheduling problem;

- Collect the log file schedul2.log that is placed in the \Program Files\Common
Files\Acronis\Schedule2 folder;

Please also collect the following information:

- Describe actions taken before the problem appears step-by-step;

- Have you installed Acronis True Image 9.0 over the older version (e.g. 7.0 or 8.0) or was it a "clean" install?

- Create Acronis Report and Windows System Information as it is described in Acronis Help Post;

Send all the collected files and information to support@acronis.com along with the screen shot of the error message and the link to this thread. We will investigate the problem and try to provide you with the solution.

Thank you.
--
Alexey Popov

 

the problem occured after scheduling task for one-time run,
it looks like it has dissapeared with build 2259
i will test this again,
if it reappears i will take the actions outlined in your mail