My apologies. I didn't realise they would act differently.
So, to confirm, it should be like below now?
I tried that, and it made no difference.
Maybe the ASP.NET is the issue, and not what is being suggested?
My apologies. I didn't realise they would act differently.
So, to confirm, it should be like below now?
I tried that, and it made no difference.
Maybe the ASP.NET is the issue, and not what is being suggested?
I think it's better to call @patrick
@patrick, do you know why this might be an issue with ASP.NET? Are there any workarounds?
Thanks
Ray
ASP.NET handles errors a bit different, the error contains a lot more information and often the actual error cause is nested within the InnerException. We don't have a way to pick the different data from the error so you will need to write a custom expression for it. Best is to first just output the whole $_ERROR
within the catch to see how the object is structured and then write the desired expression you need.
Does it return just the message if you use $_ERROR.orgException.InnerException.Message
?
I can change the output for the errors, but often we'll need the extra information in it to find the actual code that triggered the error when there is some bug in the code.