Invalid database

[Danijela06]

Hi all,

On one our site we have Geo scada 2021 October 2022 Update, two server in hot-standby mode.

They works fine but yesterday we get situation that one server is in state Invalid database and second shutdown. After we shutdown both, and if we start one it goes Main, and we start second server it goes to synchronization and on end we got server that was Main to shutdown and second got Invalid database.

Both server work just fine alone. 

From DBLog we get: "11-OCT-2024 07:57:55.977 4260 [STBYMON] Main Link UPOV_S2 (Monitor Connect Timeout 60, Monitor Request Timeout 240, Uncompressed) Connect returns 8007274C -> A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."

I have to mansion than end user installed new graphic card before that situation happened.

On application event log there is Application error on DBServer.exe and ModulePaht: C:\WINDOWS\System32\OLEAUT32.dll.

Any ideas how to fix this?

[AndrewScott]

The DB log error is just a generic Windows networking error indicating a TCP connection has failed.

The application error in DBServer indicates that the server has crashed, but the module path doesn't provide any useful information. "OLEAUT32.dll" is just part of Windows.

To investigate this issue will require the full DB log file(s) and the crash dump file associated with the application error and possibly a copy of the database. These should be passed to Schneider's customer support for analysis.

It looks like the main server is crashing whilst synchronising with the other server. The other server goes into the "Invalid database" state as it hasn't yet received the complete database (from the main server) so it would be unsafe to continue (data loss or corruption).

[Danijela06]

Andrew,

I've send DB Logs to support but thinking maybe someone had similar problem, as it is weekend.

When I delete complete database on one server they start synchronization and ended in Main-Standby state but when they had to change again Invalid Database and Shut down. I tried this process on both servers. If the database is correct then the configuration is problem?

Yesterday before all started unexpected Windows update happened...  

[Danijela06 · Accepted solution]

Dear all,

I've got answer from support and that was solution for my problem. I'm posting it so maybe will help someone too.

I did the following :
1) stop both servers
2) delete the database from the standby server and Create a Blank Database.
3) start the main server
4) start the standby server
5) check the synchronization status of the servers

Best regards