Kbase P124042: OpenEdge Architect debugger fails with single user database connection
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/05/2007 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.1x
SYMPTOM(s):
OpenEdge Architect debugger fails with single user database connection
If the OpenEdge Architect uses a single user connection to the database, then the database is not available to the debugger.
CAUSE:
This is expected behavior. The product is working as designed. A multi user database connection is a prerequisite for using the OpenEdge Architect debugger.
When the debugger is started from within the Architect, another separate prowin32.exe session is started for the debugger process. Subsequently this new session also needs to be able to connect to the database, and therefore a multi user database broker is required.
In the Architect online help the following section documents this:
Prerequisites for using the Debugger
To use the Debugger:
You must enable debugging for your OpenEdge environment by running a command line utility, proDebugEnable. This is a one-time procedure; you need to repeat it only if you disable debugging or reinstall OpenEdge.
You must make compiled r-code available for all files to be debugged. You can specify in your project properties settings whether .r files are automatically created when you compile code, and where the files are stored.
You must make sure that the database connections used by your application allow multiple users; that is, that the connection parameters do not include the -1 option. See Adding database connections to a project.
FIX:
If you need to use the debugger start and connect to a multi user database broker from the Architect session.