Hi All,
I have found issue in OpenEdge(10.1B) ADM2,.
After adding the new record at client side, while trying to save, getting the following error message
Error: "** FIND FIRST/LAST failed for table RowObjUpd". (565)
I am getting this error rarely. I am not able to find the root cause of this issue.
Please suggest .
Thanks
Are you running with -debugalert (or SESSION:DEBUG-ALERT)? If not, turn it on and when the error appears, click help and look at the entries in the debug list to determine where the issue is occurring.
Thanks Kevin,
But there is a issue while putting Debug alert.
Since this error in unpredictable, means this error occours rendomely.
and we are also using debug alert for showing some information to client.
So, it will provide all unexpected message, though we are not sure when error will raise again.
Since i have't found this error in earliar version of progress, So, I just want to know .
Is it a BUG in OpenEdge 10.1B for ADM2 ?
Since RowobjUpd is ADM defined table, So it should me handle by ADM environment properly.
Thanks
Vishwdeep
vishwdeep.pandey wrote:
Thanks Kevin,
But there is a issue while putting Debug alert.
Since this error in unpredictable, means this error occours rendomely.
and we are also using debug alert for showing some information to client.
So, it will provide all unexpected message, though we are not sure when error will raise again.
Since i have't found this error in earliar version of progress, So, I just want to know .
Is it a BUG in OpenEdge 10.1B for ADM2 ?
Since RowobjUpd is ADM defined table, So it should me handle by ADM environment properly.
Thanks
Vishwdeep
I have no idea if this is a bug in 10.1B, but at my current client we are using 10.1B03 and I've not seen this happen.
Is it possible to update to service pack 3 (considering if you contact support that is the first thing they will tell you to do)?
you should be using the event "end-update".
When we got out of this event, the framework adm2 executes the following code:
"IF ERROR-STATUS: ERROR THEN
RUN dispatch ('show-errors': U).
"
to avoid this error do:
"ERROR-STATUS: ERROR = no"
or use another event like the "assign"
sorry for my english