Open josh2112 opened 6 years ago
I don't know anything, but the error says "Liberty PRO OPC Server" -- OPC is a different thing than OPC-UA. You don't build OPC server using OPC UA stack, do you?
I did; I'm in the right place. My code is built with UA-.NET and based on the UA Sample Server project.
AFAIK it won't work -- if you want to develop OPC soft use OPC stack, if you want to develop OPC-UA soft use OPC-UA stack, no mixing.
@astrowalker , I think you're getting hung up on terminology and missing my actual question. As I said, my code is based on the UA Sample Server found in the UA-.NET (now UA-.NET Legacy) sample code. If you look at the stack trace and the log provided in the first post you can see the framework used. If there's an issue with me referring to it as OPC instead of OPC-UA, I apologize, maybe a poor naming choice on my part; but that's not relevant to question.
As stated in my original post, I have had this server working for some time now. I connect to it frequently from the UA Expert client for testing. It's worked fine on every PC up to this point. My question is not one of development or choice of framework.
Does anyone else have any insight? I have seen posts such as this one from StackOverflow suggesting that on my particular system the certificate is getting read into the wrong "provider", but I'm in over my head on certificate issues like this.
I've had a working OPC server integrated into my product for several months. I don't know much about certificates. I recently had an issue with my Windows 10 PC so I performed a "reset". After reinstalling Visual Studio and rebuilding and running my server, I get this exception inside Opc.Ua.Configuration.ApplicationInstance.Start():
Luckly I had the trace file enabled. Here's its output. It seems to be having a problem with the certificate -- it creates it, then immediately fails trying to load it. Is "Invalid provider type specified" a clue??