June 10, 2019 at 5:20 pm
I finally sat down to install 2017 on a clustered server and got a failure message that said "setup attempted to perform an unauthorized operation." So I opened up the detail.txt file and found the relevant section:
(01) 2019-06-10 12:48:56 Slp: ----------------------------------------------------------------------
(01) 2019-06-10 12:48:56 Slp: Running Action: AS_Telemetry_Install_StartupFinalize_Cpu64
(01) 2019-06-10 12:48:56 Slp: Action Data:
(01) 2019-06-10 12:48:56 Slp: Feature = Analysis_Server_Full_sql_as_Cpu64
(01) 2019-06-10 12:48:56 Slp: Scenario = install
(01) 2019-06-10 12:48:56 Slp: Timing = StartupFinalize
(01) 2019-06-10 12:48:56 Slp: ConfigObjectType = Microsoft.SqlServer.Configuration.ASTelemetry.ASTelemetrySetupPrivate
(01) 2019-06-10 12:48:56 Slp: FeatureName = Analysis_Server_Full
(01) 2019-06-10 12:48:56 Slp: FeatureCpuType = Cpu64
(01) 2019-06-10 12:48:56 Slp: FeaturePackageId = sql_as
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Installing telemetry service for Analysis Services
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Adding Analysis Services telemetry service to Analysis Services Admins
(01) 2019-06-10 12:48:56 ASTelemetry: Getting setting ASTELSVCACCT: source = Default, type = Microsoft.SqlServer.Configuration.ASTelemetry.TelemetryServiceUserName.
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Data : (Utility) UserName=NT Service\SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Result: Role Member Added
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Action: Updating role with newly added roles
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Result: Success
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Result: Success
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Starting Analysis Services CEIP services...
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to open SC Manager
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to open service handle for service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to close service handle for service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to close SC Manager
(01) 2019-06-10 12:48:56 ASTelemetry: Getting setting ASTELSVCSTARTUPTYPE: source = Default, type = Microsoft.SqlServer.Configuration.ASTelemetry.ASTelemetryStartMode.
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to open SC Manager
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to open service handle for service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 Slp: Invoking QueryServiceStatus Win32 API
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to close service handle for service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to close SC Manager
(01) 2019-06-10 12:48:56 ASTelemetry: --ASTelemetrySetupPrivate: Starting service: SSASTELEMETRY$MyNewSQLServer, status = Stopped.
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to start service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to start service SSASTELEMETRY$MyNewSQLServer, start parameters
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to start service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to open SC Manager
(01) 2019-06-10 12:48:56 Slp: Sco: Attempting to open service handle for service SSASTELEMETRY$MyNewSQLServer
(01) 2019-06-10 12:48:59 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2019-06-10 12:48:59 Slp: ----------------------------------------
(01) 2019-06-10 12:48:59 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2019-06-10 12:48:59 Slp: Inner exceptions are being indented
(01) 2019-06-10 12:48:59 Slp:
(01) 2019-06-10 12:48:59 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2019-06-10 12:48:59 Slp: Message:
(01) 2019-06-10 12:48:59 Slp: Attempted to perform an unauthorized operation.
(01) 2019-06-10 12:48:59 Slp: HResult : 0x84bb0001
(01) 2019-06-10 12:48:59 Slp: FacilityCode : 1211 (4bb)
(01) 2019-06-10 12:48:59 Slp: ErrorCode : 1 (0001)
(01) 2019-06-10 12:48:59 Slp: Data:
(01) 2019-06-10 12:48:59 Slp: DisableRetry = true
(01) 2019-06-10 12:48:59 Slp: Inner exception type: System.UnauthorizedAccessException
(01) 2019-06-10 12:48:59 Slp: Message:
(01) 2019-06-10 12:48:59 Slp: Attempted to perform an unauthorized operation.
(01) 2019-06-10 12:48:59 Slp: HResult : 0x80070005
(01) 2019-06-10 12:48:59 Slp: Stack:
(01) 2019-06-10 12:48:59 Slp: at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
After doing some Google, I wondered if this was related to the registry / anti-virus problem, so hit "Cancel" on the error message (rather than "Retry") assuming it would uninstall everything and I'd start over when I got the anti-virus problem handled.
The only problem was that after a few seconds, the install then proceeded to tell me it had succeeded (see picture).
I am VERY confused. I'm rebooting right now, then installing SSMS locally to verify. But I can open the SQL Server Configuration Manager and see all the services up (except for Launchpad, which makes me want to crack a Disney joke but I'll refrain @=).
Any thoughts on what could be going on?
June 10, 2019 at 9:26 pm
It looks like it's only the telemetry service it couldn't install so I would consider that more of a success if everything else installed okay.
But it looks like it's just registry permissions. Are you a local admin on the box? I thought I've read others hit that same error with the registry and got things to work when they ran setup with a local admin account. Whoever manages that part of the windows server world in your company - gpo, security area - might be able to let you know what the restrictions would be with the registry access and creating a new telemetry service.
Sue
June 11, 2019 at 9:56 am
I am local admin on the box. If you think it's a registry perm issue, I'm betting it's the same registry issue other people have run into (i.e. the anti-virus problem). I'll check into that.
Thanks.
June 11, 2019 at 5:09 pm
I hit one similar to that with the registry but it was my own fault. I was a local admin but didn't run setup using Run As Administrator. I found the registry issues using Process Monitor. Fairly useless to you after the fact. But I almost always fire that up on installs now just because of weird things like this one.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply