A few days ago, I wrote a blog where I have to perform repair of the SQL instance to fix the issue. While running repair, I encountered an interesting error. In this blog, we would learn how to fix error “The service cannot be started, either because it is disabled or because it has no enabled devices associated with it” during the repair process.
I started to repair SQL Server installation using “Repair” option
Almost at the end, I encountered the first popup with an error message
I always read Detai.txt for such issues. I searched for the text which is there on the screen (i.e. IS_Telemetry_Repair_Startup_Cpu64) and found below.
(01) 2018-02-03 08:37:58 Slp: Running Action: IS_Telemetry_Repair_Startup_Cpu64
When I checked services, there were few disabled services and I need to find which service is causing an error. If we look at above log, we can see service name SSISTELEMETRY140. To find the display name of the service we can see below command.
sc getdisplayname SSISTELEMETRY140
Name = SQL Server Integration Services CEIP service 14.0
We can see that display name via services.msc and indeed, it was disabled along with one more service.
To fix the issue, I need to change the Startup type to Manual and hit retry on the screen.
I enabled earlier service, I again got the same error for another service.
And here is the log.
(01) 2018-02-03 08:41:47 Slp: Running Action: SQL_Telemetry_Repair_Startup_Cpu64
(01) 2018-02-03 08:41:47 Slp: Sco: Attempting to open SC Manager
(01) 2018-02-03 08:41:47 Slp: Sco: Attempting to open service handle for service SQLTELEMETRY
(01) 2018-02-03 08:41:47 Slp: Sco: Attempting to close service handle for service SQLTELEMETRY
(01) 2018-02-03 08:41:47 Slp: Sco: Attempting to close SC Manager
(01) 2018-02-03 08:41:47 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2018-02-03 08:41:47 Slp: —————————————-
(01) 2018-02-03 08:41:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2018-02-03 08:41:47 Slp: Inner exceptions are being indented
This time service name is SQLTELEMETRY and here is the display name – SQL Server CEIP service (MSSQLSERVER)
I performed the same steps for this service also and clicked “Retry” button to move forward.
Do you know the use of these services? I think this is used by Microsoft to capture usage data for SQL Server service, Integration service, and Analysis service.
Reference: Pinal Dave (https://blog.sqlauthority.com)