Kbase P131682: Debugger from within an application fails with error (4106).
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/13/2008 |
|
Status: Unverified
SYMPTOM(s):
When opening the debugger, after the splash screen appears, a one-character error message is generated:
T
Unable to startup PROGRESS Debugger. (4106)
Debugger enabled with ProDebugEnable -enable-all.
Debugger invoked within 4GL code as follows:
DEBUGGER:INITIATE().
DEBUGGER:SET-BREAK().
When debugger is started first and then attached to a procedure, it does not fail.
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
OpenEdge 10.1C
CAUSE:
This is a known issue.
FIX:
One or more of the following steps may prevent the error from occurring.
Check the Data Execution Prevention (DEP) setting:
Right click the My Computer icon on the desktop and select Properties, or choose System from the Control Panel, to display the System Properties dialog.
Select the Advanced tab.
In the Performance section, click the Settings button.
Select the Data Execution Prevention tab.
Either select "Turn on DEP for essential Windows programs and services only", or click the "Add..." button and add <JREHOME>\bin\java.exe to the list of excepted programs.
Click the OK button in each of the dialogs to exit.
From Proenv, run ProDebugEnable -enable-all.
Set the JREHOME environment variable as in step 2 below.
Set the JREHOME environment variable:
Right click the My Computer icon on the desktop and select Properties, or choose System from the Control Panel, to display the System Properties dialog.
Select the Advanced tab.
Click the Environment Variables button.
Click the New button.
Add the variable JREHOME to the System section. Set its value to <DLC>\jre. For <DLC>, use the exact DLC path (for example, "C:\Progress\OpenEdge"); do not use "%DLC%".
Click the OK button in each of the dialogs to exit.
Start the debugger using the Compile>Debug menu option or the Shift-F4 function key rather than running the procedure with Compile>Run or F2. If the already contains code to start the debugger, exit the debugger, and it will start correctly when the DEBUGGER: statements are reached.