December 1, 2010 at 2:22 pm
Hi All
am getting nowhere searching for this -
We have experienced Random failed login alert being generated on the secondary mirror. The principle server is still up. No Witness involved in this setup.
Principle is Windows 2K8 R2 Enterprise x64 - SQL Server 2008 Enterprise x64
Mirror is the same configuration
No Witness
The alerts seem to be generated close to alerts posted that the secondary has lost connection with the mirror, however NOT all the alerts are being generated like this - they just seem to happen.
Has anyone experienced this before - we have looked in old/stale network cache - but this secondary server is brand new - never been in production before.
Application is using an ADO.net connection with a cfg file with the destination server - no caching of enumerated SQL installations or such.
It just seems like the principle is switching login attempts to the secondary when it looses connection with the mirror - seems like -but this doesn't make sense
Can anyone suggest something else for me to look at - thanks
December 7, 2010 at 10:03 pm
Do you have the failover partner specified in the application connection string? What source is bring provided for where the login is failing?
Is the application reporting a login failure was experienced, or the mirroring session? What service accounts are you using between the mirroring session?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply