Chad Callihan runs into an error with an availability group:
The availability group in question was unhealthy, and none of the added databases were syncing. By the time I started investigating, the SQL service on the secondary had been restarted. There were also no recent errors in Failover Cluster Manager.
I checked the SQL Server Error Log and found some clues. The SQL Server Error Log was filled with “Always On: DebugTraceVarArgs” errors for each database that included the message:
“Seeding encountered a transient failure ‘108’, retrying…”
Read on to see how Chad fixed this.