Help: SQL Server

Sharing my knowlege about SQL Server Troubleshooting Skills

  • Blog Stats

    • 1,695,749 hits
  • Select GETDATE()

    November 2019
    M T W T F S S
    « Apr    

Archive for the ‘SQL Server’ Category

SQL Server Cluster – Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).

Posted by blakhani on February 16, 2016

This is one of an interesting issue I faced with one of my customer. Its worth to share as this is NOT a very common issue and I was not able to find the solution which we discovered. We were having 2 nodes windows cluster running single clustered instance of SQL Server. Node names were SRV1 and SRV2.

Log Name:      Application
Source:        MSSQLSERVER
Date:          1/22/2016 6:10:33 AM
Event ID:      17141
Level:         Error
Keywords:      Classic
User:          N/A
Could not register Service Control Handler. Operating system error = 2310(This shared resource does not exist.).

  • Checked the log folder to see SQL server error log but there was no file generated there.
  • We tried starting the SQL server service via services.msc applet but that also did not work
  • net start mssqlserver also gives same
  • Interestingly, when we start sqlservr.exe from the command prompt it works fine.

Cluster Log shows below:

00000f44.00000ad8::2016/01/22-11:06:32.221 ERR   [RES] SQL Server <SQL Server>: [sqsrvres] StartResourceService: Failed to start MSSQLSERVER service.  CurrentState: 1
00000f44.00000ad8::2016/01/22-11:06:32.221 ERR   [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 435)
00000f44.00000ad8::2016/01/22-11:06:32.221 ERR   [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: Error 435 bringing resource online.
00000f44.00000ad8::2016/01/22-11:06:32.221 ERR   [RHS] Online for resource SQL Server failed.
0000091c.00001230::2016/01/22-11:06:32.221 WARN  [RCM] HandleMonitorReply: ONLINERESOURCE for ‘SQL Server’, gen(1) result 5018.
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] TransitionToState(SQL Server) OnlinePending–>ProcessingFailure.
0000091c.00001230::2016/01/22-11:06:32.221 ERR   [RCM] rcm::RcmResource::HandleFailure: (SQL Server)
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] resource SQL Server: failure count: 2, restartAction: 0.
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] resource SQL Server will not be restarting; isLowPriority: false; numDependents: 1, failureCount: 2, restartAction: 0
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] TransitionToState(SQL Server) ProcessingFailure–>[WaitingToTerminate to Failed].
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] TransitionToState(SQL Server) [WaitingToTerminate to Failed]–>[Terminating to Failed].
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] Will retry online of SQL Server in 3600000 milliseconds.
0000091c.00001230::2016/01/22-11:06:32.221 INFO  [RCM] TransitionToState(SQL Server Agent) WaitingToComeOnline–>OfflineDueToProvider.
0000091c.00001450::2016/01/22-11:06:32.221 INFO  [RCM] HandleMonitorReply: TERMINATERESOURCE for ‘SQL Server’, gen(2) result 0.
0000091c.00001450::2016/01/22-11:06:32.221 INFO  [RCM] TransitionToState(SQL Server) [Terminating to Failed]–>Failed.


We also had a file share resource in cluster. Interestingly that failed with error:

File system check failed because scoped network name appears not to be registered with Server service, number of shares verified: 3.

Solution: Restart the “Server” Service. We tried keeping this server is delayed start mode but that didn’t help. We found that every time we restarted the node, we had same problem. So solution was to restart the “Server” service after reboot and then failover works without problem.

Posted in Cluster, SQL Server | Tagged: , , | 10 Comments »

Solution – Unable to install SQL Server 2008 on Windows Server 2012 Server – Error – The service did not respond to the start or control request in a timely fashion

Posted by blakhani on June 10, 2015

Recently I was trying to do some test with old version of SQL and ran into interesting issue. I ran the setup of SQL Server 2008 RTM on Windows Server 2012. It failed with error

The service did not respond to the start or control request in a timely fashion

The error means that SQL Setup was unable to start the SQL Server service in middle of the installation. I had no choice but  to cancel the installation. Here are the messages logged in various setup logs. here is the snip from Summary.txt

Overall summary:

  Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.

  Exit code (Decimal):           -595541211

  Exit facility code:            1152

  Exit error code:               49957

  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.

  Start time:                    2015-05-08 21:26:19

  End time:                      2015-05-08 21:37:05

  Requested action:              Install

  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150508_212400\Detail.txt

Detailed results:

  Feature:                       Database Engine Services

  Status:                        Failed: see logs for details

  MSI status:                    Passed

  Configuration status:          Failed: see details below

  Configuration error code:      0xDC80C325

  Configuration error description: The service did not respond to the start or control request in a timely fashion. 

  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150508_212400\Detail.txt

