The sql services are not coming up in another node of the cluster?
Question
Tuesday, February 4, 2014 5:18 PM
Hi All,
we have active active 2008r2 cluster. for example we have A instance on Node1 and B instance on Node2. last week we fail over the B sql instance from Node2 to Node1. all resources are came online except sql services. after this we checked the event viewer and found the below errors.
1) [sqsrvres] OnlineThread: Error 435 bringing resource online.
2) Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).
3) Another computer has sent a name release message to this computer, probably because a duplicate name has been detected on the TCP network. The IP address of the node that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
4) Failed to initialize
SQLSQM timer. One of the following can be the source of the problem: registry
doesn't contain all necessary information, server instance name can not be
retrieved correctly, failure during timer creation, etc
and then we google it and came to know, it's happened because of .net frame work got corrupted. we have only one way to uninstall the .net and reinstall it on problem node and then reboot the server.
but we didn't see the any other errors related to the .net corrupted in server. we didn't fail over the A instance from Node1 to Node2 and fail back from Node2 to Node1 to check it's working fine or not.
Please help me to come out from this problem.
Thanks in Advance,
rup
All replies (4)
Wednesday, February 5, 2014 9:23 AM
Hi,
Have you tried starting SQL from command prompt?
.NET framework could be the culprit. Since it a prerequisite for SQL server, the service would not be able to come online without the .NET framework 3.5. We would not be able to tell what exactly could have caused the corruption of .NET framework.
In addition, the file share are suspicious. Open Server Manager > File Services > Share and Storage Management, and check if there are duplicate shares. If so, delete the duplicate both , then restart the Server service.
Thanks.
Tracy Cai
TechNet Community Support
Wednesday, February 5, 2014 11:07 PM
Hi Tracy,
Thanks for the reply...
we didn't try to start the sql server service through command prompt.
if it is problem with .net... already A instance is working fine on Node1... when we move the B instance from Node2 to Node1 we facing the problem, so how we can say it is problem with .net.
when you want to me to check the file shares? means presently we are maintaining the A instance on Node1 and B instance on Node2... in this situation I checked the file shares it is good we don't have duplicate file shares as per my knowledge. do u want to me to check after move the B instance from Node2 to Node1?
please explain clearly how can I check the file shares?
Thanks,
rup
Friday, February 7, 2014 6:07 AM
Hi,
I understand your concerns. If .NET framework was corruption on Node 1, why instance A still works fine on Node 1 but instance B not. In my option, this is possible. For example, when applying a .NET Framework update, it may be fails due to the corruption components of .NET Framework. However, we can still use the previously installed program which requires .NET Framework. Until the updates failing or programs not work correctly, we do not .NET Framework components were broken. Generally, I can see the .NET Framework related error message in the program’s log because .NET Framework itself has not logs to indicate it status.
If .NET Framework is the culprit in this case, I suspect only the part of it was broken. Thus, the currently running instance A was not effected while instance B not.
To check the duplicate shares factor, open Server Manager->File Services->Share and Storage Management. If duplicate shares exist, the shared drives letter will show twice. You can check it on both nodes.
Thanks
Tracy Cai
TechNet Community Support
Friday, February 7, 2014 3:18 PM
Hi Tracy,
Thank You Tracy for your explanation. so, we have only one option to come out from this problem that is uninstall the .net on Node1 and reinstall it after that reboot the Node1.
one more thing, we may have chance to face the same problem when we move the A instance from Node1 to Node2. I don't think so because the B instance is working fine when we fail back it from Node1 to Node2.
As per my knowledge the file shares are good we don't have duplicate shares.
if you have any Microsoft document which is say about the above problem, please provide to me it will help to us to talk with wintel team to uninstall the .Net and reinstall it.
Thanks,
rup