

Please Log in or Create an account to join the conversation. If it does not, we will need to look at it further (looking for reproducible scenario first). If it does, upgrade (we do not support or fix version 5.35, sorry). If that does not help, next action would be to rebuild your app with latest QuickOPC and retest, to see if the problem goes away. Your first attempt should be to try the steps described in the forum article you linked to. Obviously, handle leak, if it coming from QuickOPC, would be a bug. The bottom line is that there is practically nothing we can infer from these message alone.Īd 3 and ad 4. Also, the DAServerManager mentioned in the seconds message is not "ours". Specifically, I find it somewhat weird that the first message mentioned CIOPServer.cpp file - a) that's not our file, and b) is your software written in C++? That would be quite unusual for Windows Forms app. They might be related to your (or other software) handling some QuickOPC-related exception - or not - but there is no way to tell, because nothing in the texts comes from QuickOPC. The errors on the image do not resemble anything that has to do with QuickOPC. This fix will be going through the usual testing processes and hopefully it will solve our problems in production but in the interim we are trying to get a greater understanding of what these problems are.Ĭan you provide any more information on the symptoms associated with Quick OPC handle leaks? If it is a known bug (which it surely must be), then do you have any records of symptoms and problems that other users have experienced with it? Handle leaks can be very tricky things to link specifically with unwanted application behaviour but any information the OPC team could provide on this would be much appreciated.Īd 1 and ad 2.



We have a applied the fix suggested by OPC and it has eliminated the handle leaks. The CIOPCServer.cpp error I sent in the first message is actually from our Archestra OI Gateway Server which manages the connection to the OPC Server but is itself not OPC code. The logs I have provided you with are captured from the System Management Console of our automation software platform software (Wonderware Archestra/inTouch) and for sure are not OPC client logs. The application in question is written in c# and utilises QuickOPC. Apologies If I wasn't clear on a few things in my initial message.
