| Help Center |
 |
|
| Q&A Directory | |
|
|
|
|
| |
|
|
|
"AutoDutyPRO for Windows 4.0 has stopped working", "application failed to initialize" |
|
|
On startup, AutoDutyPRO displays "Unable to create directory" |
|
|
When I start AutoDutyPRO, I am getting ACCESS DENIED errors |
|
|
What do the various 'machnm1.exe' errors mean? Can I stop them? |
|
|
Stream Write errors when calculating duty rosters |
|
|
"AutoDutyPRO for Windows 4.0 has stopped working", "application failed to initialize" |
| |
| When attempting to run AutoDutyPRO, Windows displays a message indicating that "AutoDutyPRO for Windows 4.0 has stopped working" and provides two options:
- Check online for a solution - Close the program Checking online does not find a solution, and when choosing the Close the program option, another error message is displayed that says: The application failed to initialize properly (0xc0000005). Click OK to terminate the application. Clicking OK clears the error message; however, AutoDutyPRO will not operate at all. HOW IT IS TRIGGERED This is most likely caused by a Microsoft Windows feature called Data Execution Prevention, or DEP. DEP is an advanced system setting in Windows that is meant to protect memory during an application's use. Essentially, before AutoDutyPRO can even launch, Windows prevents it from running. SOLUTION First, ensure the latest version of AutoDutyPRO, v4.32, has been installed. This release may be freely downloaded here. NOTE: On military computers, administrator privileges will be required to install this version. Second, after installation ensure that AutoDutyPRO is NOT flagged for compatibility settings. With v4.31 and later, compatibility flags are not required and, in fact, must not be enabled for AutoDutyPRO. Third, check the settings for DEP (and EMET, if it is used), adjusting if required. This only applies to v4.31 and earlier! Follow the steps below: 1. Click the Windows START button, right-click COMPUTER, and choose PROPERTIES 2. From the panel on the left, choose ADVANCED SYSTEM SETTINGS 3. In the box labeled PERFORMANCE?, click the SETTINGS button 4. Click the DATA EXECUTION PREVENTION tab 5. If the DEP tab is greyed out, this means that the DEP settings are being managed by another tool, such as EMET, and you will need to use that tool to fix this issue (starting with Step 7 below). If the DEP tab is NOT greyed out and the first option is selected, the computer is already set to OPT-OUT mode (only operating system programs and services are affected), and DEP is most likely not the cause of the issue. Skip to Step 7 below. If the DEP tab is NOT greyed out and the second option is selected, AutoDutyPRO will need to be added to the exception list. Click the Add button and navigate to the AutoDutyPRO executable. Under Windows 64-bit versions, the AutoDutyPRO executable is located here: C:\Program Files (x86)\AutoDutyPRO\a4w.exe Under Windows 32-bit versions, the AutoDutyPRO executable is located here: C:\Program Files\AutodutyPRO\a4w.exe Click OK, then OK again to close out the ADVANCED SYSTEM SETTINGS window. 6. Changes to the DEP settings may require the computer to be restarted; if so, reboot the computer. After the computer is back up, AutoDutyPRO should run without the errors above. 7. If the issue continues, and EMET is installed on this computer, one or more mitigation settings must be disabled for the AutoDutyPRO executable. The simplest method to make these changes is via the EMET GUI; if that is not available, the changes may be made via the command-line (EMET v5.0-v5.4), or via policy settings (EMET v5.5+). For all versions of EMET, disable the DEP mitigation and test. Using the command-line method as an example: EMET_conf ?set program.exe ?DEP (where ?program.exe? is A4W.EXE, including the path) If AutoDutyPRO is still prevented from running, then disable both EAF and CALLER mitigations: EMET_conf ?set program.exe ?EAF (where ?program.exe? is A4W.EXE, including the path) EMET_conf ?set program.exe ?Caller (where ?program.exe? is A4W.EXE, including the path) If EMET v5.5+ is in use, most likely these changes will need to be done via policy settings, not through the command-line. 8. If some other mitigation software is in use (e.g., CREDANT), start with disabling the DEP mitigation for the AutoDutyPRO executable. 9. If the solution here does not resolve the issue, please contact us. |
|