For the last week or so I have struggled to get database mirroring with failover (failover being a witness machine) working as advertised from Microsoft. After struggling with error messages like this for the past few days:
|
2007-07-06 15:50:44.62 spid31s Error: 1474, Severity: 16, State: 1. 2007-07-06 15:50:44.62 spid31s Database mirroring connection error 2 'Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.' for 'TCP://192.168.0.8:7042'. AND 2007-07-06 15:55:00.07 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.0.7] 2007-07-06 15:55:00.09 Logon Error: 17806, Severity: 20, State: 2. 2007-07-06 15:55:00.09 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.0.7] 2007-07-06 15:55:00.09 Logon Error: 18452, Severity: 14, State: 1. AND 2007-07-06 15:57:24.26 spid26s Error: 1474, Severity: 16, State: 1. 2007-07-06 15:57:24.26 spid26s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://192.168.0.8:7024'. |
I finally broke down and called Microsoft and opened up a new case. After 10 hours (yes … Read moreMSSQL 2005 Database Mirroring With Certificates