Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

Application failed with .NET runtime related issue when used in COM mode

More
16 Nov 2017 10:19 #5660 by m.baumgartner
Hello,

Our application is a windows service that uses QuickOPC UA for COM to collect data from devices on the network. We've been conducting a stress test lately and have been observing the following issue :

The Windows service fails and shut down on it's own. A windows system log has been found indicating the following :

Erreur à 01:06:26 .NET RuntimeApplication : Cprod.exe
Version du Framework : v4.0.30319
Description : le processus a été arrêté en raison d'une exception non gérée.
Informations sur l'exception : code d'exception c0000005, adresse d'exception 07677324
Erreur 01:06:28 Application Error
Nom de l’application défaillante Cprod.exe, version : 1.0.0.0, horodatage : 0x5a04779e
Nom du module défaillant : ntdll.dll, version : 10.0.15063.608, horodatage : 0x802f667e
Code d’exception : 0xc0000005
Décalage d’erreur : 0x00085ab4
ID du processus défaillant : 0x2c14
Heure de début de l’application défaillante : 0x01d35deca19ac5d1
Chemin d’accès de l’application défaillante : C:\Program Files (x86)\Smcom Software\Cwork\bin\Cprod.exe
Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\ntdll.dll
ID de rapport : a0cd2565-f921-41bb-b2d6-115f2838fbec
Nom complet du package défaillant :
ID de l’application relative au package défaillant :


I'm sorry it's in french but it's quite understandable.
Apparently it's a .Net Runtime related error.

We're not using any other .Net related components in our application.


Our stress test protocol is the following :

- 14 boolean OPCDA tags changing value every 5 seconds. All together.
- Our app gets the events and act accordingly with our internal algorithm

It worked perfectly fine the time it lasted (around 6 to 7 hours) with CPU usage at decent levels.
It then crashed around 1:06 AM without any error that we were able to catch.

An idea?

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.156 seconds