V
Valeriy Bashkatov
Guest
Ок. I have no idea which OpenEdge server parameters can affect this. As an option, you need to see the code of the second OE application, where the error occurs. For the second application session, you can enable advanced logging. Then reproduce the error, and see in which procedure and on which line the error occurred. See ABL client session parameters "Client Logging (-clientlog)", "Debug Alert (-debugalert)", "Log Entry Types (-logentrytypes)" with 4GLMessages, 4GLTrace, DB.Connects options, "Logging Level (-logginglevel)" with level 4 (Extended). At a minimum, this will allow us to understand where the error occurs in the ABL code of the second application, and proceed from this point further. I do not think the transaction isolation level on the side of ODBC somehow can influence the appearance of this error. It's possible that the second application is not connected to the database at this time, or it was for some reason disconnected from this database. Most likely, advanced logging will help to understand this. In addition, it is worth looking at the log of your OpenEdge database, maybe there are some important messages there.
Continue reading...
Continue reading...