I love the error message in summary as it tells me what exactly need to be done. Investigate, correct the cause, uninstall SQL and re-run setup. Perfect! So let’s investigate. Detail.txt had nothing interesting than telling that I am not able to start SQL Service. Since SQL service was present after cancelling the setup, I tried to start manually but it was same error via services.msc. So I tried to start SQL Server executable via command prompt by running sqlserver.exe –c –sMSQLSERVER command and it gave me below popup message.

Problem signature:

  Problem Event Name:         BEX64

  Application Name:           sqlservr.exe

  Application Version:        2009.100.1600.1

  Application Timestamp:      4bb6b40b

  Fault Module Name:          StackHash_120f

  Fault Module Version:

  Fault Module Timestamp:     00000000

  Exception Offset:           PCH_EF_FROM_ntdll+0x000000000009177A

  Exception Code:             c0000005

  Exception Data:             0000000000000008

  OS Version:                 6.3.9600.

  Locale ID:         1033

  Additional Information 1:         120f

  Additional Information 2:         120feecb532e5330843bb85768dc5d8d

  Additional Information 3:         86ef

  Additional Information 4:         86ef44a294d70f6087e5d1fcc74465eb


Read our privacy statement online:


If the online privacy statement is not available, please read our privacy statement offline:


The code highlighted above is Access Violation hex code. I did some more search and found below KB (How to use SQL Server in Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2)


So, now I know that my issue is that RTM version of SQL Server 2008 is not supported on Windows Server 2012 and I have to do slipstreaming of media so that SP2 is installed along with RTM.

I Slipstreamed media using Peter’s blog

After making media ready, I uninstalled SQL, restarted machine and used the slipstream media. This time I was able to install SQL without any error.

Hope this helps.

  • Cheers,
  • Balmukund Lakhani
  • Twitter @blakhani
  • Posted in Installation, Setup, SQL Server, SQL Server 2008 | Tagged: , , | 2 Comments »

    Restore ERROR : This backup cannot be restored using WITH STANDBY because a database upgrade is needed

    Posted by blakhani on May 21, 2015

    One of my colleague in office sent an email to find the cause of the error. He wanted to configure Log-Shipping with secondary on Standby mode. Rather than “reply to all”, I generally ping the person directly to tell the possible reason of error. Here is what we discussed (let’s assume that his name is Manoj – M)

    B: Hi Manoj
    M: Hello
    B: Saw you email to DL about log shipping problem.
    M: Oh yeah. Thanks for reaching out.
    B: No problem.
    B: Are you restoring database from lower version to higher version of SQL?
    M: No, both are 2008.
    B: That’s doesn’t sound right. Can you please run Select @@version command in Management Studio on both the server and share the output?
    M: Sure. Give me a minute to connect and run the query.
    B: Sure

    <1 min pause>

    M: There you go

    Microsoft SQL Server 2008 (SP1) – 10.0.2573.0 (X64)
    Feb 4 2011 11:27:06
    Copyright (c) 1988-2008 Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

    Microsoft SQL Server 2008 R2 (RTM) – 10.50.1600.1 (X64)
    Apr 2 2010 15:48:46
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2)


    B: Okay. that is the problem. You are taking backup from SQL 2008 and restoring on SQL 2008 R2 in standby mode.
    M: Both are not 2008?
    B: No, destination is 2008 “R2” which is the next release after 2008.
    M: Oh.. I thought its like a service pack on top of SQL 2008.
    B: Unfortunately, its not a service pack. It’s fresh release having some enhancements.
    M: Okay. So error message is correct.
    B: Yeah. If you want to use secondary for reporting then you have to use standby mode. This can only be done on destination which has same version of SQL. Or you need to upgrade current primary server.
    M: Hmm.. I got it now. Let me check with my DBA team and management to decide the next action.
    B: Sure Manoj. Is there any other clarification you might need?
    M: No Balmukund. I am good at this point. You have been very helpful. Appreciate it.
    B: My pleasure. Bye for now.
    M: Bye!

    In summary, Here is what you would get in SSMS if we try to restore a backup from lower version of SQL to higher version of SQL in standby mode.

    TITLE: Microsoft SQL Server Management Studio
    SQL Server Management Studio restore database ‘DabbaWala’
    Restore failed for Server ‘Destination’.  (SqlManagerUI)

    For help, click:
    System.Data.SqlClient.SqlError: This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY. (Microsoft.SqlServer.Smo)
    For help, click:


    The error is raised because during restore from lower to higher version the database version needs an upgrade to match with system table (or any other) change in higher version. Here is the query to see the version I am talking about.

    Select name, version from sys.sysdatabases

    This version upgrade is part of recovery process and we can’t pause recovery in middle and view the database state (that’s what is done in standby mode). So, the only way to restore that would be to use “with recovery” or “with norecovery” option.

    Hope this helps!

  • Cheers,
  • Balmukund Lakhani
  • Twitter @blakhani
  • Author: SQL Server 2012 AlwaysOnPaperback, Kindle
  • Posted in Error, Logshipping, Restore, SQL Server | Tagged: , , | 2 Comments »