Hello Daniel,

It is working well in Lyon airport since years with version 10.0SP1
Communication ModBus IP and OPC

Hello Daniel.

Your question (and also the title of this thread) is confusing.
I think what you mean is not that the FireDemon project crashes, but the PcVue project, right?
Also, it is not FireDemon which is restarting, but FireDemon is restarting the sv32 process, right?

Is it really a problem that is related to FireDemon (ie. launching PcVue as a service)? Have you tried to reproduce the problem when starting PcVue normally without FireDemon (as an application and not as a service)?

Have you looked at the exception message in detail? Obviously, its origin is in the 104-driver. Is there anything else that we can guess from the exception? Does it occur upon reading or writing of a variable, upon connection/disconnection of a device or sector or else...?

Hello,

Yes, FireDaemon is restarting the sv32 process.

The exception does not occur on start up. According to the customer and the exceptions log, the exception also doesn't occur regularly.
As I wrote before, this happens every couple of hours or sometimes there is no problem for a some days.
So I guess this is really hard to reproduce...

I don't think FireDaemon is the reason for the crash.

The customer said, it looks like FireDaemon detects a loss of the connection to the devices and then is restarting the process. They got this information from the internal FireDaemon log.

Unfortunately I personally cannot extract any more info form the exception. There is only this line
Exception handler: _104Family::_Run() and then the exception text with all the errors starts.

Mostly the first erros are:
1: 1
1: ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 69661452)
1: 69661452 (svvar): (filename not available): _LocalServer::AckWrite

1: 2
1: ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 69342B6D)
1: 69342B6D (svvar): (filename not available): COperate::SendAckWrite

But I'm not sure if this really helps to find the cause...

Why not asking the FireDaemon support's opinion?

I just received the log file of firedaemon for the sv32 process.

Each time such an exception occurs you find the following in the log:

Mon Jan 12 18:57:07 2015 [0x3e70]: Service 'sv32' is not restarting by Scheduler now, just stopped.
Mon Jan 12 18:57:07 2015 [0x3e70]: Killing the process just to make sure it's gone.
Mon Jan 12 18:57:07 2015 [0x3e70]: Ready to terminate process: handle=624 procID=2156
Mon Jan 12 18:57:07 2015 [0x3e70]: Service 'sv32': Event no. 106 [0x6a], The service failed to shutdown correctly.Reason: subprocess unable to be killed
Mon Jan 12 18:57:07 2015 [0x3e70]: Service 'sv32': Event no. 123 [0x7b], Subprocess monitoring failed due to subprocess is no longer active
Mon Jan 12 18:57:07 2015 [0x3e70]: Start child process.
Mon Jan 12 18:57:07 2015 [0x3e70]: Will be started interactive.
Mon Jan 12 18:57:07 2015 [0x3e70]: Launching process '"D:ARC InformatiquePcVue 11Binsv32.exe" -p srl-clens -wsa'
Mon Jan 12 18:57:07 2015 [0x3e70]: Starting the process Interactively as a user, flags = 0x00000020
Mon Jan 12 18:57:07 2015 [0x3e70]: AddRemoveTheAceWindowStation. Remove mode = 1.
Mon Jan 12 18:57:07 2015 [0x3e70]: Address of SID Pointer = [0x2f6a20]
Mon Jan 12 18:57:07 2015 [0x3e70]: SID of this Process = S-1-5-5-0-85224032
Mon Jan 12 18:57:07 2015 [0x3e70]: There are 10 active ACEs on the window station
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-12
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-12
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-32-544
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-32-544
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-18
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-18
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-5-0-85221187
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-5-0-85221187
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-5-0-85224032
Mon Jan 12 18:57:07 2015 [0x3e70]: Found GENERIC_ACCESS ACE on the Window Station I created, removing it.
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-5-0-85224032
Mon Jan 12 18:57:07 2015 [0x3e70]: Found WINSTA_ALL ACE on the Window Station I created, removing it.
Mon Jan 12 18:57:07 2015 [0x3e70]: Cleaning up any created ACEs on the Window Station
Mon Jan 12 18:57:07 2015 [0x3e70]: Modifying the security descriptors for the window station
Mon Jan 12 18:57:07 2015 [0x3e70]: There are now 8 active ACEs on the window station
Mon Jan 12 18:57:07 2015 [0x3e70]: AddRemoveTheAceDesktop. Remove mode = 1.
Mon Jan 12 18:57:07 2015 [0x3e70]: There are 5 active ACEs on the desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: Found DESKTOP_ALL ACE on the Desktop I created, removing it.
Mon Jan 12 18:57:07 2015 [0x3e70]: Cleaning up any created ACEs on the Desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: Modifying the security descriptors for the desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: There are now 4 active ACEs on the desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: Ace desktop success.
Mon Jan 12 18:57:07 2015 [0x3e70]: AddRemoveTheAceWindowStation. Remove mode = 0.
Mon Jan 12 18:57:07 2015 [0x3e70]: Address of SID Pointer = [0x2f6a20]
Mon Jan 12 18:57:07 2015 [0x3e70]: SID of this Process = S-1-5-5-0-85224032
Mon Jan 12 18:57:07 2015 [0x3e70]: There are 8 active ACEs on the window station
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-12
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-12
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-32-544
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-32-544
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-18
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-18
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-5-0-85221187
Mon Jan 12 18:57:07 2015 [0x3e70]: Current ACE SID = S-1-5-5-0-85221187
Mon Jan 12 18:57:07 2015 [0x3e70]: Adding GENERIC_ACCESS ACE to the Window Station
Mon Jan 12 18:57:07 2015 [0x3e70]: Adding WINSTA_ALL ACE to the Window Station
Mon Jan 12 18:57:07 2015 [0x3e70]: Modifying the security descriptors for the window station
Mon Jan 12 18:57:07 2015 [0x3e70]: There are now 10 active ACEs on the window station
Mon Jan 12 18:57:07 2015 [0x3e70]: AddRemoveTheAceDesktop. Remove mode = 0.
Mon Jan 12 18:57:07 2015 [0x3e70]: There are 4 active ACEs on the desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: Adding DESKTOP_ALL ACE to the Desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: Modifying the security descriptors for the desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: There are now 5 active ACEs on the desktop
Mon Jan 12 18:57:07 2015 [0x3e70]: Ace desktop success.
Mon Jan 12 18:57:07 2015 [0x3e70]: CreateProcess() call returned 1
Mon Jan 12 18:57:07 2015 [0x3e70]: Launched process (38496) '"D:ARC InformatiquePcVue 11Binsv32.exe" -p srl-clens -wsa'
Mon Jan 12 18:57:07 2015 [0x3e70]: Service 'sv32': Event no. 17 [0x11], The program "D:ARC InformatiquePcVue 11Binsv32.exe" -p srl-clens -wsa
Mon Jan 12 18:57:07 2015 [0x3e70]: Try to remove lost SIDs for the interactive user.
Mon Jan 12 18:57:07 2015 [0x3e70]: Current Process SID = S-1-5-5-0-85224032

Ciao Daniel,

I remember one case where some mistakes in IEC-104 configuration causes PcVue to crash in random way with a similar behaviour (if I'm not wrong due of a duplication of ASDU).

You can ask Cesar to help you for decipher the sv32exception...

Hope it helps,

Ciao Filippo,

Thanks for the info and the tipp!

I will do that.

Hello,

I am agree with filippo, you can ask Cesar to help you for decipher the sv32exception and put me in copy because the crash come from 104 protocol

Issue was resolved in PcVue 11.1.06018.13445
Thank you Jaques, Dominique and Cesar!