none
Upgrade to SQL Server 2016, stuck at SQL Server Service Health Check

    Question

  • Hi Guys,

    I am upgrading an instance from SQL Server 2014 (SP2-CU3) to SQL Server 2016, but the upgrade wizard has stuck at "SQL Server Service Health Check" for hours, when I firstly stuck here this morning, I did a reboot, apparently ,it does not work,

    Here is where I am stuck:

    I checked the upgrade log, after 18:56, there is nearly 3 hours without new log:

    (14) 2017-03-26 18:56:55 Slp: Sco: Attempting to close SC Manager
    (14) 2017-03-26 18:56:55 Slp: Sco: Returning service process id 9088
    (14) 2017-03-26 18:56:55 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle_3'
    (14) 2017-03-26 18:56:55 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$INSTANCE1' to be created
    (14) 2017-03-26 18:56:56 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$INSTANCE1' or sql process handle to be signaled

    I checked the log for that instance, it is just working as usual.

    Does anyone know what happened?

    Sunday, March 26, 2017 10:43 AM

All replies

  • Can you verify the account that SQL server is running under. You might also need to run the upgrade using an login which has administrative rights on the machine.
    Sunday, March 26, 2017 12:41 PM
  • you need change some permission.

    This failure often is caused by a system or domain policy removing the SeDebugPrivelege security privilege from the administrator account running setup. Verify that the account running has this privilege.

    Open Group Policy…

    Start | Run | gpedit.msc | OK |

    Navigate to: Computer Configuration | Windows Settings | Security Settings | Local Policies | User Rights Assignment | Debug programs

    The account through which we are trying to run the setup should be here ( besides the local admin on that machine). I included that here, restarted the server ( this is mandatory, gpupdate /force will not work) and ran the setup and it was successful this time.

    NOTE: Rebooting the Server is critical in applying the permission

    SQL Server 2008 setup needs this privilege to start up the SQL Server process and listen to an event that signals back to setup that SQL Server successfully started.

    Another link


    Please Mark it as Answered if it answered your question OR mark it as Helpful if it help you to solve your problem.


    • Edited by Av111 Sunday, March 26, 2017 1:50 PM
    Sunday, March 26, 2017 1:48 PM
  • the account was fine, after 7 hours, I got a failure re report service, on that instance we have an unused reporting service, it was turned off, I uninstalled the report service first then run upgrade again, this time takes less than 1 hour and job done.

    Thanks!

    Sunday, March 26, 2017 11:21 PM
  • Hello,

    It is working mark answer ,it will help other.


    Please Mark it as Answered if it answered your question OR mark it as Helpful if it help you to solve your problem.

    Monday, March 27, 2017 3:44 AM