| Data Execution Prevention (DEP) |
In newer Microsoft Operating System environments (Server 2003 SP1 and higher), your Trac product may be prevented from executing by Windows' implementation of Data Execution Prevention (DEP). In its focus on security Microsoft has implemented stronger defaults and privilege reduction on services that prevents your Trac server application from executing. To resolve this issue it is just a matter of making a simple exception change within the DEP properties.
| What is DEP? |
| Data Execution Prevention (DEP) is a set of hardware and software technologies that perform additional checks on memory to help prevent malicious code from running on a system. The primary benefit of DEP is to help prevent code execution from data pages.|
| Symptoms |
| When DEP is preventing your application from executing, the Trac product is immediately shut down after you attempt to start it. If you have just installed your Trac server application and are unable to run the program to enter your installation information, it is most likely due to DEP settings.|
| How do I set my Trac application as an Exception? |
| To make the necessary changes you must be an administrator on the server and logged in as such.|
- Go to your start menu, right-click My Computer and select properties from the menu.
- Select the Advanced tab then click on the Settings button under the Performance heading.
- In the Performance Options select the Data Execution Prevention tab.
- In the DEP settings select the radio button next to "Turn on DEP for all programs and services except those I select".
- Next click the Add button and browse for your Trac product executable file (i.e. tutortrac.exe, advisor.exe, fitness.exe, labtrac.exe) in the installed folder.
- Click Apply to save the changes you have just made, then OK in the Performance Options window, and lastly OK in the System Properties window.
*Your server may require a restart to put the settings into effect.
*The DEP Settings may need to be entered multiple times to stick. This has been the case with some Windows servers.