[Migrated content. Thread originally posted on 11 January 2012]

Recently, users are intermittently getting this error when working with Commercial Policies. It seems to happen when processing endorsements, applying payments, removing terrorism notices or approving policies (no clear pattern, in other words). It throws them out of the app, however when they reenter it again, they are able to process without the any issues.

It is an 'Attempt to access item beyond bounds of memory', but I can't find the manual referenced in your knowledge base (Handling Protection Violation Errors in the 'Program Development Manual' Chapter 5) on this website to try and find out why, suddenly, this is occurring. I have gotten it to occur in animate and a mfdebug.log is produced, but I'm not sure how I can use this for debugging purposes.

A runtime error 114 is kind of a catch-all error usually indicative of some sort of memory corruption or call stack corruption.

It can occur for many reasons but some of the more frequent reasons are that calls are being made with incorrect parameter sizes or numbers or you have a mismatch between the Net Express compiler version and the Server run-time version.

Things to check would be the version and wrappack level of both the compiler and Server products installed and also ensure that all your application programs have been compiled with the same version.

The MFDEBUG.LOG can be useful to see what programs are on the call stack at the time of the error and you can also see from where the cblrtss.dll runtime is being loaded. Frequently an old copy may be getting loaded from within the PATH and this can cause these types of problems.

If none of the above appears to be a problem then you should probably open up a new incident with Supportline because debugging a 114 error will take more resources than are available through this forum.

Thanks.

---