I can tell you how many times I have heard about this error. This can appear in any of the situation where SQL needs to create a cluster network name resource in the WSFC Cluster. Here are the two situations I can think of:
Installing SQL Server Failover Cluster instance.
Creating listener in the AlwaysOn availability group.
This blog is an outcome of an email communication with my client. The issue was that they were having big tempdb files. They had multiple files and of uneven size. As soon as they restart SQL, the initial size itself was huge and when they tried to shrink the TempDB database, it was not doing anything. Here was the message in SQL Server Management Studio query window.
If you work with a product for a long time, you would start loving it. I have worked with many other RDBMS, but my love to SQL Server will never die. The amount of information available in logs is very helpful and can help in pointing the exact issue related to retrieve data.
As a part of my passion, I try to help people in fixing simple issues and explain the behavior by looking at logs. Here is an email from my friend about Availability Group Missing or Deleted Automatically.
One of my client was unable to modify the maintenance plan using SSMS. When we did various tests, we found that existing maintenance plans could execute and work. We tried creating a new maintenance plan and found it to be working. So, our issue is confined to “unable to modify existing plans”. Here is the error message
One of my client was trying to start SQL Service and it was failing. I asked to hare ERRORLOG so that we will get some idea about the cause. Here is the information from ERRORLOG file.
While I have been blogging about SQL Server for a long time, I still believe that there is still a lot of error which are not discovered by me. It is always fun to see new error and find a fix for the issue. Let us see how to fix error related to MERGE statement.