M
Martyn Reid
Guest
Hey Valeriy, Thanks for the response. To add a bit of context... We have a .net windows service that synchronises Progress database changes into a replica SQL Server database. So we don't write any OpenEdge 4GL, we just query, via a Read Uncommitted ODBC connection, the OpenEdge audit tables and then run OpenEdge's archiveaudit routines. The solution works well and doesn't affect the source OpenEdge system. We have one particular customer who has a second OpenEdge application that is integrated with the same source OpenEdge system that we query. They use shared 4GL procedure libraries to communicate with each other. You're correct: we're not doing any ABL stuff so we're not calling SETUSERID. It is this second OE application that experiences the exceptions. The app that we query doesn't have any problems with our querying for data and our running auditarchive routines. I believe that when we run a long running (minute or two) audit archive routine (and maybe the ODBC query) the second application runs into problems communicating with our source OE application. Whilst we have dabbled in OE development we're not OE developers and our technical support ran out a few years back. We have a number of Customers using our software, all successfully, and some with the same configuration of this second OE application communicating with our source app. So I'm hoping it can be fixed with some OE server configuration changes...
Continue reading...
Continue reading...