SQL Server 2008 Enterprise SQL Server 2008 Developer SQL Server 2008 Standard SQL Server 2008 Standard Edition for Small Business SQL Server 2008 Workgroup SQL Server 2008 R2 Developer SQL Server 2008 R2 Enterprise SQL Server 2008 R2 Standard SQL Server 2008 R2 Standard Edition for Small Business SQL Server 2008 R2 Workgroup Еще…Меньше
Корпорация Майкрософт распространяет исправления Microsoft SQL Server 2008 в один файл для загрузки. Поскольку исправления являются кумулятивными, каждый новый выпуск содержит все исправления и исправления для системы безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008.Корпорация Майкрософт распространяет исправления Microsoft SQL Server 2008 или SQL Server 2008 R2 как один файл для загрузки. Поскольку исправления являются кумулятивными, каждый новый выпуск содержит все исправления и исправления для системы безопасности, которые были включены в исправленный выпуск SQL Server 2008 или SQL Server 2008 R2.
Проблемы
При запуске программы установки SQL Server 2008 или SQL Server 2008 R2 программа установки может завершить работу со сбоем и произойдет неуправляемое исключение. Кроме того, в журналах настройки регистрируются сообщения об ошибках, похожие на приведенные ниже.
Индекс (Отсчитываемый от нуля) должен быть больше или равен нулю и меньше, чем размер списка аргументов. Код ошибки 0x84B10001.
Примечание. Это исключение не является исходным сообщением об ошибке.
Причина
Эта проблема возникает из-за ошибки в программе установки SQL Server 2008 или SQL Server 2008 R2. Существует множество возможных сценариев, которые могут инициировать эту ошибку. Например, сбой в предыдущей установке SQL Server может повредить реестр, и это повреждение реестра может вызвать эту ошибку.
Решение
Сведения о накопительном пакете обновления
SQL Server 2008 R2
Исправление для этой проблемы впервые выпущено в накопительном обновлении 5. Для получения дополнительных сведений о том, как получить этот накопительный пакет обновления для SQL Server 2008 R2, щелкните следующий номер статьи базы знаний Майкрософт:
2438347 Накопительный пакет обновления 5 для SQL Server 2008 R2 Примечание. Поскольку сборки являются кумулятивными, каждый новый выпуск исправлений содержит все исправления и все исправления безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008 R2. Рекомендуется установить последнюю версию исправления, которая включает это исправление. Дополнительные сведения см. в следующей статье базы знаний Майкрософт:
981356 Сборки SQL Server 2008 R2, выпущенные после выпуска SQL Server 2008 R2
SQL Server 2008 с пакетом обновления 1
Исправление для этой проблемы впервые выпущено в накопительном обновлении 10 для SQL Server 2008 с пакетом обновления 1 (SP1). Чтобы получить дополнительные сведения об этом накопительном пакете обновления, щелкните следующий номер статьи базы знаний Майкрософт:
2279604 Накопительный пакет обновления 10 для SQL Server 2008 с пакетом обновления 1 (SP1)Примечание. Так как сборки являются кумулятивными, каждый новый выпуск исправлений содержит все исправления и все исправления безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008. Корпорация Microsoft рекомендует установить последнюю версию исправления, которая включает это исправление. Дополнительные сведения см. в следующей статье базы знаний Майкрософт:
970365 Сборки SQL Server 2008, выпущенные после выпуска пакета обновления 1 (SP1) для SQL Server 2008 Исправления Microsoft SQL Server 2008 создаются для конкретных пакетов обновления для SQL Server. Вы должны применить исправление для SQL Server 2008 с пакетом обновления 1 (SP1) к установке SQL Server 2008 с пакетом обновления 1. По умолчанию любое исправление, предоставленное в пакете обновления SQL Server, входит в следующий пакет обновления для SQL Server.
SQL Server 2008 с пакетом обновления 2
Исправление для этой проблемы впервые выпущено в накопительном обновлении 1 для SQL Server 2008 с пакетом обновления 2. Чтобы получить дополнительные сведения об этом накопительном пакете обновления, щелкните следующий номер статьи базы знаний Майкрософт:
2289254 Накопительное обновление 1 для SQL Server 2008 с пакетом обновления 2Примечание. Так как сборки являются кумулятивными, каждый новый выпуск исправлений содержит все исправления и все исправления безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008. Рекомендуется установить последнюю версию исправления, которая включает это исправление. Дополнительные сведения см. в следующей статье базы знаний Майкрософт:
2402659 Сборки SQL Server 2008, выпущенные после выпуска пакета обновления 2 (SP2) для SQL Server 2008
Статус
Корпорация Майкрософт подтверждает наличие этой проблемы в своих продуктах, которые перечислены в разделе «Применяется к».
Ссылки
Чтобы получить дополнительные сведения о модели добавочного обслуживания для SQL Server, щелкните следующий номер статьи базы знаний Майкрософт:
935897 Модель обслуживания изменений, используемая рабочей группой SQL Server, предоставляет модель ISM для распространения исправлений обнаруженных проблемЧтобы получить дополнительные сведения о схеме присвоения имен обновлениям SQL Server, щелкните следующий номер статьи базы знаний Майкрософт:
822499Новая схема присвоения имен пакетам обновлений программного обеспечения Microsoft SQL ServerЧтобы получить дополнительные сведения о терминологии обновления программного обеспечения, щелкните следующий номер статьи базы знаний Майкрософт:
824684 Стандартные термины, используемые при описании обновлений программных продуктов Майкрософт
Нужна дополнительная помощь?
Нужны дополнительные параметры?
Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.
В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.
Hi Vatseq,
Could you please share the full error message to us for analysis? You can get it from Program FilesMicrosoft SQL Server120Setup BootstrapLog****_****Detail.
Based on my experience, this issue can be caused in the following scenarios:
1. If you have installed SQL Server before, this problem could occur when the previous failed installation of SQL Server is not removed completely.
2. SQL Server installation media is corrupted, you can check its MD5 or SHA1, if it is corrupted, please download SQL Server installation media from https://www.microsoft.com/en-sg/download/details.aspx?id=42299 .
3. The user did not have the permissions to access the register, you can grant full permissions to below registry keys to the setup account and SQL Service account.
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server120
You can uninstall SQL Server and then install it again by using the following steps:
1. Uninstall SQL Server by using the following steps:
At normal conditions, you can uninstall SQL Server by going to ‘Programs and Features’, then right click Microsoft SQL Server **** and select Uninstall, click Remove. On the Ready to Remove page, review the list of components and features that will be uninstalled,
then click Remove to begin uninstalling.
If SQL Server cannot be uninstalled completely, you can use the following steps to uninstall SQL Server:
1. Uninstall the existing SQL Server Express and all the components from the control panel.
2. Backup the registry and delete the following keys in registry:
—HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
—HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServer
3. Go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall and delete all the sub-keys referencing SQL Server.
4. Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices and delete all the keys referencing SQL Server.
5. Rename all the SQL Server folders in the computer.
6. Reboot the machine.
2. Install it again, use administrator to open full installation media. Change the SQL Server service account and SQL Server Browser account to Local System.
In addition, SQL Server 2014 is not supported on windows 10, we should apply SQL Server 2014 Service Pack 1 or a later update.
Regards,
Teige
-
Edited by
Thursday, July 21, 2016 6:04 AM
-
Proposed as answer by
Alberto MorilloMVP
Thursday, July 21, 2016 11:24 AM -
Marked as answer by
Lydia ZhangMicrosoft contingent staff
Friday, July 29, 2016 10:06 AM
OS: Windows Server 2012 R2
When attempting to install SQL Server 2016 on a Server that is already running SQL 2012 I receive 0x84BB0001. This stops my Database Engine Service from installing correctly.
There is no antivirus running.
Ive deleted the contents of C:/Users/[UserName]/AppData/Local/Microsoft_Corporatio
Ive given admin rights to the following:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server130
Really at a loss for what to do here?
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068119551
Start time: 2016-10-31 15:39:25
End time: 2016-10-31 15:53:10
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: FUALSNA_SQL
Machine processor count: 1
OS version: Microsoft Windows Server 2012 R2 Standard (6.3.9600)
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SSMS 1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Adv_SSMS 1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2016
ProductName: SQL Server 2016
Type: RTM
Version: 13
SPLevel: 0
Installation location: D:x64setup
Installation edition: Standard
Product Update Status:
User selected not to include product updates.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT ServiceSQLAgent$SQL
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20161031_153925ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTROPENLICENSETERMS: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQL2016
INSTANCENAME: SQL
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$SQL
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: FUALSNAadministrator
SQLTELSVCACCT: NT ServiceSQLTELEMETRY$SQL
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: false
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20161031_153925ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The specified driver is invalid.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=0x476BF04A%400xDC80C325&EvtType=0x476BF04A%400xDC80C325
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20161031_153925SystemConfigurationCheck_Report.htm
(01) 2016-10-31 15:52:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2016-10-31 15:52:47 Slp: Inner exceptions are being indented
(01) 2016-10-31 15:52:47 Slp:
(01) 2016-10-31 15:52:47 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2016-10-31 15:52:47 Slp: Message:
(01) 2016-10-31 15:52:47 Slp: The specified driver is invalid.
(01) 2016-10-31 15:52:47 Slp:
(01) 2016-10-31 15:52:47 Slp: HResult : 0x84bb0001
(01) 2016-10-31 15:52:47 Slp: FacilityCode : 1211 (4bb)
(01) 2016-10-31 15:52:47 Slp: ErrorCode : 1 (0001)
(01) 2016-10-31 15:52:47 Slp: Data:
(01) 2016-10-31 15:52:47 Slp: WatsonData = perf-MSSQL$SQL-sqlctr13.0.1601.5.dll@OpenSQLPerformanceData@CollectSQLPerformanceData@CloseSQLPerformanceData
(01) 2016-10-31 15:52:47 Slp: DisableRetry = true
(01) 2016-10-31 15:52:47 Slp: Inner exception type: System.ComponentModel.Win32Exception
(01) 2016-10-31 15:52:47 Slp: Message:
(01) 2016-10-31 15:52:47 Slp: The specified driver is invalid.
(01) 2016-10-31 15:52:47 Slp:
(01) 2016-10-31 15:52:47 Slp: HResult : 0x80004005
(01) 2016-10-31 15:52:47 Slp: Error : 2001
(01) 2016-10-31 15:52:47 Slp: Stack:
(01) 2016-10-31 15:52:47 Slp: at Microsoft.SqlServer.Configuration.Sco.PerformanceCounter.LoadPerformanceCounter(String symbolInstallPath, String counterPrefixServiceName)
(01) 2016-10-31 15:52:47 Slp: at Microsoft.SqlServer.Configuration.Sco.PerformanceCounter.RegisterPerformanceCounterCore(String libraryFileName, String openFunction, String collectionFunction, String closeFunction, String symbolInstallPath, String counterPrefixServiceName)
(01) 2016-10-31 15:52:47 Slp: at Microsoft.SqlServer.Configuration.Sco.PerformanceCounter.RegisterPerformanceCounter(String libraryFileName, String openFunction, String collectionFunction, String closeFunction, String symbolInstallPath, String counterPrefixServiceName)
jarlh
41.9k8 gold badges45 silver badges63 bronze badges
asked Oct 31, 2016 at 5:09
For anyone else having this particular issue, my solution was to download a new ISO from Microsoft. Appears that at some point my ISO was corrupted. New ISO worked perfectly.
answered Nov 2, 2016 at 0:25
Mark WilsonMark Wilson
271 gold badge1 silver badge5 bronze badges
I discovered that I would repeatedly get this error when attempting to install MSSQL 2016 SP1 or SP2 on Windows Server 2012 R2 With latest updates as of OCT 2018.
0x84BB0001 A connection was successfully established with the server,
but then an error occurred during the login process. (provider: SSL
Provider, error: 0 — No process is on the other end of the pipe.)
Solution:
Re-enable TLS1.0 and attempt to install again.
(We recently disabled TLS 1.0 on our Windows Server 2012R2 template.)
— You can check if TLS1.0 is disabled and enable it using IISCrypto Tool.
answered Oct 19, 2018 at 5:34
I realise this is an old post, but I recently struck this issue as I needed to install 2016 for vendor compatibility.
In my case the issue was the service accounts being used.
Solution was to install using the default NT Service virtual accounts then change to domain accounts post install (we were actually using group managed service accounts)
answered Mar 29 at 22:36
Hi everybody!
OS: Windows 7 Enterprise, 32-bit
I’m having a lot of trouble installing the Service Pack 3 update for SQL Server 2012. When done through Windows Update, it fails with the error code 84BB0001.
I then tried installing the update manually and get the error:
Attempted to perform an unauthorized operation.
Error code 0x84BB0001.
I’ve tried uninstalling everything related to SQL Server, and now I cannot even install it again without the same error above.
Here is a part of the log from the installation:
(01) 2016-01-27 12:49:11 Slp: Sco: Attempting to open registry subkey {C1E2ED51-6345-6C38-9F8E-0E3F8FB11FF6} (01) 2016-01-27 12:49:11 Slp: Sco: Attempting to get registry value SQLProductPatchFamilyCode (01) 2016-01-27 12:49:11 Slp: Sco: Attempting to get registry value ProductId (01) 2016-01-27 12:49:11 Slp: Sco: Attempting to open registry subkey {C25215FC-5900-48B0-B93C-8D3379027312} (01) 2016-01-27 12:49:11 Slp: Sco: Attempting to get registry value SQLProductPatchFamilyCode (01) 2016-01-27 12:49:11 Slp: Sco: Attempting to get registry value ProductId (01) 2016-01-27 12:49:11 Slp: Sco: Attempting to open registry subkey {C44506FC-B846-4782-AC2B-8C30236CE075} (01) 2016-01-27 12:49:11 Slp: Prompting user if they want to retry this action due to the following failure: (01) 2016-01-27 12:49:11 Slp: ---------------------------------------- (01) 2016-01-27 12:49:11 Slp: The following is an exception stack listing the exceptions in outermost to innermost order (01) 2016-01-27 12:49:11 Slp: Inner exceptions are being indented (01) 2016-01-27 12:49:11 Slp: (01) 2016-01-27 12:49:11 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException (01) 2016-01-27 12:49:11 Slp: Message: (01) 2016-01-27 12:49:11 Slp: Attempted to perform an unauthorized operation. (01) 2016-01-27 12:49:11 Slp: HResult : 0x84bb0001 (01) 2016-01-27 12:49:11 Slp: FacilityCode : 1211 (4bb) (01) 2016-01-27 12:49:11 Slp: ErrorCode : 1 (0001) (01) 2016-01-27 12:49:11 Slp: Data: (01) 2016-01-27 12:49:11 Slp: WatsonData = Uninstall@{C44506FC-B846-4782-AC2B-8C30236CE075} (01) 2016-01-27 12:49:11 Slp: DisableRetry = true (01) 2016-01-27 12:49:11 Slp: Inner exception type: System.UnauthorizedAccessException (01) 2016-01-27 12:49:11 Slp: Message: (01) 2016-01-27 12:49:11 Slp: Attempted to perform an unauthorized operation. (01) 2016-01-27 12:49:11 Slp: HResult : 0x80070005 (01) 2016-01-27 12:49:11 Slp: Stack: (01) 2016-01-27 12:49:11 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 12:49:11 Slp:
And one more log:
,
(01) 2016-01-27 13:14:34 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction" threw an exception during execution. (01) 2016-01-27 13:14:34 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Attempted to perform an unauthorized operation. ---> Microsoft.SqlServer.Configuration.Sco.ScoException: Attempted to perform an unauthorized operation. ---> System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:34 Slp: --- End of inner exception stack trace --- (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.ArpRegKey.CleanupPatchedProductRegistryInfo() (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) (01) 2016-01-27 13:14:34 Slp: --- End of inner exception stack trace --- (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue() (01) 2016-01-27 13:14:34 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution. (01) 2016-01-27 13:14:34 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Attempted to perform an unauthorized operation. ---> Microsoft.SqlServer.Configuration.Sco.ScoException: Attempted to perform an unauthorized operation. ---> System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:34 Slp: --- End of inner exception stack trace --- (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.ArpRegKey.CleanupPatchedProductRegistryInfo() (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) (01) 2016-01-27 13:14:34 Slp: --- End of inner exception stack trace --- (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue() (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream) (01) 2016-01-27 13:14:34 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream) (01) 2016-01-27 13:14:35 Slp: Received request to add the following file to Watson reporting: C:UsersdtoAppDataLocalTemptmp449E.tmp (01) 2016-01-27 13:14:35 Slp: The following is an exception stack listing the exceptions in outermost to innermost order (01) 2016-01-27 13:14:35 Slp: Inner exceptions are being indented (01) 2016-01-27 13:14:35 Slp: (01) 2016-01-27 13:14:35 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException (01) 2016-01-27 13:14:35 Slp: Message: (01) 2016-01-27 13:14:35 Slp: Attempted to perform an unauthorized operation. (01) 2016-01-27 13:14:35 Slp: HResult : 0x84bb0001 (01) 2016-01-27 13:14:35 Slp: FacilityCode : 1211 (4bb) (01) 2016-01-27 13:14:35 Slp: ErrorCode : 1 (0001) (01) 2016-01-27 13:14:35 Slp: Data: (01) 2016-01-27 13:14:35 Slp: WatsonData = Uninstall@{C44506FC-B846-4782-AC2B-8C30236CE075} (01) 2016-01-27 13:14:35 Slp: DisableRetry = true (01) 2016-01-27 13:14:35 Slp: HelpLink.EvtType = 0xEF814B06@0x92D13C14 (01) 2016-01-27 13:14:35 Slp: EMBResult = Cancel (01) 2016-01-27 13:14:35 Slp: Stack: (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess) (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.ArpRegKey.CleanupPatchedProductRegistryInfo() (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId) (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) (01) 2016-01-27 13:14:35 Slp: Inner exception type: System.UnauthorizedAccessException (01) 2016-01-27 13:14:35 Slp: Message: (01) 2016-01-27 13:14:35 Slp: Attempted to perform an unauthorized operation. (01) 2016-01-27 13:14:35 Slp: HResult : 0x80070005 (01) 2016-01-27 13:14:35 Slp: Stack: (01) 2016-01-27 13:14:35 Slp: at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess)
The error is happening to several users and I’m lost as to what is wrong.
I’ve made sure I’m admin on the computer, running the setup is admin. I’ve also created a local user account with admin priv. and the error still shows up.
Any ideas?
Troubleshooter note: SQL Installation fails with exitcode 0x84BB0001 on a ReFS formatted partition.
So I tried to install SQL the other day for a new ConfigMgr environment, but I kept getting an error during the first seconds of the installation with 0x84BB0001 as the exit code. With some quick investigation into the log files I found this
%Temp%SqlSetup_Local.log:
C:Program FilesMicrosoft SQL Server110Setup BootstrapLogSummary.txt:
Shows that the installation has difficulties installing on a ReFS formatted partition
Disk Manager Shows that D: is formatted with ReFS (I blame my PowerShell Script :)):
Now the quick and easy way of fixing this is to reformat the partition to NTFS. And this is what I did in this case. But Microsoft has introduced support for ReFS for various versions of SQL in Cumulative Updates but not for SQL 2012. “There are some features of NTFS that aren’t supported by ReFS, specifically named streams, object IDs, short names, compression, file-level encryption (EFS), user data transactions, sparse, hard-links, extended attributes, and quotas. SQL Server databases uses named streams and sparse files in several functions, for example DBCC CHECKDB. This means you should not use ReFS with SQL Server. Stick with NTFS. Ref; http://windowsitpro.com/sql-server-2012/using-refs-sql-server
FIX: “Requested value ReFS was not found” error when you install SQL Server 2014 on a local drive that is ReFS formatted: https://support.microsoft.com/en-us/kb/3017266
Changing it back to NTFS fixed to issue for me. 🙂 Happy troubleshooting!
Share This Story, Choose Your Platform!
Microsoft Enterprise Client Management Evangelist with: 10+ years experience within Microsoft System Management Solutions
Extensive experience across Private and Public Sector
Passion for Community Driven work, volunteering within Microsoft technology
Great belief that sharing experience within fellow peers is key to creating a sustainable society
Strong commitment to System Center User Group Norway as co-founder and current leader
I am a technology enthusiast working as a consultant for the consultant company CTGlobal. I have always been passionate about IT and have the last 10 + years worked with Management and Automation within Microsoft technology. Back in 2005/6 I started working with System Management Server (SMS) 2003 and have been working with Enterprise Client Management ever since, where i today focus on helping customers design and implement solutions based on System Center Configuration Manager and/or Enterprise Mobility Suite from Microsoft. Other parts of my work consists of speaking and presenting at different events and seminars, doing research and blog about solutions I find and products I work with. I truly believe in a strong community where knowledge and know-how is essential. Creating creative arenas where it is possible for peers to spread the word about new technologies and solutions is key and as an act on this I co-founded System Center User Group Norway (www.scug.no). SCUG is an initiative where we discuss, preach and present new technologies and solutions in the System Center Space from Microsoft. This is a free arena for everybody to join that is interested in/or enthusiastic about Microsoft Cloud Platform (Enterprise Client Management or Cloud and Datacenter).
Specialties:
System Center Configuration Manager (SCCM2007-SCCM2012), Enterprise Mobility and Intune, Windows and Windows server deployment.
Beslægtede indlæg
Page load link