Skip to content
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 Files\Microsoft SQL Server\110\Setup Bootstrap\Log\Summary.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
Generic Answer
This answer applies to all installation issues with SQL Server. It is a generic answer describing the steps required to analyse further details.
SQL Server Setup Routine Logging
When you installed SQL Server 2019 a detailed (very verbose) setup log was created in a sub-directory like this:
C:\Program Files\Microsoft SQL Server\VVV\Setup Bootstrap\Log\YYYYMMDD_HHMMSS\Detail.txt
VVV= SQL Server Version- 100 = SQL Server 2008 / 2008 R2
- 110 = SQL Server 2012 / 2012 R2
- 120 = SQL Server 2014
- 130 = SQL Server 2016
- 140 = SQL Server 2017
- 150 = SQL Server 2019
YYYYMMDD= Date the installation occurred- e.g.
20200727
- e.g.
HHMMSS= Time the installation occurred- e.g.
110523
- e.g.
An actual path would be:
C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20200727_110523\Detail.txt
^ ^ ^
| | |
SQL Server 2019 ----+ | |
July 27th, 2020 ------------------------------+ |
11.05am (23 seconds) ---------------------------------------+
Detail. txt
The Detail.txt will contain a detailed description at or around the time of failure.
Example Failure / Error / Exception
A section where a failure occurs will look similar to this:
(01) 2020-06-17 13:11:20 Slp: ---------------------------------------------------------------------- (01) 2020-06-17 13:11:20 Slp: Running Action: ProcessUpdateParametersAction (01) 2020-06-17 13:11:20 Slp: (01) 2020-06-17 13:11:20 Slp: Product Update Status: (01) 2020-06-17 13:11:20 Slp: User selected not to include product updates. (01) 2020-06-17 13:11:20 Slp: Error message: (01) 2020-06-17 13:11:20 Slp: The following is an exception stack listing the exceptions in outermost to innermost order (01) 2020-06-17 13:11:20 Slp: Inner exceptions are being indented (01) 2020-06-17 13:11:20 Slp: (01) 2020-06-17 13:11:20 Slp: Exception type: Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSearchException (01) 2020-06-17 13:11:20 Slp: Message: (01) 2020-06-17 13:11:20 Slp: SQL Server setup failed to search for product updates. This may indicate that the Windows Update service does not have online access to the Microsoft Update server or Windows Server Update Services. (01) 2020-06-17 13:11:20 Slp: HResult : 0x85190003 (01) 2020-06-17 13:11:20 Slp: FacilityCode : 1305 (519) (01) 2020-06-17 13:11:20 Slp: ErrorCode : 3 (0003) (01) 2020-06-17 13:11:20 Slp: Data: (01) 2020-06-17 13:11:20 Slp: WatsonData = Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSearchException@3 (01) 2020-06-17 13:11:20 Slp: Stack: (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSearchUtility.TrySearch(String serviceId, String query) (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSearchEngine.Search(String serviceId, String query) (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSetupSearchEngine.SearchUpdates() (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.SearchUpdatesAction.ExecuteAction(String actionId) (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b() (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate) (01) 2020-06-17 13:11:20 Slp: Inner exception type: Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaUpdateSearchException (01) 2020-06-17 13:11:20 Slp: Message: (01) 2020-06-17 13:11:20 Slp: Failed to search for updates with query 'CategoryIDs contains '6F210755-A742-449E-A57D-E459E20596C8''. Error: Ausnahme von HRESULT: 0x80240438 (01) 2020-06-17 13:11:20 Slp: HResult : 0x85170004 (01) 2020-06-17 13:11:20 Slp: FacilityCode : 1303 (517) (01) 2020-06-17 13:11:20 Slp: ErrorCode : 4 (0004) (01) 2020-06-17 13:11:20 Slp: Data: (01) 2020-06-17 13:11:20 Slp: Query = CategoryIDs contains '6F210755-A742-449E-A57D-E459E20596C8' (01) 2020-06-17 13:11:20 Slp: ErrorMessage = Ausnahme von HRESULT: 0x80240438 (01) 2020-06-17 13:11:20 Slp: WatsonData = Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaUpdateSearchException@4 (01) 2020-06-17 13:11:20 Slp: Stack: (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaUpdateSearcher.Search(Int32 timeout, String criteria) (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSearchUtility.Search(String serviceId, String query) (01) 2020-06-17 13:11:20 Slp: Inner exception type: System.Runtime.InteropServices.COMException (01) 2020-06-17 13:11:20 Slp: Message: (01) 2020-06-17 13:11:20 Slp: Ausnahme von HRESULT: 0x80240438 (01) 2020-06-17 13:11:20 Slp: HResult : 0x80240438 (01) 2020-06-17 13:11:20 Slp: Stack: (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Interop.WUApiLib.IUpdateSearcher.EndSearch(ISearchJob searchJob) (01) 2020-06-17 13:11:20 Slp: at Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaUpdateSearcher.Search(Int32 timeout, String criteria) (01) 2020-06-17 13:11:20 Slp: (01) 2020-06-17 13:11:20 Slp: Completed Action: ProcessUpdateParametersAction, returned True (01) 2020-06-17 13:11:20 Slp: Completed Action: ExecuteDownloadSetupUpdatesWorkflow, returned True (01) 2020-06-17 13:11:20 Slp: Completed Action: ExecuteOuterSetupStartUI, returned True (01) 2020-06-17 13:11:20 Slp: ----------------------------------------------------------------------
In this case, the error that occurred had no impact on the installation as the availability of the online update check is not a prerequisite.
Finding the Error Code
In your case, you should be able to find the error code 0x84BB0001 by opening the Detail.txt installation log file in an editor of your choice and searching for the code.
Depending on what you find, you will have to:
- Grant permissions to registry
- Remove components
- Install certain components
- ….
Educated Guess to your specific issue
As you pointed out in the comments, you already have Visual Studio installed. This has been known to cause issues during the installation of SQL Server xxxx depending on the version used.
Microsoft Visual C++ 20xx Redistributable (x86) and Microsoft Visual C++ 20xx Redistributable (x64) are also known to cause issues, when installing a lower version of SQL Server.
E.g. installing SQL Server 2016 on a Windows Server 2016 where Microsoft Visual C++ 2017 Redistributable (x86) has been installed will halt the installation.
Possible Solution(s)
- De-install Visual Studio after saving your settings.
- De-install any Visual C++ 20xx Redistributable that has a higher version than the SQL Server Version you are installing
- De-install the Microsoft SQL Server 2019 (64-bit) setup program before you try a re-install.
- Remove From My Forums
-
Question
-
-
Thursday, December 13, 2012 9:30 PM
setup (From:Getting started with SQL Server)
-
Answers
-
- Marked as answer by
Tuesday, December 25, 2012 5:03 AM
- Marked as answer by
All replies
-
- Marked as answer by
Tuesday, December 25, 2012 5:03 AM
- Marked as answer by
-
Would you please upload SQL Server setup logs,
You can check-out below «FAQ» on how to locate and upload setup logs.
-
this problem is because you are trying to install any component of sql 2012 on a ReFS formatted drive
install on an NTFS drive or format the target drive to NTFS and all works fine.
Not sure if Microsoft is going to update the installer to support its own ReFS format. time will tell
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:a95a4ef80214055fe53dx64setup Installation edition: Express Product Update Status: None discovered. User Input Settings: ACTION: Install ADDCURRENTUSERASSQLADMIN: true AGTSVCACCOUNT: NT AUTHORITYNETWORK 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 FilesMicrosoft SQL Server INSTALLSHAREDWOWDIR: c:Program Files (x86)Microsoft SQL Server INSTALLSQLDATADIR: <empty> INSTANCEDIR: C:Program FilesMicrosoft SQL Server INSTANCEID: SQLEXPRESS INSTANCENAME: SQLEXPRESS ISSVCACCOUNT: NT AUTHORITYNetwork 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 ServiceMSSQL$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 FilesMicrosoft SQL Server110Setup BootstrapLog20140729_114734ConfigurationFile.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 FilesMicrosoft SQL Server110Setup BootstrapLog20140729_114734SystemConfigurationCheck_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
2 gold badges5 silver badges14 bronze badges
Have you tried deleting the contents in the folder?
installation again as a repair, hope this will work.
answered Jul 29, 2014 at 18:03
- Remove From My Forums
-
Question
-
-
Thursday, December 13, 2012 9:30 PM
setup (From:Getting started with SQL Server)
-
Answers
-
- Marked as answer by
Tuesday, December 25, 2012 5:03 AM
- Marked as answer by
All replies
-
- Marked as answer by
Tuesday, December 25, 2012 5:03 AM
- Marked as answer by
-
Would you please upload SQL Server setup logs,
You can check-out below «FAQ» on how to locate and upload setup logs.
-
this problem is because you are trying to install any component of sql 2012 on a ReFS formatted drive
install on an NTFS drive or format the target drive to NTFS and all works fine.
Not sure if Microsoft is going to update the installer to support its own ReFS format. time will tell
- Remove From My Forums
-
Question
-
-
Thursday, December 13, 2012 9:30 PM
setup (From:Getting started with SQL Server)
-
Answers
-
- Marked as answer by
Tuesday, December 25, 2012 5:03 AM
- Marked as answer by
All replies
-
- Marked as answer by
Tuesday, December 25, 2012 5:03 AM
- Marked as answer by
-
Would you please upload SQL Server setup logs,
You can check-out below «FAQ» on how to locate and upload setup logs.
-
this problem is because you are trying to install any component of sql 2012 on a ReFS formatted drive
install on an NTFS drive or format the target drive to NTFS and all works fine.
Not sure if Microsoft is going to update the installer to support its own ReFS format. time will tell
На этой неделе мы обсудим одно из самых распространенных сообщений об ошибках, которые мы получаем при установке 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. Но я не уверен, сколько случаев это действительно решило проблему, поэтому я упомянул первый метод.
Эти методы должны помочь вам в устранении этой ошибки.
Как решить | Исправить сообщения об ошибках установки SQL Server 2008?
Я пытаюсь установить выпуск SQL Server 2012 Developer на свой ноутбук, на котором он работал раньше. На моем ноутбуке было мало места на диске, и мне пришлось удалить его ранее. Он больше не работает и в последний момент не работает, что приводит к несанкционированной ошибке. Я использовал монитор процесса, чтобы посмотреть на проблему, и вижу, что он пытается получить доступ к разделу реестра. «HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services FltMgr» но получает в доступе отказано. Я пробовал несколько попыток предоставить всем полный доступ к этому разделу реестра, но это не сработало. Я прочитал несколько статей, прежде чем размещать его здесь, и поэтому, пожалуйста, не думайте, что я пришел сюда, чтобы быстро получить ответ без надлежащего расследования, хотя я бы хотел, чтобы его быстро разобрали. Есть идеи, пожалуйста?
ОС: Windows 10 Home Edition
Хотя установка не удалась, я вижу службу Windows «SQL Server (MSSQLSERVER)», которая не запускается. В средстве просмотра событий отображается следующая ошибка. initerrlog: не удалось открыть файл журнала ошибок ». Ошибка операционной системы = 3 (система не может найти указанный путь.).
Overall summary: Final result: Failed: see details below Exit code (Decimal): -2068119551 Start time: 2016-11-14 14:55:15 End time: 2016-11-14 15:24: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. Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Machine Properties: Machine name: DESKTOP-9VOUAM4 Machine processor count: 8 OS version: Future Windows Version 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 Package properties: Description: Microsoft SQL Server 2012 ProductName: SQL Server 2012 Type: RTM Version: 11 Installation location: D:sqlserverx64setup Installation edition: Developer Slipstream: True SP Level 2 Product Update Status: Success: KB 2958429 Product Updates Selected for Installation: Title: Service Pack 2 Knowledge Based Article: KB 2958429 Version: 11.2.5058.0 Architecture: x64 Language: 1033 Update Source: Slipstream User Input Settings: ACTION: Install ADDCURRENTUSERASSQLADMIN: false AGTSVCACCOUNT: NT ServiceSQLSERVERAGENT AGTSVCPASSWORD: ***** AGTSVCSTARTUPTYPE: Manual ASBACKUPDIR: Backup ASCOLLATION: Latin1_General_CI_AS ASCONFIGDIR: Config ASDATADIR: Data ASLOGDIR: Log ASPROVIDERMSOLAP: 1 ASSERVERMODE: MULTIDIMENSIONAL ASSVCACCOUNT: ASSVCPASSWORD: ASSVCSTARTUPTYPE: Automatic ASSYSADMINACCOUNTS: ASTEMPDIR: Temp BROWSERSVCSTARTUPTYPE: Disabled CLTCTLRNAME: CLTRESULTDIR: CLTSTARTUPTYPE: 0 CLTSVCACCOUNT: CLTSVCPASSWORD: CLTWORKINGDIR: COMMFABRICENCRYPTION: 0 COMMFABRICNETWORKLEVEL: 0 COMMFABRICPORT: 0 CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20161114_145357ConfigurationFile.ini CTLRSTARTUPTYPE: 0 CTLRSVCACCOUNT: CTLRSVCPASSWORD: CTLRUSERS: ENABLERANU: false ENU: true ERRORREPORTING: false FEATURES: SQLENGINE, REPLICATION, SSMS, ADV_SSMS FILESTREAMLEVEL: 0 FILESTREAMSHARENAME: FTSVCACCOUNT: FTSVCPASSWORD: HELP: false IACCEPTSQLSERVERLICENSETERMS: true INDICATEPROGRESS: false INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server INSTALLSQLDATADIR: INSTANCEDIR: d:Program FilesMicrosoft SQL Server INSTANCEID: MSSQLSERVER INSTANCENAME: MSSQLSERVER ISSVCACCOUNT: NT AUTHORITYNetwork Service ISSVCPASSWORD: ISSVCSTARTUPTYPE: Automatic MATRIXCMBRICKCOMMPORT: 0 MATRIXCMSERVERNAME: MATRIXNAME: NPENABLED: 0 PID: ***** QUIET: false QUIETSIMPLE: false ROLE: RSINSTALLMODE: DefaultNativeMode RSSHPINSTALLMODE: DefaultSharePointMode RSSVCACCOUNT: RSSVCPASSWORD: RSSVCSTARTUPTYPE: Automatic SAPWD: ***** SECURITYMODE: SQL SQLBACKUPDIR: SQLCOLLATION: Latin1_General_CI_AS SQLSVCACCOUNT: NT ServiceMSSQLSERVER SQLSVCPASSWORD: SQLSVCSTARTUPTYPE: Automatic SQLSYSADMINACCOUNTS: BUILTINAdministrators SQLTEMPDBDIR: SQLTEMPDBLOGDIR: SQLUSERDBDIR: SQLUSERDBLOGDIR: SQMREPORTING: false TCPENABLED: 0 UIMODE: Normal UpdateEnabled: true UpdateSource: Slipstream X86: false Configuration file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20161114_145357ConfigurationFile.ini Detailed results: Feature: Management Tools - Complete Status: Passed Feature: Management Tools - Basic Status: Passed 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: Attempted to perform an unauthorized operation. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x48BB60BC%400xBB814387&EvtType=0x48BB60BC%400xBB814387 Feature: SQL Server Replication Status: Failed: see logs for details Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. 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: Attempted to perform an unauthorized operation. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x48BB60BC%400xBB814387&EvtType=0x48BB60BC%400xBB814387 Feature: SQL Browser Status: Passed Feature: SQL Writer Status: Passed Rules with failures: Global rules: Scenario specific rules: Rules report file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20161114_145357SystemConfigurationCheck_Report.htm Несколько моментов, которые следует запомнить, если вы столкнетесь с подобной проблемой: 1. Если вы увидите «несанкционированную операцию» или аналогичную ошибку во время установки, запустите инструмент ProcessMonitor (Sysinternal / Microsoft) и проверьте трассировку после фильтрации для Процесс установки SQL Server Engine. Несанкционированная операция при установке SQL Server 2012 Express / Developer 2. Я видел, что учетная запись службы, которую использует «агент SQL Server» и «ядро базы данных SQL Server», вероятно, создается на лету, и у нее может не быть достаточных прав доступа для реестр. Я не очень уверен в этом, однако стоит взглянуть на изменение его на другую учетную запись (скажем, LocalService), если ничего не помогает.
- В среде разработки вы можете попробовать дать полное разрешение соответствующему разделу реестра. В моем случае он принадлежал учетной записи «Система» и не мог легко предоставлять разрешения. Я перезагрузил Windows 10 в безопасном режиме и дал необходимые разрешения, а затем перезагрузился в нормальный режим.
Разрешения реестра, учетные записи пользователей