Timeline for SQL Server 2012 Always On AG - DBEngine Service account locking
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2022 at 15:00 | history | tweeted | twitter.com/StackDBAs/status/1597606318315110406 | ||
| Sep 20, 2015 at 13:09 | vote | accept | Sam Partridge | ||
| Sep 20, 2015 at 13:09 | answer | added | Sam Partridge | timeline score: 3 | |
| Sep 4, 2015 at 6:58 | comment | added | Sam Partridge | At this point I've opened all firewall ports, created a new service account for the dbengines, removed all of the availability groups, deleted the endpoints, bounced the nodes, recreated the availability groups.. and it locks the account again at the last step. I am able to telnet from node 2 to the endpoint port on node one. I have used TCP View to watch connections coming from node two on the correct port. Checked that SQL Server is actually listening on the correct port... | |
| Sep 3, 2015 at 9:45 | history | edited | marc_s | CC BY-SA 3.0 |
deleted 5 characters in body; edited title
|
| Sep 3, 2015 at 7:43 | comment | added | Sam Partridge | I found this on the secondary node: A connection timeout has occurred while attempting to establish a connection to availability replica '#######' with id [62E7F607-7D0C-4AE1-BAE3-0934882BF2DE]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance." This seems to be the start of it all. Firewall ports are open on both nodes | |
| Sep 3, 2015 at 7:20 | comment | added | Sam Partridge | The login events in both the SQL Logs and the Application log of the primary node are: Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed). State 67.'. [CLIENT: ##.##.##.##].. Our server team are checking the domain controller for me as I don't have access. These seem to be more a result of the account locking out, now trying to find an error leading up to it. | |
| Sep 2, 2015 at 20:17 | comment | added | James Lupolt | Can you find the failed login events in the logs on the database server and domain controller that led to the lockouts? | |
| Sep 2, 2015 at 19:47 | history | asked | Sam Partridge | CC BY-SA 3.0 |