What caused it would be up for debate. To fix it delete the Transaction Log files so they can be rebuild. Ensure the server does a controlled shutdown so that the transaction logs are cleared.
Hurry though as the wrong time could have a severe impact on your database consistency. AND, once fixed pull NEW replicas to the clients. If this is not resolved you may need to restore from backups.
Also, long paths in Windows will create issues for the full eclipse client as some of the path names exceed the maximum Windows can handle. The fact that you have used “Program Files” as a default for the server may/might/could cause additional issues. it is highly recommended to place the server in a shorter path such as c:\Notesrv and d:\Notesrv\Data.
I’m having the same problem after upgrading my admin server; two member servers are writing rubbish to the names & admin4 dbs. I’ve stopped the server, deleted trans logs and started it again, but am getting the same errors.
Having this issue. Trying to simple replace the server replica with a new one without the problem. the server is in testing so it is not an issue to have an outage but would like to understand how it happened.