Kbase P183817: Errors (11628) and (4106) initiating the OpenEdge local debugger on Windows 7
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/03/2011 |
|
Status: Unverified
SYMPTOM(s):
Errors (11628) and (4106) initiating the OpenEdge local debugger on Windows 7
An error occurred when trying to establish communications for using the Debugger; Error code is: 10022. (11628)
Unable to startup PROGRESS Debugger. (4106)
The DEBUGGER-INITIATE() method and the Prodebugconfig command miscalculate the port number on Windows 7
Executing theDEBUGGER-INITIATE() method on Windows 7, when port 9999 is in use, generates errors (11628) and (4106)
Executing code similar to the following in an OpenEdge procedure Editor session on Windows 7 generates errors (11628) and (4106):
debugger:initiate(). debugger:set-break().
define variable i as integer no-undo init 0.
i = i + 1.
Executing the Prodebugconfig command on Windows 7, when port 9999 is in use, miscalculates the port and suggests the use of the busy port 9999 to connect to the prowin32 process.
FACT(s) (Environment):
The problem does not occur on Windows XP. Both the DEBUGGER-INITIATE() method and the Prodebugconfig command correctly calculate the port number.
Windows 7 32-Bit
OpenEdge 10.2B
OpenEdge 10.2B03
CAUSE:
Bug# OE00205511
FIX:
None at this time.