SQL server down, I need help!!!

Question

00002044.0000290c::2024/09/24-17:17:04.853 ERR   [RES] SQL Server Availability Group <ETL_LST>: [hadrag] Did not find the instance to connect in SqlInstToNodeMap key. 00002044.0000290c::2024/09/24-17:17:04.853 WARN  [RHS] Online for resource ETL_LST failed.

Answer 1

Hi @Debo Ademosu ,

Thank you for your reaching out and welcome to Microsoft Q&A!

For the event log IDs, you could refer to Failover Clustering system log events.

This error message:

Did not find the instance to connect in SqlInstToNodeMap key.

The SqlInstToNodeMap is a registry key which should have the same information as sys.dm_hadr_instance_node_map. Please refer to https://blog.sqlauthority.com/2018/10/12/sql-server-always-on-ag-hadrag-did-not-find-the-instance-to-connect-in-sqlinsttonodemap-key/#:~:text=Just%20before%20failure,%20we%20see%20this.

The error code 0x8007139a is also pretty generic and means "The cluster resource could not be brought online by the resource monitor." You can try the following methods：

1. Restart the cluster service.
2. Run “Clear-ClusterDiskReservation” and try again.
3. Check if there is a problem with the connection between the disk and the node.
4. Check whether you have proper network settings at your place. Sometimes Network fluctuations cause of getting the issue.
5. If it still cannot bring online, as Olaf said please collect and upload Error Logs in detail.

Thank you for your understanding! Your time and cooperation are much valued by us. We are looking forward to hearing from you to assist further.

Best regards,

Lucy Chen

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

https://docs.microsoft.com/en-us/answers/support/email-notifications

Answer 2

With that less on informations no one can even guess anything; really.

Review Windows EventLog, Cluster Log and SQL Server ErrorLog for more details.