SQL Server 2008 Enterprise SQL Server 2008 Developer SQL Server 2008 Standard SQL Server 2008 Standard Edition for Small Business SQL Server 2008 Workgroup SQL Server 2008 R2 Developer SQL Server 2008 R2 Enterprise SQL Server 2008 R2 Standard SQL Server 2008 R2 Standard Edition for Small Business SQL Server 2008 R2 Workgroup Еще…Меньше
Корпорация Майкрософт распространяет исправления Microsoft SQL Server 2008 в один файл для загрузки. Поскольку исправления являются кумулятивными, каждый новый выпуск содержит все исправления и исправления для системы безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008.Корпорация Майкрософт распространяет исправления Microsoft SQL Server 2008 или SQL Server 2008 R2 как один файл для загрузки. Поскольку исправления являются кумулятивными, каждый новый выпуск содержит все исправления и исправления для системы безопасности, которые были включены в исправленный выпуск SQL Server 2008 или SQL Server 2008 R2.
Проблемы
При запуске программы установки SQL Server 2008 или SQL Server 2008 R2 программа установки может завершить работу со сбоем и произойдет неуправляемое исключение. Кроме того, в журналах настройки регистрируются сообщения об ошибках, похожие на приведенные ниже.
Индекс (Отсчитываемый от нуля) должен быть больше или равен нулю и меньше, чем размер списка аргументов. Код ошибки 0x84B10001.
Примечание. Это исключение не является исходным сообщением об ошибке.
Причина
Эта проблема возникает из-за ошибки в программе установки SQL Server 2008 или SQL Server 2008 R2. Существует множество возможных сценариев, которые могут инициировать эту ошибку. Например, сбой в предыдущей установке SQL Server может повредить реестр, и это повреждение реестра может вызвать эту ошибку.
Решение
Сведения о накопительном пакете обновления
SQL Server 2008 R2
Исправление для этой проблемы впервые выпущено в накопительном обновлении 5. Для получения дополнительных сведений о том, как получить этот накопительный пакет обновления для SQL Server 2008 R2, щелкните следующий номер статьи базы знаний Майкрософт:
2438347 Накопительный пакет обновления 5 для SQL Server 2008 R2 Примечание. Поскольку сборки являются кумулятивными, каждый новый выпуск исправлений содержит все исправления и все исправления безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008 R2. Рекомендуется установить последнюю версию исправления, которая включает это исправление. Дополнительные сведения см. в следующей статье базы знаний Майкрософт:
981356 Сборки SQL Server 2008 R2, выпущенные после выпуска SQL Server 2008 R2
SQL Server 2008 с пакетом обновления 1
Исправление для этой проблемы впервые выпущено в накопительном обновлении 10 для SQL Server 2008 с пакетом обновления 1 (SP1). Чтобы получить дополнительные сведения об этом накопительном пакете обновления, щелкните следующий номер статьи базы знаний Майкрософт:
2279604 Накопительный пакет обновления 10 для SQL Server 2008 с пакетом обновления 1 (SP1)Примечание. Так как сборки являются кумулятивными, каждый новый выпуск исправлений содержит все исправления и все исправления безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008. Корпорация Microsoft рекомендует установить последнюю версию исправления, которая включает это исправление. Дополнительные сведения см. в следующей статье базы знаний Майкрософт:
970365 Сборки SQL Server 2008, выпущенные после выпуска пакета обновления 1 (SP1) для SQL Server 2008 Исправления Microsoft SQL Server 2008 создаются для конкретных пакетов обновления для SQL Server. Вы должны применить исправление для SQL Server 2008 с пакетом обновления 1 (SP1) к установке SQL Server 2008 с пакетом обновления 1. По умолчанию любое исправление, предоставленное в пакете обновления SQL Server, входит в следующий пакет обновления для SQL Server.
SQL Server 2008 с пакетом обновления 2
Исправление для этой проблемы впервые выпущено в накопительном обновлении 1 для SQL Server 2008 с пакетом обновления 2. Чтобы получить дополнительные сведения об этом накопительном пакете обновления, щелкните следующий номер статьи базы знаний Майкрософт:
2289254 Накопительное обновление 1 для SQL Server 2008 с пакетом обновления 2Примечание. Так как сборки являются кумулятивными, каждый новый выпуск исправлений содержит все исправления и все исправления безопасности, которые были включены в предыдущий выпуск исправлений для SQL Server 2008. Рекомендуется установить последнюю версию исправления, которая включает это исправление. Дополнительные сведения см. в следующей статье базы знаний Майкрософт:
2402659 Сборки SQL Server 2008, выпущенные после выпуска пакета обновления 2 (SP2) для SQL Server 2008
Статус
Корпорация Майкрософт подтверждает наличие этой проблемы в своих продуктах, которые перечислены в разделе «Применяется к».
Ссылки
Чтобы получить дополнительные сведения о модели добавочного обслуживания для SQL Server, щелкните следующий номер статьи базы знаний Майкрософт:
935897 Модель обслуживания изменений, используемая рабочей группой SQL Server, предоставляет модель ISM для распространения исправлений обнаруженных проблемЧтобы получить дополнительные сведения о схеме присвоения имен обновлениям SQL Server, щелкните следующий номер статьи базы знаний Майкрософт:
822499Новая схема присвоения имен пакетам обновлений программного обеспечения Microsoft SQL ServerЧтобы получить дополнительные сведения о терминологии обновления программного обеспечения, щелкните следующий номер статьи базы знаний Майкрософт:
824684 Стандартные термины, используемые при описании обновлений программных продуктов Майкрософт
Нужна дополнительная помощь?
Нужны дополнительные параметры?
Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.
В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.
I’m trying to install SQL Server Express with Service Pack 1 on my Win8 Pro (x64) development machine and I’m consistently getting an error 0x84b10001 when trying to install it:
Antivirus is disabled during the installation (done as Administrator) and I tried 2 versions of the SQL Server Express package and I’m getting the same issue with both.
I’m getting the same issue whether I’m trying the x86 or x64 packages.
I suspect that the issue comes from the fact that Visual Studio 2013 has already installed some SQL Server packages but I do not see any way to update and modify these to add the Management Studio for istance.
asked Feb 8, 2014 at 7:37
Renaud BompuisRenaud Bompuis
16.5k4 gold badges55 silver badges86 bronze badges
Create a new local user with administative rights and try the installation again. In my case it solves the problem with MSSQL 2008R2.
answered Jan 7, 2015 at 10:34
WaveWave
692 silver badges3 bronze badges
Create new user with administrative privileges and install using that user. It worked.
answered Feb 14, 2018 at 17:17
Remove folder:
C:Users[USER ID]AppDataLocalMicrosoft_Corporation
It worked for me.
answered May 13, 2015 at 16:37
satocsatoc
4414 silver badges7 bronze badges
In my case, it was because trying to install an x86 package on an x64 windows, installing x64 package worked for me.
answered Feb 23, 2017 at 3:41
Reza AbolfathiReza Abolfathi
3,0412 gold badges17 silver badges14 bronze badges
So i have been trying to install SQL Server 2012 Express edition But it give me an error code 0x84B10001 Error generating XML Document, This error pops up as it starts the process «ConfigEvent_SQL_WRITER_sqlwriter_Cpu64_Install_GetDefaultConfig_validation»
a few seconds into installation.
Going through many forums i haven’t found anything that helped me solve this,
Having Gone through numerous forums to try and solve this, i saw that a lot of people refereed to the to the summary log file to find the exact issue.
Below is the Summary for the latest log file.
I Hope this is enough information.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068774911
Exit facility code: 1201
Exit error code: 1
Exit message: There was an error generating the XML document.
Start time: 2017-04-25 08:00:21
End time: 2017-04-25 08:04:14
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=0xE0C083E6%400xB2215DAC&EvtType=0xE0C083E6%400xB2215DAC
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 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 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: DESKTOP-RAKCKMR
Machine processor count: 8
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United Kingdom)
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:cadbbb88a0c1ab687c313ex64setup
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: Automatic
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, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SHIPWEIGHT
INSTANCENAME: SHIPWEIGHT
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: Latin1_General_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$SHIPWEIGHT
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: SIGMAjoshua
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 BootstrapLog20170425_075926ConfigurationFile.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: 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: 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 BootstrapLog20170425_075926SystemConfigurationCheck_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.Chainer.Infrastructure.ChainerInfrastructureException
Message:
There was an error generating the XML document.
HResult : 0x84b10001
FacilityCode : 1201 (4b1)
ErrorCode : 1 (0001)
Data:
HelpLink.EvtType = 0xE0C083E6@0xB2215DAC
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.FlushCache(Boolean removeAllCachedObj)
at Microsoft.SqlServer.Configuration.SetupExtension.DatastoreCacheFeatureConfigEventHandler.InConfigurationActionExecutionEventHandler(Object sender, FeatureConfigScenarioEventArgs eventArgs)
at Microsoft.SqlServer.Chainer.Infrastructure.NotificationHandler.Invoke(Object notification, Object[] objectArray)
at Microsoft.SqlServer.Configuration.ConfigExtension.ConfigFeatureActionListener.InConfigurationActionExecutionEventHandler(ActionKey key, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Chainer.TimingConfigAction.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: System.InvalidOperationException
Message:
There was an error generating the XML document.
HResult : 0x80131509
Stack:
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
Inner exception type: System.Security.Cryptography.CryptographicException
Message:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.
HResult : 0x80090345
Stack:
at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
at Microsoft.SqlServer.Common.SqlSecureString.WriteXml(XmlWriter writer)
at System.Xml.Serialization.XmlSerializationWriter.WriteSerializable(IXmlSerializable serializable, String name, String ns, Boolean isNullable, Boolean wrapped)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write6_AgentConfigurationPublic(String n, String ns, AgentConfigurationPublic
o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write7_AgentConfigurationPublic(Object o)
-
Question
Answers
-
I finally got the SQL 2014 installer to work.
I did a search from Programs and Features until I found «Microsoft SQL Server Database Engine». For some reason it was not in the default list. Filtering for it with the search bar at the top right found it when I typed «engine».
After uninstalling MSDE and rebooting, the SQL 2014 installer worked.
/* Don Reynolds */
-
Marked as answer by
Don Reynolds
Thursday, August 14, 2014 1:45 PM
-
Marked as answer by
All replies
-
Hi,
So now do you want to install SQL server 2012 Sp2 or SQL server 2014 express ?
Did you followed Samuel Lester’s Suggestion in the Link you posted. SQL 2014 being new and 2000 being totally outdated its difficult to find system having both. It can be a compatibility issue. I don’t have both Versions so I cannot reproduce your
scenario.Do you require MSDE 2000 if not you can uninstall and try. But first refer to Samuels Suggestion
If you want to Install SP2 instead remove 2014 components from add remove program first and can you post Log file generated after failed installation of Service pack 2 .Location would be below
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
-
I am an MSDN Premium Subscriber. I want to install SQL Server 2014 Standard 64bit from the full DVD (ISO). Regardless of what I want to do, the 2012 and 2014 installer is broken. I’m not using Express, but others have experienced the same problem with Express
so I assume it is across all versions of the newer installers.I support all sorts of old technology, including VB6, older versions of Office, and older versions of SQL Server back to SQL 2000. I didn’t want to install MSDE, but I needed to in order to get some libraries and such that an old VB6 app was referencing.
I want to remove all traces of it if that is the potential problem. Obviously I can install MSDE again after the new installers run because I had no issue doing that on top of SQL Server 2012.
The problem is that there is no uninstaller for MSDE. I followed the steps to do it manually, which were written for Windows Server 2003. There were some registry key locations that didn’t exist. The MsiZap.exe is nearly impossible to find (luckily someone
had saved it and put it in a blog post).Considering these products are both SQL Server products, they could have built in a better error message to help pinpoint the problem and/or a way to cleanup older unneeded SQL installations.
/* Don Reynolds */
-
C:Program FilesMicrosoft SQL Server120Setup BootstrapLogSummary.txt
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068774911
Exit facility code: 1201
Exit error code: 1
Exit message: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
Start time: 2014-06-13 12:21:47
End time: 2014-06-13 12:22:19
Requested action: Install
Exception help link:http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x066FCAFD%400x5539C151&EvtType=0x066FCAFD%400x5539C151
Machine Properties:
Machine name: CES1358
Machine processor count: 4
OS version: Windows Server 2012
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: NoPackage properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: R:x64setup
Installation edition: StandardProduct Update Status:
None discovered.User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
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: false
ENU: true
ERRORREPORTING: false
FEATURES:
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: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: falseConfiguration file: C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140613_122137ConfigurationFile.ini
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indentedException type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
Message:
‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
HResult : 0x84b10001
FacilityCode : 1201 (4b1)
ErrorCode : 1 (0001)
Data:
HelpLink.EvtType =
0x066FCAFD@0x5539C151
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
Inner exception type: System.Xml.XmlException
Message:
‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
HResult : 0x80131940
Stack:
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
/* Don Reynolds */
-
-
Proposed as answer by
Saeid Hasani
Saturday, June 14, 2014 5:39 AM -
Marked as answer by
Saeid Hasani
Monday, June 23, 2014 7:26 PM -
Unmarked as answer by
Don Reynolds
Wednesday, July 2, 2014 3:17 PM -
Unproposed as answer by
Don Reynolds
Wednesday, July 9, 2014 4:31 PM
-
Proposed as answer by
-
I performed all the steps: folders gone, registry wiped, msizap ran on the msde program id.
I’m not sure msizap did anything though. Are there better removal steps/tools for server 2012r2 64bit?
How can I verify msde is the problem or if it is removed?
/* Don Reynolds */
-
I’m not sure msizap did anything though. Are there better removal steps/tools for server 2012r2 64bit?
How can I verify msde is the problem or if it is removed?
/* Don Reynolds */
For MSDE I guess you already referred to the the Microsoft Support link for removing SQL Server 2012 you can follow
this Microsoft LinkIf you still face issue removing please refer to solution section in Below link to remove SQL server manually from registry. Follow this step only if you face issue while removing SQL server with above link
1. Uninstall the existing SQL Server and all the components from the add remove program.
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. Rename all the SQL Server folders in the computer.
7. Reboot the machine.
Detailed Information is mentioned in Solution Section of
This link>>How can I verify msde is the problem or if it is removed?
Probably difficult to say hope you have followed MS link for removal correctly and if SQL 2012 is removed completely install fresh installation hope you will succeed
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
-
Edited by
Shanky_621MVP
Friday, June 13, 2014 10:57 PM -
Proposed as answer by
Saeid Hasani
Saturday, June 14, 2014 5:40 AM -
Unproposed as answer by
Don Reynolds
Saturday, June 14, 2014 12:28 PM
-
Edited by
-
I’m not sure why you want me to uninstall all SQL servers. First of all I need the databases in SQL 2012. Second, if msde is the problem, then why would uninstalling SQL 2012 help? Third, surely SQL 2014 will install with SQL 2012 installed. They are both
current products.
/* Don Reynolds */
-
I’m not sure why you want me to uninstall all SQL servers. First of all I need the databases in SQL 2012. Second, if msde is the problem, then why would uninstalling SQL 2012 help? Third, surely SQL 2014 will install with SQL 2012 installed. They
are both current products.
/* Don Reynolds */
I your previous post you said about removal of 2012 r2 I somehow though you are asking for removal of 2012 may be you want to doa fresh installation I misread the post apologies. Please don’t uninstall it.Instead if there is failed 2014 component please remove
that and start a fresh installation. You can install SQL Server 2014 and SQL server 2012 side by side that is for sure, and is fully supported
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
-
Edited by
Shanky_621MVP
Friday, June 13, 2014 11:16 PM
-
Edited by
-
Is there someone on the SQL team that can tell us what the installer is looking at that is causing this error? I’m sure it is one specific thing. Hacking folders and the registry when no one is sure of the problem seems reckless. The log and error message
itself are completely useless, not to mention these are all Microsoft products by the SQL team. We have hundreds of users so not being able to upgrade is directly affecting their ability to sell thousands of dollars of software and licenses. I would think
it would be in their best interest to address this directly.
/* Don Reynolds */
-
I just meant is their a better tool or instructions for the manual removal of msde in WINDOWS SERVER 2012 R2 64bit. The kb article is how to remove it in Windows Server 2003, so the platform SDK is no longer applicable and getting the msizap tool is very
difficult. Plus I’m not sure it even works correctly.
/* Don Reynolds */
-
You can try fresh installation of SQL server 2014 after removing MSDE components. Or you can raise a case with Microsoft team in that case SQL server team will immediately look at your issue. Its hard to catch MS guys on this forum.I am not sure why
MSDE removal link helped many but is causing issue with your environment. Or may be since you had series of issue you are little skeptical.I would recommend you to first try again instead of shedding some bucks and getting MS support. Or you can wait for others to reply
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
-
Proposed as answer by
Saeid Hasani
Saturday, June 14, 2014 5:41 AM -
Edited by
Shanky_621MVP
Saturday, June 14, 2014 11:55 AM -
Marked as answer by
Saeid Hasani
Monday, June 23, 2014 7:26 PM -
Unmarked as answer by
Don Reynolds
Wednesday, July 9, 2014 4:31 PM -
Unproposed as answer by
Don Reynolds
Wednesday, July 9, 2014 4:31 PM
-
Proposed as answer by
-
I’m certainly not paying to evaluate a new product (or to update a previously purchased product that is still current) because the SQL team made an installer that isn’t aware of their own products and isn’t generating enough info to allow me to get around,
identify, or fix the problem. If they would have made an uninstaller for msde, no one would have this issue (assuming that’s what it is). Any way you look at it, this is 100% the SQL team’s fault.
/* Don Reynolds */
-
I can understand your situation believe me but this is way it goes. Its quite possible that MSDE is in broken state so you cannot see the respective registry keys. You can raise case and if Microsoft finds problem with there software you would be refunded
at laest this happened in my case in SQL 2012.The whole process of un installation also depends on human error and how much expert you are with SQL server installation.
Good luck
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
-
Edited by
Shanky_621MVP
Saturday, June 14, 2014 11:56 AM
-
Edited by
-
Msde was in a good state. Who is an expert at uninstalling it that can tell me if it is uninstalled? I followed the instructions for uninstalling it in windows server 2003, despite having server 2012r2 64bit. That did not work.
/* Don Reynolds */
-
This is not even close to an answer.
/* Don Reynolds */
-
Hi Don,
This is a quick reply to let you know that I’m trying to involve someone familiar with this topic to further look at this issue.There might be some time delay.
Appreciate your patience.
Tracy Cai
TechNet Community Support -
Thanks.
/* Don Reynolds */
-
Thank you for contacting Microsoft. According to the previous similar case, your issue is caused by MSDE. I understand that you have followed the KB 320873 to try to manually uninstall the MSDE.
However, some registry described in the document can’t be found in your server. So you don’t know whether you have thoroughly uninstall it or not.
Unfortunately, since the MSDE is no longer supported, there are few document about this tool. Regarding uninstall it, we usually use control panel to remove (http://technet.microsoft.com/en-us/library/cc720203(v=ws.10).aspx),
if this doesn’t work, we move to manually uninstall it which is described in http://support.microsoft.com/kb/320873. According to your description, we highly suspect that the MSDE is not completely removed on your server. However, how can you have MSDE on
Windows Server 2012? Since MSDE is not supported on Windows Server 2012.To check whether is removed or not, please
1. Go to Add or Remove Programs in Control Panel, found Microsoft SQL Server 2000 Desktop Engine program, if it is still there,
remove it.2. Run services.msc and look for MSDE service.
If you cannot find MSDE based on the method above. We highly suggest that run process monitor during SQL Server 2014 installation. Check the monitor log to find out
which registry interfere the installation. Find out the registry belong to MSDE and delete them. Then try to install SQL Server 2014 again.-
Proposed as answer by
Saeid Hasani
Thursday, June 19, 2014 9:52 PM -
Marked as answer by
Saeid Hasani
Monday, June 23, 2014 7:26 PM -
Unmarked as answer by
Don Reynolds
Wednesday, July 2, 2014 3:18 PM -
Unproposed as answer by
Don Reynolds
Wednesday, July 9, 2014 4:32 PM
-
Proposed as answer by
-
There is no add/remove programs item or any sort of uninstaller for MSDE. This was not a good decision by the SQL Team.
There was never an «MSDE» service. There was only an MSDE SQL Server Instance in services, which is gone since I manually removed the registry entries that started it.
It’s not a registry key that is causing the failure. Judging by the exception, it is the SQL Server installer’s code trying to build some xml (most likely from system dbs of all the running SQL instances) and not finding a node that it is expecting or finding
a node that doesn’t conform to the newer SQL server structure (because MSDE is from SQL 2000 days) or something like that.…
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
Inner exception type: System.Xml.XmlException
Message:
‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.…
at System.Xml.XmlDocument.Load(XmlReader reader)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)It is probably a simple bug in the installer code made by the SQL Team because they didn’t take into account their own products and installers from the past.
MSDE works fine on all versions of Windows with any version of SQL Server if you install it after a new SQL Server is already installed. There is likely nothing the newer installers do that even affect the older versions of SQL. This appears to be an enumeration
problem during the installer startup.It’s sloppy and extremely frustrating that it leaves a system in a completely static state. I can no longer receive updates for my installed version of SQL Server 2012 or install newer versions.
/* Don Reynolds */
-
Hello Don,
Thank you for your respond. We highly suggest that use Process Monitor to monitor the SQL Server installation for further troubleshooting.
From a support perspective this is really beyond what we can do here in the forums. If you cannont determine your answer here or on your own, consider opening a support case with us. Visit this link to see the various support options that are available to
better meet your needs:http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone.
-
Proposed as answer by
Ed Price — MSFTMicrosoft employee
Friday, August 1, 2014 9:22 PM -
Unproposed as answer by
Don Reynolds
Sunday, August 3, 2014 10:26 PM
-
Proposed as answer by
-
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.
The exception showed Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument as the problem. There are dozens of suspect XML files ScenarioEngine.exe queries before crashing, every single one having result of INVALID PARAMETER:
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Datastore*.xml
I saw that one of the last things ScenarioEngine.exe writes to for logging is C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Detail.txt
(01) 2014-07-02 10:52:59 Slp: Running Action: RunRemoteDiscoveryAction
(01) 2014-07-02 10:52:59 Slp: Running discovery on local machine
(01) 2014-07-02 10:53:03 Slp: Error: Action «Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction» threw an exception during execution.
(01) 2014-07-02 10:53:03 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747. —> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException:
‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747. —> System.Xml.XmlException: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.These are all the XML files:
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreInputSettings_ChainerSettings_SlpSettings.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreInputSettings_FeatureSpecific_SlpInputSettings.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreInputSettings_RsDumper_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastorePackage.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProduct.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_AgentScript_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Agent_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Agent_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_AsDumper_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_AsInstanceId_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ASSIP_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_AS_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_AS_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterDisk_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterDisk_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterGroup_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterGroup_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterIPAddresses_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterIPAddresses_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterNodesStatus_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterNode_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ClusterNode_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_DReplayClient_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_DReplayController_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_FailOverClusterName_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_FailoverClusterName_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Fulltext_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Fulltext_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ManagementToolsAdvanced_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ManagementToolsAdvanced_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ManagementTools_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_ManagementTools_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Repl_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Repl_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_RsInstanceId_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Sku_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Sku_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SlpDumper_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Slp_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_Slp_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SniServer_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SniServer_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlBrowserStopService_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlBrowser_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlBrowser_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlEngineDumper_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlEngine_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlEngine_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlInstanceId_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlLegacyDiscovery_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlLegacyDiscovery_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlPowershell_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlPowershell_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlRSSHP_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlRSSHP_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlRS_DBPrivate.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlRS_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SqlRS_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SQLServerSCP_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SSIS_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SSIS_Public.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_SSIS_VSTA_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreProductSettings_XTP_Private.xml
C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236DatastoreSLP_Actions_PersistedActionData.xml
/* Don Reynolds */
-
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.
/* Don Reynolds */
-
Here’s the full Detail.txt:
(01) 2014-07-02 10:52:55 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile’ has been registered
(01) 2014-07-02 10:52:55 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus’ has been registered
(01) 2014-07-02 10:52:55 Slp: Reading XML resource ‘Microsoft.SQL.Chainer.PackageData.Package.xml’
(01) 2014-07-02 10:52:55 Slp: Reading schema resource ‘Microsoft.SQL.Chainer.Package.Package.xsd’
(01) 2014-07-02 10:52:55 Slp: Document ‘Microsoft.SQL.Chainer.PackageData.Package.xml’ validated with schema ‘Microsoft.SQL.Chainer.Package.Package.xsd’ has been successfuly loaded into datastore path ‘/Datastore/Package’
(01) 2014-07-02 10:52:56 Slp: ———————————————————————-
(01) 2014-07-02 10:52:56 Slp: Running Action: ReadProductXML
(01) 2014-07-02 10:52:56 Slp: Reading XML resource ‘Microsoft.SQL.Chainer.Product.Product.xml’
(01) 2014-07-02 10:52:56 Slp: Document ‘Microsoft.SQL.Chainer.Product.Product.xml’ validated with schema ‘Microsoft.SQL.Chainer.Product.Product.xsd’ has been successfuly loaded into datastore path ‘/Datastore/Product’
(01) 2014-07-02 10:52:56 Slp: Completed Action: ReadProductXML, returned True
(01) 2014-07-02 10:52:56 Slp: ———————————————————————-
(01) 2014-07-02 10:52:56 Slp: Running Action: LoadExtensions
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘MSI’ from file ‘R:x64.Microsoft.SqlServer.Configuration.MsiExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘MSI’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘PackageChainer’ from file ‘R:x64.Microsoft.SqlServer.Configuration.PackageChainerExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘PackageChainer’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘Config’ from file ‘R:x64.Microsoft.SqlServer.Configuration.ConfigExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘Config’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘Common’ from file ‘R:x64.Microsoft.SqlServer.Chainer.ExtensionCommon.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘Common’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SqlConfigBase’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SqlConfigBase.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SqlConfigBase’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘Slp’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SetupExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘Slp’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘RulesEngine’ from file ‘R:x64.Microsoft.SqlServer.Configuration.RulesEngineExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘RulesEngine’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘WorkflowData’ from file ‘R:x64.Microsoft.SqlServer.Chainer.WorkflowData.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘WorkflowData’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SlpConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SlpExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SlpConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘Clst’ from file ‘R:x64.Microsoft.SqlServer.Configuration.Cluster.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘Clst’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘AgentConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.AgentExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘AgentConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SqlPowershellConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.PowershellExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SqlPowershellConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SSISConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SSISExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SSISConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘DReplayConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘DReplayConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘ASConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.ASExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘ASConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘ReplConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘ReplConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘ManagementToolsConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘ManagementToolsConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘ManagementToolsAdvancedConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘ManagementToolsAdvancedConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘UI’ from file ‘R:x64.Microsoft.SqlServer.Configuration.UIExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘UI’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘ConfigurationResources’ from file ‘R:x64.Microsoft.SqlServer.Configuration.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘ConfigurationResources’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SqlEngineConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SqlEngineConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘XTPConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.XTP.ConfigExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘XTPConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SniServerConfigExt’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SniServerConfigExt.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SniServerConfigExt’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SqlBrowserConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SqlBrowserExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SqlBrowserConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SqlRSConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.RSExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SqlRSConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SqlRSSHPConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.RSShpExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SqlRSSHPConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘FulltextConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘FulltextConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘ScoExtension’ from file ‘R:x64.Microsoft.SqlServer.Configuration.ScoExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘ScoExtension’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘Infrastructure’ from file ‘R:x64.Microsoft.SqlServer.Chainer.Infrastructure.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘Infrastructure’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘UtilityConfig’ from file ‘R:x64.Microsoft.SqlServer.Configuration.UtilityExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘UtilityConfig’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Loading extension ‘SmartSetup’ from file ‘R:x64.Microsoft.SqlServer.Configuration.SmartSetupExtension.dll’
(01) 2014-07-02 10:52:56 Slp: Extension ‘SmartSetup’ version ‘12.0.2000.8’ loaded
(01) 2014-07-02 10:52:56 Slp: Completed Action: LoadExtensions, returned True
(01) 2014-07-02 10:52:56 Slp: ———————————————————————-
(01) 2014-07-02 10:52:56 Slp: Running Action: ExecuteBootstrapAfterExtensionsLoaded
(01) 2014-07-02 10:52:57 Slp: Workflow to execute: ‘BOOTSTRAPAFTEREXTENSIONSLOADED’
(01) 2014-07-02 10:52:57 Slp: ———————————————————————-
(01) 2014-07-02 10:52:57 Slp: Running Action: SetGlobalPackageFlags
(01) 2014-07-02 10:52:57 Slp: Setting /Package/ProductName to SQL2014
(01) 2014-07-02 10:52:57 Slp: Setting /Package/SupportedLanguages to 1028;1031;1033;1036;1040;1041;1042;1046;1049;2052;3082;1053
(01) 2014-07-02 10:52:57 Slp: Setting /Package/LogPath to %ProgramFiles%Microsoft SQL Server120Setup BootstrapLog
(01) 2014-07-02 10:52:57 Slp: Setting /Package/GlobalProperties/StopActionRequireMode to ShowProgressOnly
(01) 2014-07-02 10:52:57 Slp: Completed Action: SetGlobalPackageFlags, returned True
(01) 2014-07-02 10:52:57 Slp: ———————————————————————-
(01) 2014-07-02 10:52:57 Slp: Running Action: LoadPackageDatastoreObjects
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettingsDefaults.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettingsDefaults.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettings.xsd’ loaded into datastore path ‘/Datastore/InputSettings/ChainerSettings/SlpSettings’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpFeatureInputSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpFeatureInputSettingDefaults.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpFeatureInputSettingDefaults.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpFeatureInputSettings.xsd’ loaded into datastore path ‘/Datastore/InputSettings/FeatureSpecific/SlpInputSettings’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlInstanceIdPrivateConfigObject.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlInstanceIdPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlInstanceIdPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlInstanceIdPrivateConfigObject.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SqlInstanceId/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.AsInstanceIdPrivateConfigObject.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.AsInstanceIdPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.AsInstanceIdPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.AsInstanceIdPrivateConfigObject.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/AsInstanceId/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.RsInstanceIdPrivateConfigObject.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.RsInstanceIdPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.RsInstanceIdPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.RsInstanceIdPrivateConfigObject.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/RsInstanceId/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPublicSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Slp/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SlpExtension.SlpPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Slp/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPublicSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPublicSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPublicSettings.xsd’ loaded into datastore path
‘/Datastore/ProductSettings/SqlLegacyDiscovery/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPrivateSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPrivateSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SlpExtension.SqlLegacyDiscoveryPrivateSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SqlLegacyDiscovery/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpDumperPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpDumperPrivateConfigDefault.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpDumperPrivateConfigDefault.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SlpDumperPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SlpDumper/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlDumperPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlDumperPrivateConfigDefault.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlDumperPrivateConfigDefault.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SqlDumperPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SqlEngineDumper/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.AsDumperPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.AsDumperPrivateConfigDefault.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.AsDumperPrivateConfigDefault.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.AsDumperPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/AsDumper/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.RsDumperPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.RsDumperPrivateConfigDefault.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.RsDumperPrivateConfigDefault.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.RsDumperPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/InputSettings/RsDumper/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPublicSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Agent/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Agent/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentScriptPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentScriptPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.AgentExtension.AgentPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/AgentScript/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPublicSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SSIS/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SSISExtension.SSISPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SSIS/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SSISExtension.VSTAPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SSISExtension.VSTAPrivateSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SSISExtension.VSTAPrivateSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SSISExtension.VSTAPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SSIS/VSTA/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPublicSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SqlPowershell/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.PowershellExtension.PowershellPrivateSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SqlPowershell/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ASExtension.ASPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ASExtension.ASPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ASExtension.ASPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ASExtension.ASPublicSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/AS/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ASExtension.ASPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ASExtension.ASPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ASExtension.ASPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ASExtension.ASPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/AS/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePublicSettings.xsd’ loaded into
datastore path ‘/Datastore/ProductSettings/SqlEngine/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPublicSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Repl/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.SqlEnginePrivateSettings.xsd’ loaded
into datastore path ‘/Datastore/ProductSettings/SqlEngine/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.XTP.ConfigExtension.HkPerfCtrPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.XTP.ConfigExtension.HkPerfCtrPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.XTP.ConfigExtension.HkPerfCtrPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.XTP.ConfigExtension.HkPerfCtrPrivateSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/XTP/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPublicSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/Fulltext/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Fulltext_ConfigExtension.FulltextPrivateSettings.xsd’ loaded into
datastore path ‘/Datastore/ProductSettings/Fulltext/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PrivateSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SniServer/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SniServer.SniServerConfigExt_PublicSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SniServer/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPublicConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPublicConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPublicConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SqlBrowser/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SqlBrowser/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xsd’
/* Don Reynolds */
-
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xsd’ loaded
into datastore path ‘/Datastore/ProductSettings/SqlBrowserStopService/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Sku/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/Sku/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd’ loaded into datastore path
‘/Datastore/ProductSettings/Repl/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SqlRSSHP/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd’ loaded into
datastore path ‘/Datastore/ProductSettings/SqlRSSHP/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd’ loaded into datastore path
‘/Datastore/ProductSettings/SqlRS/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd’ loaded into datastore path
‘/Datastore/ProductSettings/SqlRS/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd’ loaded into datastore
path ‘/Datastore/ProductSettings/SqlRS/DBPrivate’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd’
loaded into datastore path ‘/Datastore/ProductSettings/ManagementTools/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd’
loaded into datastore path ‘/Datastore/ProductSettings/ManagementTools/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd’
loaded into datastore path ‘/Datastore/ProductSettings/ManagementToolsAdvanced/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd’
loaded into datastore path ‘/Datastore/ProductSettings/ManagementToolsAdvanced/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd’ loaded
into datastore path ‘/Datastore/ProductSettings/DReplayController/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd’ loaded into
datastore path ‘/Datastore/ProductSettings/DReplayClient/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterDisk/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterDisk/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterGroup/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterGroup/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterIPAddresses/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterIPAddresses/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/FailOverClusterName/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/FailoverClusterName/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterNode/Private’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterNode/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/SQLServerSCP/Private’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml’ loaded into datastore path ‘/Datastore/ProductSettings/ClusterNodesStatus/Public’
(01) 2014-07-02 10:52:57 Slp: Reading schema resource ‘Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd’
(01) 2014-07-02 10:52:57 Slp: Reading XML resource ‘Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml’
(01) 2014-07-02 10:52:57 Slp: Document ‘Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml’ validated with schema ‘Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd’ loaded into datastore path ‘/Datastore/ProductSettings/ASSIP/Public’
(01) 2014-07-02 10:52:57 Slp: Completed Action: LoadPackageDatastoreObjects, returned True
(01) 2014-07-02 10:52:57 Slp: ———————————————————————-
(01) 2014-07-02 10:52:57 Slp: Running Action: InitializeInputSettingStore
(01) 2014-07-02 10:52:57 Slp: Completed Action: InitializeInputSettingStore, returned True
(01) 2014-07-02 10:52:57 Slp: ———————————————————————-
(01) 2014-07-02 10:52:57 Slp: Running Action: InitializeRoleService
(01) 2014-07-02 10:52:57 Slp: Loading role: SPI_AS_NewFarm
(01) 2014-07-02 10:52:58 Slp: Loading role: SPI_AS_ExistingFarm
(01) 2014-07-02 10:52:58 Slp: Loading role: AllFeatures_WithDefaults
(01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRoleService, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerCommandLineArguments
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: WORKFLOW
(01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: TIMESTAMP
(01) 2014-07-02 10:52:58 Slp: Value specified: 20140702_105236
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: LOGMARKER
(01) 2014-07-02 10:52:58 Slp: Value specified:
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: MEDIASOURCE
(01) 2014-07-02 10:52:58 Slp: Value specified: R:
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: INSTALLMEDIAPATH
(01) 2014-07-02 10:52:58 Slp: Value specified: R:x64setup
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: ENU
(01) 2014-07-02 10:52:58 Slp: Value specified: True
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: MEDIALAYOUT
(01) 2014-07-02 10:52:58 Slp: Value specified: Full
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: ACTION
(01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: RULES
(01) 2014-07-02 10:52:58 Slp: Value specified: SCCCheckRules
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessMediaChainerConfigFileArguments
(01) 2014-07-02 10:52:58 Slp: Procssing media configuration file R:x64setup..DefaultSetup.ini.
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Setting: PID
(01) 2014-07-02 10:52:58 Slp: New setting source: ConfigFile; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: —————————————-
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerConfigFileArguments
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessSlipstreamParameters
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessSlipstreamParameters, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
(01) 2014-07-02 10:52:58 Slp: Action is being skipped due to the following restrictions:
(01) 2014-07-02 10:52:58 Slp: Condition «IsMediaExpress» did not pass as it returned false and true was expected.
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: InitializeRetryHandler
(01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRetryHandler, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: ExecuteBootstrapProcessInputSettings
(01) 2014-07-02 10:52:58 Slp: Workflow to execute: ‘BOOTSTRAPPROCESSINPUTSETTINGS’
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: StartSqmSession
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to open registry subkey SoftwareMicrosoftMicrosoft SQL Server120
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2014-07-02 10:52:58 Slp: SQM Service: Sqm does not have active session.
(01) 2014-07-02 10:52:58 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
(01) 2014-07-02 10:52:58 Slp: Completed Action: StartSqmSession, returned True
(01) 2014-07-02 10:52:58 Slp: ———————————————————————-
(01) 2014-07-02 10:52:58 Slp: Running Action: ValidateChainerSetting
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : Compute new PID
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : Read lcid 1033 from CultureInfo
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateChainerSetting, returned True
(01) 2014-07-02 10:52:59 Slp: ———————————————————————-
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureCommandLineArguments
(01) 2014-07-02 10:52:59 Slp: —————————————-
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ———————————————————————-
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
(01) 2014-07-02 10:52:59 Slp: Procssing media configuration file R:x64setup..DefaultSetup.ini.
(01) 2014-07-02 10:52:59 Slp: —————————————-
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ———————————————————————-
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureConfigFileArguments
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ———————————————————————-
(01) 2014-07-02 10:52:59 Slp: Running Action: ValidateSettingsAgainstScenario
(01) 2014-07-02 10:52:59 Slp: Scenario: RunRules
(01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
(01) 2014-07-02 10:52:59 Slp: ———————————————————————-
(01) 2014-07-02 10:52:59 Slp: Running Action: FinalCalculateSettings
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: — PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: Completed Action: FinalCalculateSettings, returned True
(01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapProcessInputSettings, returned True
(01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
(01) 2014-07-02 10:52:59 Slp: ———————————————————————-
(01) 2014-07-02 10:52:59 Slp: Running Action: RunRemoteDiscoveryAction
(01) 2014-07-02 10:52:59 Slp: Running discovery on local machine
(01) 2014-07-02 10:53:03 Slp: Error: Action «Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction» threw an exception during execution.
(01) 2014-07-02 10:53:03 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747. —> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException:
‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747. —> System.Xml.XmlException: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributes()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElement()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElementContent()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlDocument.Load(XmlReader reader)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: — End of inner exception stack trace —
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp: — End of inner exception stack trace —
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2014-07-02 10:53:03 Slp: Received request to add the following file to Watson reporting: c:temptmpFEEB.tmp
(01) 2014-07-02 10:53:03 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2014-07-02 10:53:03 Slp: Inner exceptions are being indented
(01) 2014-07-02 10:53:03 Slp:
(01) 2014-07-02 10:53:03 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
(01) 2014-07-02 10:53:03 Slp: Message:
(01) 2014-07-02 10:53:03 Slp: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp: HResult : 0x84b10001
(01) 2014-07-02 10:53:03 Slp: FacilityCode : 1201 (4b1)
(01) 2014-07-02 10:53:03 Slp: ErrorCode : 1 (0001)
(01) 2014-07-02 10:53:03 Slp: Stack:
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp: Inner exception type: System.Xml.XmlException
(01) 2014-07-02 10:53:03 Slp: Message:
(01) 2014-07-02 10:53:03 Slp: ‘.’, hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp: HResult : 0x80131940
(01) 2014-07-02 10:53:03 Slp: Stack:
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32&
charCount, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributes()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElement()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElementContent()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlDocument.Load(XmlReader reader)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix,
String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:08 Slp: Watson Bucket 2
Original 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 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : System.Xml.XmlTextReaderImpl.Throw
(01) 2014-07-02 10:53:08 Slp: Parameter 3 :
Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1(01) 2014-07-02 10:53:08 Slp: Parameter 4 :
System.Xml.XmlException@-2146232000(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 FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Registry_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 FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Registry_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 FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Registry_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 FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Registry_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 FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Registry_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 FilesMicrosoft SQL Server120Setup BootstrapLog20140702_105236Registry_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 SoftwareMicrosoftMicrosoft SQL Server120
(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 SoftwareMicrosoftMicrosoft SQL Server120EnableErrorReporting=.
(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.
/* Don Reynolds */
-
I finally got the SQL 2014 installer to work.
I did a search from Programs and Features until I found «Microsoft SQL Server Database Engine». For some reason it was not in the default list. Filtering for it with the search bar at the top right found it when I typed «engine».
After uninstalling MSDE and rebooting, the SQL 2014 installer worked.
/* Don Reynolds */
-
Marked as answer by
Don Reynolds
Thursday, August 14, 2014 1:45 PM
-
Marked as answer by
-
I finally got the SQL 2014 installer to work.
I did a search from Programs and Features until I found «Microsoft SQL Server Database Engine». For some reason it was not in the default list. Filtering for it with the search bar at the top right found it when I typed «engine».
After uninstalling MSDE and rebooting, the SQL 2014 installer worked.
/* Don Reynolds */
Thanks for Answer but it seems you were doing the mistake by not properly removing the components.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
-
My mistake was ever installing MSDE, but unfortunately I had to deal with a legacy app that was referencing it. In my opinion the SQL 2012/2014 setup and advisory apps shouldn’t exception and crash when MSDE is installed considering the same team
made the products, the MSDE programs and features entry shouldn’t be invisible unless you manually search for it, and the manual uninstall steps for MSDE are obviously not adequate because they do not work at all. Maybe my ordeal will help someone else avoid
frustration in the future.
/* Don Reynolds */
-
while upgrading SQL server 2012 to its latest service pack which is sp4,
<g class=»gr_ gr_132 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace» data-gr-id=»132″ id=»132″>i</g> am facing an error. if anyone could help me
with this errorkindly suggest me how to resolve this issue
Overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2068774911
Exit facility code: 1201
Exit error code: 1
Exit message: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
Start time: 2019-02-20 14:08:31
End time: 2019-02-20 14:08:51
Requested action: Patch
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.7001.0&EvtType=0x7DF5276F%400x3FB6F251&EvtType=0x7DF5276F%400x3FB6F251Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 4
KBArticle: KB4018073
KBArticleHyperlink: http://support.microsoft.com/?kbid=4018073
PatchType: SP
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 11.4.7001.0
ProductVersion: 11.0.2100.60
GDRReservedRange: 11.0.2200.60:11.0.2300.00;11.0.3100.0:11.0.3299.0;11.0.5300.0:11.0.5499.0;11.0.6200.0:11.0.6499.0;11.0.7200.0:11.0.7399.0
Installation location: e:b6ad5a1c421d828c59ee98ee16532fx64setupUser Input Settings:
ACTION: Patch
ALLINSTANCES: false
CLUSTERPASSIVE: false
CONFIGURATIONFILE:
ENU: true
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCEID: <empty>
INSTANCENAME: <empty>
QUIET: false
QUIETSIMPLE: false
SQMREPORTING: false
UIMODE: Normal
X86: falseRules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indentedException type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
Message:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
HResult : 0x84b10001
FacilityCode : 1201 (4b1)
ErrorCode : 1 (0001)
Data:
HelpLink.EvtType = 0x7DF5276F@0x3FB6F251
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile.WriteLine(LogSource source, LogStyle style, LogSeverity severity, String formatBuffer, Object[] objectArray)
at Microsoft.SqlServer.Chainer.Infrastructure.LogService.WriteLine(LogSource source, LogStyle style, LogSeverity severity, String formatBuffer, Object[] objectArray)
at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.GetInstalledPatchBySQLDiscovery(PackageInstallProperty targetPackage)
at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.GetInstalledPatch(PackageInstallProperty targetPackage)
at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.GetInstalledPackages(String instanceName, List`1& installedInstancePackages, List`1& installedSharedPackages, String& returnedErrorMessage)
at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.CollectProductData()
at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinitionAllInstances()
at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase..ctor(ServiceContainer context, FeatureEdition featureEdition)
at Microsoft.SqlServer.Configuration.PatchFeatureTree..ctor(ServiceContainer context)
at Microsoft.SqlServer.Configuration.PatchFeatureTree.InitializePatchFeatureTree(ServiceContainer context)
at Microsoft.SqlServer.Configuration.SetupExtension.InitializeUIDataAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: System.FormatException
Message:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
HResult : 0x80131537
Stack:
at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at System.IO.TextWriter.WriteLine(String format, Object[] arg)
at Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile.WriteLine(LogSource source, LogStyle style, LogSeverity severity, String formatBuffer, Object[] objectArray)-
Edited by
Abid.dba
Thursday, February 21, 2019 5:25 AM
-
Edited by
SQL Server Setup has encountered the following error:
There was an error generating the XML document.
Error code 0x84B10001.
This issue occurs when SQL Server(2008, 2012, 2014, 2016, 2017) Setup fails.
Cause of this Error:
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.
Solution-1:
From Control Panel, uninstall existing Microsoft SQL Server Setup installation and start again with fresh installation.
Solution-2:
1. Create a new windows user on your machine and add this user to local Administrator group.
2. Log in with new user and start the SQL Server installation again.