Backup failing - ACT.EXE Application Error
I've installed Acronis Backup & Recovery 10.0.11133 on a Windows 2003 Server SP2 (not a member of our Domain). It was running OK for a few days but now it's failing with this error message whenever a backup is started:
"act.exe - Application Error: The application failed to initialize properly (0xc0000142). Click on OK to terminate the application"
I'm not seeing any messages in the Event Log related to it.
I re-ran the install/repair hoping that would fix whatever is causing the failure but no such luck.
Any ideas?
I am getting the same error. In addition to remedies already enumerated, I have deleted all tasks and recreated them with no change in outcome.
Would like to request some support at this point.
I have same problem, with workstation version.
I reboot and backup work fine.
I created an reboot task before backup waiting a solution from acronis
Hello all,
Thank you for posting your question, I will be happy to help.
To resolve the issue please do the following:
- Go to Start -> Run, type REGEDT32.EXE to start Registry Editor.
- In Registry Editor, locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems
- In the right pane of Registry Editor, click Windows.
- On the Edit menu, click Modify.
- In the Edit String dialog box, locate the SharedSection parameter string in the Value data box, and then specify a larger value for the SharedSection parameter. If you increase the desktop heap by 256 KB or by 512 KB, the issue should be resolved.
- Click OK and reboot the computer.
Please see this Microsoft article for more information.
Please let us know the results, we should be sure that the program runs flawlessly. If the provided information is not clear or if you have any other question do not hesitate to post them and we will be glad to answer.
Thank you.
my shared section is 16384,8192,2048 and there is failure of act.exe every 2 to 3 days
Running latest build of acronis backup and recovery SBS edition
my shared section is 1280,3584,512 and there is a failure approximately every 5 days. Also, there have been up to 20ish, at least, scheduler tasks running by that time.
Running the latest build of acronis backup and recovery for windows server 2003.
Hello all,
Thank you very much for your messages.
If the solution offered in Oleg's post does not resolve the issue, please submit a support request with a brief description of the steps taken before this error appears, together with the AcronisInfo report, we will be able to resolve this for you.
Please let me know if you have any other questions.
Thank you.
Has this issue been resolved? I just started getting this error. We just bought and installed the software last month. It had been running fine till a few days ago and we started getting the Act.exe error.
Hello Stuart!
Welcome to our Forum, we're glad you joined us!
The main solution was specified by Oleg in this comment. If the problem persist the situationwill require investigation. Please follow suggestion mentioned in Anton's comment. Please also make sure that you are using the latest build - currently it's 11639. You can obtain it from your account. All you need is to have the product license registered here.
Should we have any additional solution available, we will immediately update the thread and let you know.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
Since this is the only topic I can find (using Google because searching "act.exe" in the forum gives me no results), and I am not getting decent support by email, I will post here.
This problem started once I began using the GFS backup plan, at least that is what it seems. I have already reinstalled the program once, and increased the non-interactive desktop heap once already and I'm going to try it again. Also because the backup periodically fails, the cleanup is not working correctly either. Has anyone else solved this problem?
Hello Eric,
Thank you for the update.
I answered your post about this issue here.
We are still working on the issue, I am sorry for any inconvenience.
Thank you.