D
dbeavon
Guest
So it sounds like the problem is most likely related to loading the .net runtime, and related assemblies, right? I'm hoping it isn't a catch-all error message that could arise for any arbitrary .Net exception (eg, including something in the implementation of the constructor of this class: System.Net.WebClient). Why isn't there a way to get the .Net exception details? This error (14081) is not something from the .Net runtime itself. Troubleshooting is so much more difficult when Progress hides all the inner exception details. I've noticed that the .Net openclient for appserver does the same thing. It hides all the root-cause information like inner exceptions and stack traces, and replaces them with some generic message that will take many hours to troubleshoot. (You almost need to have a debugger attached before you will find the real root cause for any of the unexpected errors).
Continue reading...
Continue reading...