Progress error 8336 when attempting to connect Explorer tool to Adminserver.
Solution ID: qad55794
Usage: 1
Status: Unverified
Last Modified: 01/31/2008
Fact: Progress 9.1X
Fact: Progress Open Edge 10.X
Fact: Windows 2003 Service Pack 1
Fact: Windows XP Service Pack 2
Fact: Progress Explorer
Fact: Progress Adminserver
Symptom: Cannot connect to Adminserver with Progress Explorer
Symptom: Progress error 8336
Symptom: Unable to connect to Adminserver. Ensure Adminserver is running. (8336)
Symptom: Adminserver is started in Windows Services.
Symptom: Running a 'proadsv -query' returns to command prompt with no message.
Symptom: No Java processes in Task Manager.
Symptom: No Adminserver log files created.
Symptom: Windows Data Execution Prevention error for java.exe on bootup of server.
Cause: Microsoft's Data Execution Prevention (DEP) is preventing Java from launching. The Adminserver runs under a Java process. If Java can not start, the Adminserver will not start. If the Adminserver is set to Autostart in Services (as is the default), it will try to launch java.exe on bootup and the error will occur.
Fix: Turn off DEP for the Java process. This will allow Java to start, which will allow the Adminserver to start. There is an option in the pop-up message on Windows reboot to change settings for DEP to allow java.exe to run. If the pop-up window is no longer displayed, you can access the DEP setting by right-clicking on My Computer => Properties => Performance => Data Execution Prevention and select 'Turn on DEP for essentional Windows programs and services only.' This will allow Java to start and allow the Adminserver to start.