I have a few applications that use your product. One is a slightly older app so it still needs updating to the latest but below are the versions being used -
OpcLabs.EasyOpcUA, Version=5.70.1012.1
OpcLabs.EasyOpcUA, Version=5.71.302.1
I was recently made aware that on occasion the operator on the production line has found the programs to no longer be running and is needing to restart the programs. I checked the Windows Application Event Log and find at those times there are unhandled exceptions being logged. Below is an example. I cannot find (yet) any particular time of day, length of time the program has been running, etc. that might tell me why it crashes. Sometimes the program will run for days without an issue and other times it might crash and have to be restarted twice in a 24 hour period. Please let me know if this might be something I can solve with an update to QuickOPC. I did try using Visual Studio 2019 to do performance profiling and did not see what appeared to be memory leaks which I thought it might be since researching that exception says low resources on a computer can cause. My applications looks to keep a very small memory footprint of around 45mb and 96mb respectively. Thank you for your help!
Application: BackPrintInterface.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.EasyUAClientEngine.GetMonitoredItemEntry(OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient, Int32)
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.EasyUAClientEngine.InnerUnsubscribeMonitoredItems(OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient, Int32[])
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.EasyUAClientEngine.UnsubscribeMonitoredItems(OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient, Int32[])
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient.InternalUnsubscribeAllMonitoredItems()
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient.InternalDispose(Boolean)
at OpcLabs.BaseLib.Internal.DisposableObject.Dispose(Boolean)
at OpcLabs.BaseLib.Internal.DisposableObject.Finalize()
Faulting application name: BackPrintInterface.exe, version: 1.0.0.0, time stamp: 0x63e3ca19
Faulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f709e
Exception code: 0xc0000006
Fault offset: 0x00026619
Faulting process id: 0x1854
Faulting application start time: 0x01d9e2001ec97ae4
Faulting application path: \\ENTDFS01\Applications\Mperia\Sites\SD\BackPrintInterface.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: ce8267d7-9654-4b7c-a7a1-bf07306d5c8d
Faulting package full name:
Faulting package-relative application ID:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program BackPrintInterface because of this error.
Program: BackPrintInterface
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: C0000034
OpcLabs.EasyOpcUA, Version=5.70.1012.1
OpcLabs.EasyOpcUA, Version=5.71.302.1
I was recently made aware that on occasion the operator on the production line has found the programs to no longer be running and is needing to restart the programs. I checked the Windows Application Event Log and find at those times there are unhandled exceptions being logged. Below is an example. I cannot find (yet) any particular time of day, length of time the program has been running, etc. that might tell me why it crashes. Sometimes the program will run for days without an issue and other times it might crash and have to be restarted twice in a 24 hour period. Please let me know if this might be something I can solve with an update to QuickOPC. I did try using Visual Studio 2019 to do performance profiling and did not see what appeared to be memory leaks which I thought it might be since researching that exception says low resources on a computer can cause. My applications looks to keep a very small memory footprint of around 45mb and 96mb respectively. Thank you for your help!
Application: BackPrintInterface.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.EasyUAClientEngine.GetMonitoredItemEntry(OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient, Int32)
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.EasyUAClientEngine.InnerUnsubscribeMonitoredItems(OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient, Int32[])
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.EasyUAClientEngine.UnsubscribeMonitoredItems(OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient, Int32[])
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient.InternalUnsubscribeAllMonitoredItems()
at OpcLabs.EasyOpc.UA.Implementation.NetSdk.Client.NetSdkEasyUAClient.InternalDispose(Boolean)
at OpcLabs.BaseLib.Internal.DisposableObject.Dispose(Boolean)
at OpcLabs.BaseLib.Internal.DisposableObject.Finalize()
Faulting application name: BackPrintInterface.exe, version: 1.0.0.0, time stamp: 0x63e3ca19
Faulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f709e
Exception code: 0xc0000006
Fault offset: 0x00026619
Faulting process id: 0x1854
Faulting application start time: 0x01d9e2001ec97ae4
Faulting application path: \\ENTDFS01\Applications\Mperia\Sites\SD\BackPrintInterface.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: ce8267d7-9654-4b7c-a7a1-bf07306d5c8d
Faulting package full name:
Faulting package-relative application ID:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program BackPrintInterface because of this error.
Program: BackPrintInterface
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: C0000034