Any help would be appreciated. Thanks < >Help with my application please Can't open image(s) with error: External component has thrown an exceptionHelpful Please support me on Patreon: have a problem when deploying application to server.Primarily related to External component has thrown an exception or unknown error. As I go look at queries, seems to be related to a folder connection linking to mdb/MDB files.
Rename this
However it did not occur again after closing and restarting our application.The computer in question did not seem to be stressed out. If they opted to ignore the error, then the program continued working but the error re-occurred when this routine was next run. Hence it may or may not have been this error.From the stack-trace, the actual error was when constructing a class which does not directly call any interop code, but perhaps complicated by the fact that the object may be part of a list that is databound to a DevExpress Grid.The error was 'caught' by an unhandled exception routine which normally will close down the program, but has an option to ignore and continue. They were unable to give me more details and I could not find any logged errors. I have learnt from experience, not to take this description too literally, as it usually means that someone relating to the computer is not working as expected. They mentioned that in the last month, the computer has twice 'stopped working'.
External Component Has Thrown An Exception Dll And This
Then I relaunched Visual Studio under a different user account which was an administrator on the machine. I encountered the very same error reported by OP.I realized that Visual Studio was launched with a user account which was not an administrator on the machine. I was calling a native method by performing p/invoke on a C++ assembly loaded at run-time. Net project in Visual Studio 2017 Community edition. This is often an indication that other memory is corruptThe component makers say that this has been fixed in the latest version of their component which we are using in-house, but this has not been given to the customer yet.Given that the consequences of the error are low (no work is lost and restarting the program and getting back to where they were only takes a minute at most) and given that the customer will shortly be getting a new version (with the updated third-party component), I can obviously cross my fingers and hope the error won't occur again.Operating System : Windows 10 Version 1703 (x64)I faced this error while debugging my C#. Another section of the same program uses a third party component which is effectively a dotnet wrapper around a native dll and this component does have a known issue where very occasionally, you get aAttempted to read or write protected memory.