Программа установки sql server обнаружила следующую ошибку 0x84b10001
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Install SQL 2012 Developer Edition fails with 0x84B10001. Unable to load one or more of the requested types
Question
I m tring to install SQL 2012 Developer edition on m dev laptop that is already running SQL 2008 R2 Developer
When I run the setup on the dvd I get the error 0x84B10001. Unable to load one or more of the requested types
Answers
Seems like media corruption issue,
1-try re-download setup media
2-copy to local drive then launch setup
FAQ
----
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
This can be beneficial to other community members reading the thread.
All replies
Please check these workarounds:
Could you please share the sql setup log (c:\program files\microsoft sql server\110\setup bootstrap\log)?
Hope, this may help :)
Seems like media corruption issue,
1-try re-download setup media
2-copy to local drive then launch setup
FAQ
----
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
This can be beneficial to other community members reading the thread.
Which file in particular as there are quite a few. I assume you are refering to the Detail_LandingPage.txt file.
Again this file is quite large, so posting it here will be messy
The extract for the error in the file is;
as there is no way to upload the whole file here hope this except helps
I have a 2nd Install but it is key based not the same as the MSDN version. I was hopping to avoid using the key based one.
But ill give that a run and see if it is just the media that is corrupt
The 2nd Run installed so it seems to be a corrupt media issue
Thanks fro the help guys
I also faced the same issue while installing SQL server 2014 Enterprise edition. This error is coming due to file missing.
So follow the below step to get it done.
1- First of all uninstall each and every setup of of SQL server if you have installed earlier.
2-Now delete all the files of SQL from Program files folder.
3-Now if you have downloaded the SQL server as ISO image file then unzip directly in the same folder.(Do not use extract file, use extract here option while extracting the ISO image file.
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.
Проблемы
Индекс (Отсчитываемый от нуля) должен быть больше или равен нулю и меньше, чем размер списка аргументов. Код ошибки 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 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 More. Less
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.Microsoft distributes Microsoft SQL Server 2008 or SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 or SQL Server 2008 R2 fix release.
Symptoms
When you run SQL Server 2008 Setup or SQL Server 2008 R2, Setup may fail, and an unhandled exception occurs. Additionally, an error message that resembles the following is logged in the setup logs:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
Error code 0x84B10001.
Note This exception is not the original error message.
Cause
This issue occurs because of an error in the SQL Server 2008 or SQL Server 2008 R2 Setup program.
There are many possible scenarios that may initiate this issue. For example, a failure of a previous installation of SQL server may corrupt the registry, and this registry corruption may initiate this issue.
Resolution
Cumulative update information
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2438347 Cumulative Update package 5 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 10 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2279604 Cumulative update package 10 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254 Cumulative update 1 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Even the SQL 2014 System Configuration Checker crashes with the same exception. How am I supposed to make sense of the Process Monitor output from the SQL Team's installer? There are THOUSANDS of non-success results.
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\*.xml
I saw that one of the last things ScenarioEngine.exe writes to for logging is C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Detail.txt
These are all the XML files:
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\InputSettings_ChainerSettings_SlpSettings.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\InputSettings_FeatureSpecific_SlpInputSettings.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\InputSettings_RsDumper_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\Package.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\Product.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_AgentScript_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Agent_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Agent_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_AsDumper_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_AsInstanceId_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ASSIP_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_AS_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_AS_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterDisk_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterDisk_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterGroup_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterGroup_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterIPAddresses_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterIPAddresses_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterNodesStatus_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterNode_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ClusterNode_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_DReplayClient_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_DReplayController_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_FailOverClusterName_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_FailoverClusterName_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Fulltext_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Fulltext_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ManagementToolsAdvanced_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ManagementToolsAdvanced_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ManagementTools_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_ManagementTools_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Repl_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Repl_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_RsInstanceId_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Sku_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Sku_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SlpDumper_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Slp_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_Slp_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SniServer_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SniServer_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlBrowserStopService_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlBrowser_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlBrowser_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlEngineDumper_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlEngine_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlEngine_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlInstanceId_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlLegacyDiscovery_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlLegacyDiscovery_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlPowershell_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlPowershell_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlRSSHP_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlRSSHP_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlRS_DBPrivate.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlRS_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SqlRS_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SQLServerSCP_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SSIS_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SSIS_Public.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_SSIS_VSTA_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\ProductSettings_XTP_Private.xml
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Datastore\SLP_Actions_PersistedActionData.xml
The SQL installers are obviously generating these XML files, which have some sort of error in them. Then it exceptions when it tries to read them. It would be helpful to figure out which XML file and what node is causing the problem. I'm pretty sure the SQL Team could figure that out pretty quickly and easily by installing MSDE and then running the System Configuration Checker with a debugger. It crashes in seconds.
Here's the full Detail.txt:
(01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server 2014@RTM@
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : System.Xml.XmlTextReaderImpl.Throw
(01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-07-02 10:53:08 Slp:
Final Parameter Values
(01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server 2014@RTM@
(01) 2014-07-02 10:53:08 Slp: Parameter 1 : 0xDBE3EAAC
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : 0x066FCAFD
(01) 2014-07-02 10:53:08 Slp: Parameter 3 : 0xDF039760@1201@1
(01) 2014-07-02 10:53:08 Slp: Parameter 4 : 0x5539C151
(01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:10 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:10 Slp: Watson bucket for exception based failure has been created
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2014-07-02 10:53:10 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\120\EnableErrorReporting=.
(01) 2014-07-02 10:53:10 Slp: WER: Application level consent value '' was mapped to consent status 'WerConsentNotAsked'
(01) 2014-07-02 10:53:12 Slp: WER: Result of the submission:: 'WerReportCancelled'
(01) 2014-07-02 10:53:12 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: Error result: -2068774911
(01) 2014-07-02 10:53:12 Slp: Result facility code: 1201
(01) 2014-07-02 10:53:12 Slp: Result error code: 1
(01) 2014-07-02 10:53:12 Slp: SQM Service: Sqm does not have active session.
Приносим извинения. Запрошенное содержимое было удалено. Вы будете автоматически перенаправлены через 1 секунду.
Спрашивающий
Вопрос
in the sql server installation center I click on "new sql server stand alone installation. " and get this error message.
thank you for your help
- Изменено Samuel Lester - MSFT Microsoft employee 24 августа 2013 г. 11:23 Cleaned up format
Все ответы
Hi, can you try to unpack the Express package and run setup from the command line? This should get around the issue. To do so,
- Uninstall SQL Server setup package from add/remove programs
- Unpack the Express package to a local folder and run setup as admin. To do so, run /x:"c:\SQLExpressUnpacked"
- Launch setup.exe from the command line from c:\SQLExpressUnpacked using "setup.exe /action=install"
Thanks,
Sam Lester (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.
- Предложено в качестве ответа Ahmed Ibrahim - MSFT Microsoft employee 16 сентября 2013 г. 18:48
thank you for yor reply!
there is no sql setup packge or anything like that on the add/remove programs.
beside that I don't understand the other two bullets below
No problem. SQL Server Express edition ships as a downloadable .exe file which unpacks and runs setup.exe when you launch it. We're going to "unpack" the shipped .exe to access the folder structure directly, then run the setup.exe file from inside. To do so:
Step 1: uninstall any existing SQL Server Express bits (not needed since you don't have any in A/R Programs)
Step 2: Depending on your package that you downloaded (32-bit, 64-bit, etc.), you'll run the following from the command line (run as administrator).
SQLEXPR_x64_ENU.exe /x:"c:\SQLExpressUnpacked" (where c:\SQLExpressUnpacked is a folder that you've created to put the temporary install files)
Step 3: From the cmd prompt, navigate to c:\SQLExpressUnpacked\ and run " setup.exe /action=install"
This will launch SQL Server Express setup directly and should get you around the issue.
Thanks,
Sam Lester (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.
Читайте также: