A client could not bring the Analysis Service online in a cluster, and the logs only said Error 1067. Here is the systematic approach that found the cause.
SQL SERVER – AlwaysOn Automatic Seeding Failure – Failure_code 15 and Failure_message: VDI Client Failed
One database would not seed to the secondary replica. Here is how sys.dm_hadr_physical_seeding_stats showed failure_code 15 and VDI Client Failed.
SQL SERVER – Mirroring Error 1456 – The ALTER DATABASE Command Could not be Sent to the Remote Server Instance
Adding a new witness server after a disaster failed with database mirroring error 1456. Here is one possible cause and what to check.
SQL SERVER – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
A client used AlwaysOn automatic seeding for a huge database, but it stayed in Restoring state on the secondary. Here is the reason we found.
QL SERVER – Unable to Create Listener: Msg 41009 – The Windows Server Failover Clustering (WSFC) Resource Control API Returned Error Code 5057
Creating an AG listener failed with Msg 41009: the Windows Server Failover Clustering (WSFC) resource control API returned error 5057. Here is the fix.
SQL SERVER- Unable to Failover AlwaysOn Availability Group to Disaster Recovery Site
A client added a DR node but was unable to failover AlwaysOn Availability Group to it. The listener had only one IP address, and here is the fix.
SQL SERVER – Always On Availability Group Failover Generating Dump. Error: 17066: SQL Server Assertion: HadrFstrVnnUtils.cpp:479
A client’s availability group failover across subnets got stuck in Resolving and generated dumps with Error 17066. Here is what we found and how we fixed it.