About Me

My photo
I am an MCSE in Data Management and Analytics, specializing in MS SQL Server, and an MCP in Azure. With over 19+ years of experience in the IT industry, I bring expertise in data management, Azure Cloud, Data Center Migration, Infrastructure Architecture planning, as well as Virtualization and automation. I have a deep passion for driving innovation through infrastructure automation, particularly using Terraform for efficient provisioning. If you're looking for guidance on automating your infrastructure or have questions about Azure, SQL Server, or cloud migration, feel free to reach out. I often write to capture my own experiences and insights for future reference, but I hope that sharing these experiences through my blog will help others on their journey as well. Thank you for reading!

OnlineThread: Error 435 bringing resource online and error 2310 while failover of database server.

Issue:-

Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).
n  [sqsrvres] StartResourceService: Failed to start MSSQL$HomeSQL01 service.  CurrentState: 1
n  [sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
n  [sqsrvres] OnlineThread: Error 435 bringing resource online.
n  Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).
n  [sqsrvres] StartResourceService: Failed to start MSSQL$HomeSQL01 service.  CurrentState: 1
n  sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
n  [sqsrvres] OnlineThread: Error 435 bringing resource online.



Environment:-

2 Node Windows Cluster and 2 SQL Server Service installed in each node as SQL Server Cluster

Windows Server Name : 
  •                                          Windows2k8r2-1 
  •                                          Windows2k8r2-2
SQL Server ServiceName:

  •                                           MSSQL$HomeSQL01
  •                                           MSSQL$HomeSQL02
   Windows Server 2008 R2 and SQL Server 2008 R2 Enterprise edition..  

 Problem:-

   Both SQL Server Service running on Wndows2k8r2-2. I tried to failover MSSQL$HomeSQL02 SQL Server service from Windows2k8r2-2 to Windows2k8r2-1 and observed below in Cluster Manager console.

  1. Network Name successfully failed over.
  2. All disks related to that resource group success
  3. SQL Server service failed
  4. SQL Server Agent offline.

After, Failover  of SQL Server service, I tried to check error log of SQL Server service and found New Error log of MSSQL$HomeSQL02 did not create. {Strange}

I also tried the same with 2nd SQL Server service[MSSQL$HomeSQL02] failover from Node2 to Node1. and found New Error log of MSSQL$HomeSQL02 did not create.

      Then Checked System event viewer and Application event viewer and found below sequence of events..

          -- Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).
n  [sqsrvres] StartResourceService: Failed to start MSSQL$HomeSQL01 service.  CurrentState: 1
n  [sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
n  [sqsrvres] OnlineThread: Error 435 bringing resource online.
n  Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).
n  [sqsrvres] StartResourceService: Failed to start MSSQL$HomeSQL01 service.  CurrentState: 1
n  sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
n  [sqsrvres] OnlineThread: Error 435 bringing resource online.


Then I reviewed Cluster log and did not find much information from there..  
Since both SQL Server service did not start from 1st node, hence the assumption was to any OS component is got corrupt.

Resolution:-


I  found hint here https://support.symantec.com/en_US/article.TECH155434.html and thought to give a try.. 

for some people issue resolved by repairing .netFrameWork framework 3.5 SP1 and rebooting the node.

I also tried the same and issue resolved. 

what I did is:
   1. On problematic node repaired .NetFramework 3.5 sp1.
   2. Rebooted Problematic node.
  3. Then did failover and found failover of both SQL Server service happened successfully.

 Thanks for reading! Kindly give your comment, if it helped you in resolving the issue.  :)



  



    



Labels: ,