First of all, I have to say that I am not 100% sure if this procedure is going to work. Normally, it should. But I have seen cases in which it did not.

It is relatively simple. The steps (after you install and run Visual Studio) should be:

1. Start your application (I am assuming it is not going to crash quickly and will give you time to do the steps below).
2. In Visual Studio, do Debug -> Attach to Process
3. Press the "Select" button right to the "Attach to:" box.
4. In the "Select Code Type" dialog, select "Debug these code types" radio button, and in the list below, check "Managed (v4.6, v4.5, v4.0)" and "Native".
5. Press OK.
6. In the list of processes (back in the Attch to Process) dialog, select the process of your application.
7. Press "Attach".
8. Wait for your application to crash. Hopefully, at that moment, it will break itself automatically into Visual Studio.
9. Make note/screenshot of what message appears at that moment.
10. Do Debug->Windows->Output, and select "Show output from" = Debug. Select all text (Ctrl+A), then Copy everything to clipboard, and send it to us.
11. Do Debug->Windows->Modules. In the Modules window, select all (Ctrl+A, or through right-click), then Copy everything to clipboard, and send it to us.
12. Do Debug->Windows->Threads. In the Threads window, under the Location column, expand each thread by clicking on the "down arrow". Select all (Ctrl+A, or through right-click), then Copy everything to clipboard, and send it to us. This is the most important piece of information.

Regards

Hello,

your version are all fine.
I do not know which level of debugger is included in the Visual Studio Express/Community editions. But even if it's not sufficient, I think you can install a full Visual Studio and run it for 30 days for free.

Best regards

This registry part basically shows the version of .NET Runtime and not the .NET Framework (libraries). Since all 4.x versions use the same "original" runtime version 4.0, that's what you see.

To answer this question, there are some tools to do so, or we just need to know
1) the operating system you are using, and
2) which .NET frameworks are listed in the Add/Remove Programs control panel applet of windows.

And, this question remained unanswered:
Which QuickOPC version are you using please?

Thank you

I am kind of surprised by your .NET Framework version. Our recent versions all require .NET Framework 4.5.2 minimum (and should not even run on earlier versions). See kb.opclabs.com/Versions .

Which QuickOPC version are you using please?

OK, so can you please confirm you are not using OPC DA (in this test) at all?

Anyway, this is going to be difficult, because not much is known about the exception. 0xc0000005 seems to be "Access violation" error. But, that's not normal in a .NET application - the code is managed, so it cannot normally access an invalid address, with exception of a null reference, but for that there is a different exception. It is more likely that it is related to the COM/.NET interop layer.

I do not know which tools you have at hand. If it were me, I would attached a Visual Studio debugger to the service, specifying it to debug native code AND .NET managed code, let it run, and see if it catches the exception together with call stack - which would then hopefully tell us more.

Regards