Hi Thomas,

Can you be more specific as to how you resolved it by setting sys(3050) values from a config file and how you determined the appropriate values to use to resolve it? I must have missed that in this thread...


>Hi Aleksey,
>
>>You can contact product support, options are described on this page:
>>http://support.microsoft.com/oas/default.aspx?ln=en-us&c1=501&x=14&y=13&gprid=7992
>>To resolve this issue, we will likely need both code and data.
>
>What can I do in case I specifically cannot deliver the data ? I had one issue where one set of data produced at certain sys(3050)-levels (also physical ram dependant) no error, at other levels memory errors at one of two specific places in the source.
>
>Reprodudicble at our site, but by specific customer agreement we are not allowed to share the confidential data. I "fixed" it by making it possible to feed sys(3050) different values from a config-file, so not a big deal (afterwards!) for us to create app's and tweak the config file if it crops up again, but this error hasn't found it's way into MS error database.
>
>regards
>
>thomas