D
dbeavon
Guest
Its a long shot, but intermittent problems like this may somehow be related to code page conversions. Perhaps .Net and ABL are having integration issues of some type. I saw the same .Net error message in the release notes for 11.6; there is some relationship to the code page that was used. see link: OpenEdge 11.6 Release Notes - Wiki - OpenEdge General - Progress Community The hard part may be to reproduce the issue *consistently*. We've had code page error messages in our PASOE logs in the past but don't seem to get them anymore. I was never able to isolate a consistent reproducible for this: [17/11/22@12:33:21.133-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031) [17/11/22@12:33:21.138-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031) [17/11/22@12:33:21.146-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031) [17/11/22@12:33:21.149-0500] P-012800 T-008724 1 AS-7 -- The client's code page in unknown. No code page conversions will be made. (8031) We've changed our code around significantly since then. One thing we stopped doing is using the QUIT statement to restart our so-called "session-managed" client activity. That was problematic for us. Perhaps it negatively impacted the SESSION code page. It would be helpful if there was additional logging that was specific to code page operations in an ABL session. Good luck, David (FYI, I am currently using the .Net framework successfully from PASOE on Windows; and I don't see the code page errors in PASOE that I had seen in the past.)
Continue reading...
Continue reading...