none
Attempted to perform an unauthorized operation RRS feed

  • Question

  • Hi

    First time got this error while installing SQL Server 2014 Express on a Win 10 Pro 64bit.

    How can I fix it? The user seems to be a member of Administrators.

    Thanks

    Regards


    • Edited by Y a h y a Saturday, July 1, 2017 2:11 PM
    Saturday, July 1, 2017 2:10 PM

Answers

  • As Hilary says, you need to look at the setup logs or share them somewhere we can look at them.

    I recall that another poster got this error messge some months back. It turned out in that case, he was running some anti-malware program that protected his registry a bit to vigorously. Disabling it was not sufficient, but he had to uninstall it, to be able to install SQL Server.

    Now, the message you get is a fairly generic one, so the underlying reason in your case may be different. But I still mention this in case it rings a bell with you.

    • Marked as answer by Y a h y a Saturday, July 1, 2017 5:29 PM
    Saturday, July 1, 2017 3:40 PM

All replies

  • As Hilary says, you need to look at the setup logs or share them somewhere we can look at them.

    I recall that another poster got this error messge some months back. It turned out in that case, he was running some anti-malware program that protected his registry a bit to vigorously. Disabling it was not sufficient, but he had to uninstall it, to be able to install SQL Server.

    Now, the message you get is a fairly generic one, so the underlying reason in your case may be different. But I still mention this in case it rings a bell with you.

    • Marked as answer by Y a h y a Saturday, July 1, 2017 5:29 PM
    Saturday, July 1, 2017 3:40 PM
  • Hi Hilary

    Which of the log files would be relevant? Below are from Detail.txt.

    Thanks

    Regards

    The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2017-07-01 16:29:13 Slp: Inner exceptions are being indented
    (01) 2017-07-01 16:29:13 Slp: 
    (01) 2017-07-01 16:29:13 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    (01) 2017-07-01 16:29:13 Slp:     Message: 
    (01) 2017-07-01 16:29:13 Slp:         Attempted to perform an unauthorized operation.
    (01) 2017-07-01 16:29:13 Slp:     HResult : 0x84bb0001
    (01) 2017-07-01 16:29:13 Slp:         FacilityCode : 1211 (4bb)
    (01) 2017-07-01 16:29:13 Slp:         ErrorCode : 1 (0001)
    (01) 2017-07-01 16:29:13 Slp:     Data: 
    (01) 2017-07-01 16:29:13 Slp:       WatsonData = HKEY_LOCAL_MACHINE@SYSTEM\CurrentControlSet\Services\FltMgr
    (01) 2017-07-01 16:29:13 Slp:       DisableRetry = true
    (01) 2017-07-01 16:29:13 Slp:     Inner exception type: System.UnauthorizedAccessException
    (01) 2017-07-01 16:29:13 Slp:         Message: 
    (01) 2017-07-01 16:29:13 Slp:                 Attempted to perform an unauthorized operation.
    (01) 2017-07-01 16:29:13 Slp:         HResult : 0x80070005
    (01) 2017-07-01 16:29:13 Slp:         Stack: 
    (01) 2017-07-01 16:29:13 Slp:                 at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess)


    (01) 2017-07-01 16:41:38 Slp: Error result: -2068119551
    (01) 2017-07-01 16:41:38 Slp: Result facility code: 1211
    (01) 2017-07-01 16:41:38 Slp: Result error code: 1
    (01) 2017-07-01 16:41:38 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
    (01) 2017-07-01 16:41:43 Slp: WER: Result of the submission:: 'WerReportUploaded'
    (01) 2017-07-01 16:41:43 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
    (01) 2017-07-01 16:41:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2017-07-01 16:41:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2017-07-01 16:41:43 Slp: Sco: Attempting to get registry value CustomerFeedback


    • Edited by Y a h y a Saturday, July 1, 2017 3:56 PM
    Saturday, July 1, 2017 3:54 PM
  • That looks like the relevant part.

    I note that you too run into a problem with a registry key. You should be able to see which key it is if you look at the part just before the exception.

    I would definitely suspect firewall/AV software to be the culprit.

    Saturday, July 1, 2017 5:52 PM