Kbase 18360: Error 735 Running AppServer or a Persistent Procedure
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress Appserver
Progress 8.2x
SYMPTOM(s):
** Incomplete write when writing to the server. (735)
Using persistent procedures or the AppServer
One of your procedures includes the timer OCX
CAUSE:
This is a Progress bug (98-04-02-052) that was patched in Version 8.2C05 and fixed in Version 8.3A.
The error is caused by an attempt to run two pieces of code at once.
If your code calls an AppServer procedure, it will sit and wait for the procedure to return, as with any other run statement. If, during this wait time, the OCX timer fires as well as the trigger that runs attempts to read from the database, the error is generated.
FIX:
A fix for this issue is available in 8.3A and 9.0A.
In order to workaround this error, before you call the AppServer procedure reset the timer so that it will not fire during the call.
When the call returns, you can reset the timer value to its normal state.
Alternatively, you can set a flag which is tested by the tick trigger before you attempt to access the database. Reset the flag when the call returns.