D
dbeavon
Guest
I think the biggest problem with this... Cannot throw or return error/stop object to remote client because object is not serializable or client does not support it. (14438) ... is that it is essentially the equivalent of an "unhandled exception" which is escaping ABL/PASOE . But there is no more information than that. The logs don't have any additional detail, and the .Net openclient receives no additional information than a generic message saying that an error occurred. That is not what software developers generally expect from unhandled exceptions. There is a lot more information that is available within our S.E.H Progress errors, including their data type, member fields, and stack information, and ToString() output. Why can't this stuff be written somewhere? I probably wouldn't even mind if the MS-agent-session crashed as long as it gave me the relevant information about the unhandled exception that was escaping the ABL runtime environment. We have configured our sessions using the -errorstack. Is there any other parameter I can use to force the session to spill all the related error information that is available?
Continue reading...
Continue reading...