Hi Vatseq,
Could you please share the full error message to us for analysis? You can get it from Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\****_****\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_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\120\
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_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
—HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
4. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services 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_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\130
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:\x64\setup\
Installation edition: Standard
Product Update Status:
User selected not to include product updates.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$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 Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161031_153925\ConfigurationFile.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 Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQL2016
INSTANCENAME: SQL
ISSVCACCOUNT: NT AUTHORITY\Network 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 Service\MSSQL$SQL
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: FUALSNA\administrator
SQLTELSVCACCT: NT Service\SQLTELEMETRY$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 Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161031_153925\ConfigurationFile.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 Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161031_153925\SystemConfigurationCheck_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
42.7k8 gold badges45 silver badges64 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
- Remove From My Forums
-
Вопрос
-
Attempting to install fails at Core
(01) 2017-11-14 23:52:58 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2017-11-14 23:52:58 Slp: Message:
(01) 2017-11-14 23:52:58 Slp: Attempted to perform an unauthorized operation.
(01) 2017-11-14 23:52:58 Slp: HResult : 0x84bb0001
(01) 2017-11-14 23:52:58 Slp: FacilityCode : 1211 (4bb)
(01) 2017-11-14 23:52:58 Slp: ErrorCode : 1 (0001)
(01) 2017-11-14 23:52:58 Slp: Data:
(01) 2017-11-14 23:52:58 Slp: WatsonData = HKEY_LOCAL_MACHINE@SYSTEM\CurrentControlSet\Services\FltMgr
(01) 2017-11-14 23:52:58 Slp: DisableRetry = true
(01) 2017-11-14 23:52:58 Slp: SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2017-11-14 23:52:58 Slp: WatsonConfigActionData = INSTALL@CONFIGNONRC@SQL_ENGINE_CORE_INST
(01) 2017-11-14 23:52:58 Slp: WatsonExceptionFeatureIdsActionData = System.String[]PC set as Workgroup and I am running as Administrator. Any ideas on avoiding this permission issue.
Ответы
-
Hi Jeff,
If that still fails, I would suggest opening a case with
Microsoft Customer Support Services (CSS), so that a dedicated Support Professional can assist you in a more efficient manner.If you have any other questions, please let me know.
Regards,
Hannah
MSDN Community Support
Please remember to click «Mark as Answer» the responses that resolved your issue, and to click «Unmark as Answer» if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to
MSDN Support, feel free to contact MSDNFSF@microsoft.com.-
Помечено в качестве ответа
23 ноября 2017 г. 15:02
-
Помечено в качестве ответа
I am receiving the 0x84BB0001 Error after attempting to install a new instance of SQL Server 2012. This is happening after an uninstall of a previous version of SQL Server 2012. I have pasted the log file below. Any help is greatly appreciated.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: The system cannot find the file specified.
Start time: 2014-07-29 11:59:09
End time: 2014-07-29 12:09:12
Requested action: Install
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0x37D77D9E%400xDC80C325&EvtType=0x37D77D9E%400xDC80C325
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for LocalDB: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
Machine name: MAPCOM444
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
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
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: c:\a95a4ef80214055fe53d\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
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>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, SSMS, SNAC_SDK, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: c:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140729_114734\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: LocalDB
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Writer
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140729_114734\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
Message:
The system cannot find the file specified.
HResult : 0x84bb0001
FacilityCode : 1211 (4bb)
ErrorCode : 1 (0001)
Data:
WatsonData = SQLBrowser
DisableRetry = true
HelpLink.EvtType = 0x37D77D9E@0xDC80C325
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.Sco.Service.GetStartAccount()
at Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPublicConfig.CalculateUserNamePassword()
at Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPublicConfig.Calculate()
at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CalculateSettings(IEnumerable`1 settingIds)
at Microsoft.SqlServer.Configuration.Settings.Calculate()
at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.LoadData()
at Microsoft.SqlServer.Configuration.InstallWizard.ServicesController.LoadData()
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.PageEntered(PageChangeReason reason)
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardTabbedPageHost.PageEntered(PageChangeReason reason)
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.OnPageNavigationRequest(PageChangeReason reason)
at Microsoft.SqlServer.Configuration.InstallWizard.DiskUsageController.LoadData()
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.PageEntered(PageChangeReason reason)
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Inner exception type: System.ComponentModel.Win32Exception
Message:
The system cannot find the file specified.
HResult : 0x80004005
Error : 2
Stack:
at Microsoft.SqlServer.Configuration.Sco.Service.QueryServiceConfig()
at Microsoft.SqlServer.Configuration.Sco.Service.GetStartAccount()
asked Jul 29, 2014 at 17:20
I was able to get past the error by changing the instance name. The old instance name from the uninstalled version was SQLEXPRESS, I changed this to SQLEXPRESS2012 and the installation proceeded.
answered Jul 29, 2014 at 17:53
ghoston3rdghoston3rd
1292 gold badges5 silver badges14 bronze badges
Have you tried deleting the contents in the folder?
C:/Users/[UserName]/AppData/Local/Microsoft_Corporation.
installation again as a repair, hope this will work.
answered Jul 29, 2014 at 18:03
1
Содержание
- KB2379466-FIX: «0x84B10001», ошибка при установке SQL Server 2008 или SQL Server 2008 R2, и при запуске SQL Server 2008 или SQL Server 2008 R2 возникает неуправляемое исключение
- Проблемы
- Причина
- Решение
- Сведения о накопительном пакете обновления
- SQL Server 2008 R2
- SQL Server 2008 с пакетом обновления 1
- SQL Server 2008 с пакетом обновления 2
- Статус
- Ссылки
- Sql server код ошибки 0x84bb0001
- Answered by:
- Question
- Answers
- All replies
- question
- Getting 0x84BB0001 when installing SQL Server 2019 Developer Edition with only Database Engine services
- 2 Answers
- question
- SQL Server 2019 Installation Fails due to 0x84BB0001 error code
- 2 Answers
KB2379466-FIX: «0x84B10001», ошибка при установке SQL Server 2008 или SQL Server 2008 R2, и при запуске SQL Server 2008 или SQL Server 2008 R2 возникает неуправляемое исключение
Корпорация Майкрософт распространяет исправления 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 Стандартные термины, используемые при описании обновлений программных продуктов Майкрософт
Источник
Sql server код ошибки 0x84bb0001
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
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:
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:
And one more log:
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.
Answers
I solved it by disabling McAfee. It seems that even the enterprise version is very agressive.
Grant full permissions to below registry keys to the setup account and SQL Service account:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server110
Follow the instructions provided on the following thread:
Run SQL Server setup with the «Run as Administrator» option.
Hope this helps.
- Edited by Alberto Morillo MVP Wednesday, January 27, 2016 3:30 PM
Thanks for the reply.
Unfortuantly it doesn’t work, I still get the same error message.
I also tried the things Imaeb mentioned, but nothing seems to work.
Any other ideas? 🙂
I solved it by disabling McAfee. It seems that even the enterprise version is very agressive.
For me it was enough just to disable the on-access scanner and access protection.. But you have to watch it, because it tries to reenable itself after some time.
I am wondering though if McAfee is at fault here, because the error only happens because the SQL Server installation tries to access registry keys related to uninstalling McAfee.
I found out by searching for the registry key mentioned in the log.
McAfee of course tries to prohibit uninstalling by denying access to these registry keys, which the SQL Server installer should just ignore instead of stopping all together.
I don’t quite understand why the SQL Server installer is looking at these registry keys in the first place — and why it’s so important to be able to access them (failure to access = failure to install).
Источник
question
Getting 0x84BB0001 when installing SQL Server 2019 Developer Edition with only Database Engine services
I’m trying to install SQL Server 2019 Developer Edition. I don’t need anything but the core so all I selected for the installation is the Database Engine services.
However, that one keeps failing to install and I get the error code 0x84BB0001 as result.
I installed it with admin privileges so I’m not sure what it could mean by with the error description («Attempted to perform an unauthorized operation.»).
Never had any SQL Server installed before, so there can’t be any old leftovers either. Would be the first instance I tried installing as well.
Would appreciate some help here. Thanks in advance.
In C:Program FilesMicrosoft SQL Server150Setup BootstrapLog there is one folder per installation attempt. In the most recent attempt, find the files Summary.txt and Detail.txt and attach them here.
What anti-malware software are you running?
I attached both files in the question. My AV is BullGuard.
2 Answers
Thanks for the files, but I don’t need to look at them. BullGuard is a known troublemaker when it comes to SQL Server installs. I have helped people with this in the past, and I even tried testing installing SQL Server with BullGuard present.
You need to uninstall BullGuard to be able to install SQL Server. You can try just merely disable it, if you like, but that usually don’t help with troublesome anti-malware programs, because the issue is presumably with a filter driver. Once you have installed SQL Server, you can reinstall BullGuard if you like to keep it. I am not aware of any problems running SQL Server with BullGuard installed. (But I never came that far in my testing myself.)
Источник
question
SQL Server 2019 Installation Fails due to 0x84BB0001 error code
Multiple feature installations (e.g., Python, R, Database Engine Service and others) fail during SQL Server 2019 express with advanced service installation.
The summary reports (see attached) states the same error code and error descriptions for all failed features:
Component error code: 0x84BB0001
Error description: One or more command-line switches were invalid.
Things I’ve already tried:
— complete re-install of SQL server 2019 (incl. deleting all registry keys etc.)
— turning on .NET Framework 3.5
— installing SQL server as admin
— turning off the Firewall during installation
— installing latest .NET Framework 4.8
Can anyone please help with properly installing all required SQL server features?
Thanks in advance!
176433-summary-laptop-r51n9sev-20220221-114135.txt
2 Answers
Also I had once a problem (not sure if this one though ?) when installing from a long path such as C:UsersMyUserNameDownloadsen_sql_server_2019_express_with_advanced_services_x64_e2d9f596x64setup (maybe the setup creates a command with this kind of path one or two times and uses a buffer that is not long enough or whatever ?
Since then, I prefer to install from c:installsql or I mount the ISO and install from the driver letter.
extracting the directory path to c:installsql and installing the SQL server from there has worked. 🙂
Thank you so much for your help!
It seems that your computer has the residue of uninstallation. Have you ever had a failed installation before? If so, please uninstall it clearly and reinstall it.
Please follow the below steps to remove all components of previous installed SQL Server completely:
1. Remove all SQL Server components from ‘Programs and Features’
2. Backup the registry
3. Delete the following keys in regedit:
—HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
—HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServer
4. Go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall and delete all the sub-keys referencing SQL Server
5. Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices and delete all the keys referencing SQL Server
6. Reboot the machine
Download the SQL Server again, and mount the ISO file as a virtual drive.
In addition, please use an administrator account to reinstall SQL Server on your computer(Right click->run as administrator).
Here is the article which can give you some help: https://getanadmin.com/windowsserver/win2019/sql-server-2019-installation-step-by-step/
Of course, the installation process inside is for your reference.
You also need change the SQL Server service account and SQL Server Browser account to Local System on the Server Configuration page of SQL Server setup.
If the answer is the right solution, please click «Accept Answer» and kindly upvote it. If you have extra questions about this answer, please click «Comment».
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Источник
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?
На этой неделе мы обсудим одно из самых распространенных сообщений об ошибках, которые мы получаем при установке SQL Server 2008 R2 в системах Windows . Это пятая статья серии «Устранение неполадок SQL», которую мы начали несколько недель назад В последние пару недель мы обсуждали различные сообщения об ошибках при установке SQL. На этой неделе мы обсудим большинство распространенных ошибок; «Системе конфигурации не удалось инициализировать 0x84B10001».
Системе конфигурации не удалось инициализировать 0x84B10001
Когда я впервые получил эту ошибку, мне пришлось провести много исследований, чтобы выяснить причину. После долгих поисков выяснилось, что эта ошибка происходит из-за Microsoft .NET.
В папке C: Windows Microsoft.NET Framework64 v2.0.50727 CONFIG находится файл machine.config , вызывающий эту ошибку.
Файл Machine. config содержит параметры, которые применяются ко всему компьютеру. Этот файл находится в каталоге C: Windows Microsoft.NET Framework64 v2.0.50727 CONFIG . Machine.config содержит параметры конфигурации для привязки сборки на уровне машины, встроенных каналов удаленного взаимодействия и ASP.NET. Система конфигурации сначала просматривает файл конфигурации машины и другие разделы конфигурации, когда может позвонить разработчик. Этот файл содержит, помимо многих других элементов XML, элемент browserCaps . Внутри этого элемента находится ряд других элементов, которые определяют правила синтаксического анализа для различных пользовательских агентов и какие свойства поддерживает каждый из этих синтаксических анализаторов.
Чтобы исправить эту ошибку, мы должны изменить файл Machine.config. Нам нужно удалить раздел конфигурации, который содержит все элементы конфигурации Windows Communication Foundation (WCF) ServiceModel . Я все еще не понимаю, почему нам нужно удалить этот раздел, чтобы это сообщение об ошибке исчезло.
Есть два метода, которые вы можете попытаться решить эту проблему.
Метод первый
В этом методе мы изменим файл Machine.config.
- Перейдите в C: Windows Microsoft.NET Framework64 v2.0.50727 CONFIG .
- Найдите файл Machine.config и создайте копию этого файла в качестве резервной копии.
- Щелкните правой кнопкой мыши файл Machine.config и выберите команду «Изменить» (лучше всего использовать Notepad ++ для изменения этого файла).
- Найдите следующий раздел (найдите )
- Удалите всю конфигурацию, т. Е. С на
- Сохраните файл Machine.config .
Теперь попробуйте установить Microsoft SQL Server 2008 R2 и посмотреть, если вы получаете ту же ошибку.
Метод второй
В этом методе вы можете попытаться загрузить последний серверный пакет Microsoft SQL Server 2008 R2 и попытаться установить его. Потому что, по мнению Microsoft, эта ошибка исправлена в пакете обновления 1 (SP1) для Microsoft SQL Server 2008 R2. Но я не уверен, сколько случаев это действительно решило проблему, поэтому я упомянул первый метод.
Эти методы должны помочь вам в устранении этой ошибки.