I've added a database to an availability group that already has a few databases, all of which seeded and syncing fine to the secondary.
This last one gets added to the availability group, it would seem, but is marked as "not synchronizing" and no errors are returned. I've tried it multiple times with the same result.
I've looked in extended events, Event Viewer... nothing. Clicking on "warnings" in the dashboard says nothing useful. The database files do not exist on the secondary at all. I suspect that it was blocked right at the start of its seeding process (but clearly after the initial validations in the "add to AG" wizard).
I have this distinct feeling SQL server must be logging a relevant failure message to some DMV I'm not aware of.
Is there a canonical guide to ALL the places one is supposed to look for AlwaysOn related errors?