on 06-19-2023 11:51 AM
Ok, I know what it is: the Microsoft debugger automatically stops, when a NullReferenceException is thrown, no matter whether later some code catches and handles it or not.
RfcConfigParameters.LoadConfiguration() first tests, whether the program runs as a standalone/desktop .NET Application or as a Web Application inside IIS. Unfortunately, this is possible only by some Microsoft .NET API, which throws a NullReference when not running in IIS... 😞
But the exception is then caught internally in NCo, and the code branch for "standalone .NET Application" is then executed and everything continues normally.
So basically: just ignore the exception, everything works fine! You can disable the feature that the .NET debugger stops at that exception like Sandra has done here:
https://answers.sap.com/questions/13508257/getdestination-returns-object-reference-not-set-to.html
(By the way, a quick search on answers.sap.com would have found that solution and saved you the trouble of creating a new question for an already known problem...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
11 | |
7 | |
6 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.