Dragan,

Thank you for your answer. I'll try anything by now, but as I wrote earlier,
once it occurs the error seems to wander all over the app, so it's difficult to see any particular pattern, which of course makes it nearly impossible to fix the problem.

I'm fairly certain that it's Citrix related, since I've never seen it happen in an ordinary installation.

It is a C0000006 and not a C0000005 error, btw.

Regards

Peter



>>The setup is something like this:
>>
>>6 Citrix servers, to which users are randomly assigned at logon.
>>I assume this has something to do with automatic load balancing.
>>
>>The app itself resides on an application server.
>>
>>The error occurs randomly, sometimes on one, sometimes on several Citrix servers at the time, but can, once it occurs, be consistently reproduced on said server(s) until they are rebooted.
>>
>>There is nothing obvious in the code, that (at least to me) would explain why.
>>
>>For instance READ EVENTS or
>
>That may be what the log shows, but it's quite possibly something else. Does this really happen when the Read Events is issued, or is it just that the app is seemingly idle and then something hits it?
>
>>

IF CURSORGETPROP("SOURCETYPE") = 1 OR CURSORGETPROP("SOURCETYPE") = 2

>>
>>can fire the error, which in general seems to wander all over the application.
>>
>>Hopefully none of the above can be considered to be spectacular transgressions of any kind?
>
>I seem to remember that calling pemstatus() twice in the same line used to cause c0000005s a few versions ago... if that's the case, try
>
>

nSourceType=CURSORGETPROP("SOURCETYPE")
>if inlist(nSourceType, 1, 2)...

>
>Who knows, it may just be something like that. Disclaimer: this is just a hunch, no exact science here.