I have several Ignition servers some pointing to the same database source. The database source is setup as an Availability Group, so the connection is to the Availability Group Listener. Our primary in that group failed over the weekend, but the secondary took over no problem. We got the Primary back online and again no problems, everything seemed to be working...
This morning I came in and noticed a random bunch of databases faulted on different servers.
For example
Server 1 Database A showed faulted
Server 1 Database B showed connected.
Database A and Database B on same AG server.
Server 2 Database A shows connected
Server 2 Database B shows faulted.
Error on servers:
Unable to access availability database 'A' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later. ClientConnectionId:d1eccca3-a61c-4e0f-8385-ec6d21f0db21
Similar message for Server 2 database B.
My quick fix was to open the faulted database connection page and save it.
Connection goes from Faulted to Connecting Stays as connecting, but I confirmed it is working via designer in a project from the Server.
Just curious if anyone else has experienced this? I Am guessing the "connecting" state of the databases will clear when we do the next scheduled reaboot.