ODB omnis databridge failure after first connection

[roland at optiektotaal.nl]

Hi all,

 

I was wondering if any of you have experienced similar failures with the
omnis databdrige.

 

The win server 2019 is hosted on a VM (hyper-v). 

The datafiles are placed on this server. 

The omnis databridge is installed on the server. 

Client pc's are all windows based. I use omnis 11 runtimes to access the
data through the omnis databridge.

 

The log of the omnis databridge shows:

! This is just the moment of failure! During normal operation, the odb shows
no failures.

 

06/11/2023  17:53:10 : 10.0.0.203 : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Client disconnect : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Client disconnect : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Client disconnect : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Disconnect...OK

06/11/2023  17:53:10 : 10.0.0.203 : Client disconnect : Disconnect...OK

07/11/2023  08:54:17 : 10.0.0.201 : Connect...OK

End of log

 

So they log of in the evening. All well. And then the first connection to
the databrdige seems the fault or force stop the odb. 

 

After that I installed omnis RT and the odbconfig tool. So I could monitor
connections more closely. I could not see anything faulty. But. when I
installed this, the odb kept running. No more failures for two weeks,
instead of every 3 or so days.

 

Then the RMM software on the server auto update updated windows server and
rebooted the system (saterday night). And the omnis RT with odbconfig was no
longer running.

This was followd by a day of stable performance on Monday (closed on
Sunday). Followed by a failure of the odb on Tuesday, similar to the logging
above.

 

In the eventviewer of windows I see the application error.

Faulting application name: odbridge.exe, version: 0.0.0.0, time stamp:
0x62a6fec1

Faulting module name: odbridge.exe, version: 0.0.0.0, time stamp: 0x62a6fec1

Exception code: 0xc0000005

 

The annoying part is, the odb probably (asumption) is faulting before this,
but since there are no requests the service keeps running.

 

Do you guys and ladies have any advice?

Any similar experiences?

Any tweaks to improve stability?

 

Tnx in advance!

 

Vriendelijke groet,

 

Roland Voshol

06-52891237

 

OptieKTotaal

Probleemloos automatiseren

www.optiektotaal.nl