Kbase 16358: Trouble-shooting ESQL error 4362
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Trouble-shooting ESQL error 4362
Possible cause of error:
Embedded SQL interface is not re-entrant. (4362)
Error 4362 is usually a symptom of a previous untrapped error.
What actually causes this message is that a fatal error
has occurred with ESQL, and the application C program logic
is such that it is trying to call into ESQL again, while the
ESQL layer thinks it is already active. The ESQL layer is
confused, but this is only a side effect of the original
fatal error.
The first thing to do to locate the original fatal error
is to use the debugger to step through the application to
the point at which it fails, and trace the ESQL calls that
are being made.
One thing to pay particular attention to is the error handling
logic inside the application. Check to make sure that you are
handling the sqlgetmsg() in all cases that an error might occur.
It is likely that you are missing the error messages that are
generated when this fatal error occurs. These are the ones you
really want to track down, because these errors will probably
point to the root of the problem.
Progress Software Technical Support Note # 16358