SQL Server Setup Failure 0x84B10001 (SQL 2012 SP2 and SQL 2014 Standard)

I'm having a problem with SQL Server Setup. I had SQL Server 2012 R2 SP1 installed, and the SP2 installer would fail.
I decided to just get SQL Server 2014. The setup (and system configuration checker) for that fails with the same error.
SQL Server Setup failure
SQL Server Setup has encountered the following error:
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
Error code 0x84B10001
I found this and other posts about similar problems that point at MSDE being the cause.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc9f4949-1b45-427c-aa2b-d2222488a13e/problems-installing-sql-server-2012error-code-0x84b10001?forum=sqlexpress
I definitely had MSDE installed, but I went through the steps to manually remove it and rebooted with no luck.
/* 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:\x64\setup\
(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:\x64\setup\..\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 Software\Microsoft\Microsoft SQL Server\120
(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:\x64\setup\..\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:\temp\tmpFEEB.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 Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:10 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:10 Slp: Watson bucket for exception based failure has been created
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2014-07-02 10:53:10 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\120\EnableErrorReporting=.
(01) 2014-07-02 10:53:10 Slp: WER: Application level consent value '' was mapped to consent status 'WerConsentNotAsked'
(01) 2014-07-02 10:53:12 Slp: WER: Result of the submission:: 'WerReportCancelled'
(01) 2014-07-02 10:53:12 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: Error result: -2068774911
(01) 2014-07-02 10:53:12 Slp: Result facility code: 1201
(01) 2014-07-02 10:53:12 Slp: Result error code: 1
(01) 2014-07-02 10:53:12 Slp: SQM Service: Sqm does not have active session.
/* Don Reynolds */

Similar Messages

  • SQL Server Setup failure (Error code 0x858C001B)

    Hola..
    Vengo con un problema que me esta causando desesperacion, ya he buscado en los hilos y no puedo solucionar este problema.
    Resulta que descargue la version de SQL Server Express 2012 64 bits y al quere instalarlo me muestra el error:
    SQL Server Setup has encountered the following error:
    The SQL Server license agreement cannot be located for the selected edition, EXPRESS. This could be a result of corrupted media or the edition being unsupported by the media.
    Error code 0x858C001B
    Ya he buscado y no encuentro respuesta. 
    SQL Server Setup failure (Error code 0x858C001B)

    Hi,
    Can u have look at this Discussion
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • SQL Server Setup failure.SQL Server Setup has encountered the following error: Method not found: 'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()'.. ----------

    Hi Team,
    Earlier i had SQL Server 2008 R2 on my Machine. For one work around i unistall SQL Server 2008 R2 and Trying to install SQL Server 2008 but i am not able to install with below error:
    TITLE: SQL Server Setup failure.
    SQL Server Setup has encountered the following error:
    Method not found: 'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()'..
    Thanks

    Hi Lydia,
    i have followed the above step and i am able to proceed further but while installation i am getting the below error consistently.
    TITLE: Microsoft SQL Server 2008 Setup
    The following error has occurred:
    Locating the SQL Server Browser service component failed with Windows Installer return code '2'. The component ID: '{2E86FD41-C179-456E-8E6A-5157ED427228}'.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x8510C01B%25400x31BA4472%25401222%254052007
    BUTTONS:
    &Retry
    Cancel
    2: 
    TITLE: Microsoft SQL Server 2008 Setup
    The following error has occurred:
    SQL Server Browser configuration for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' was cancelled by user after a previous installation failure. The last attempted step: Retrieving full path to the SQL Server Browser service executable using Windows Installer
    API for the SQL Server Browser component with ID '{2E86FD41-C179-456E-8E6A-5157ED427228}'..
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x8510C01B%25400x31BA4472%25401222%254052007
    BUTTONS:
    OK
    After ignoring these step..installation getting complete but ..at the end i am not able to connect to server.
    Could you please help me on this.
    Thanks,
    Sumit

  • MOSS 2007 SP1 & SQL Server 2008 upgrade plan into MOSS 2010 and SQL Server 2008 R2 ?

    Hi All,
    I've got the following setup in one single server:
    Windows Server 2008 Standard
    SQL Server 2008 Standard
    SharePoint Server 2007 Enterprise SP1
    that I'd like to upgrade into the following:
    Windows Server 2008 R2 Standard
    SQL Server 2008 R2 SP1 ?
    SharePoint Server 2010 Enterprise
    can i just perform CA farm level backup then import it on the new SharePoint server ? is there any caveat that i should pay attention to ? (eg. non working site list or web parts ? )
    thanks.
    /* Infrastructure Support Engineer */

    Backup/import will not work for upgrade. As mentioned on the other thread, you need to perform a database attach upgrade to move to a separate 2010 from from a 2007 farm. For information about upgrading to SharePoint Server 2010, see the upgrade guide:
    http://technet.microsoft.com/en-us/library/cc303420.aspx 

  • Installation of SCCM 2012 R2 and SQL Server 2014 error

    Hello All,
    I am attempting to setup SQL Server 2014 and SCCM 2012 R2 but I keep running into an error stating that "Configuration Manager requires Microsoft SQL Server
    2008 SP2 w/ CU9........ all the way up to Microsoft SQL Server 2012 with CU2 or higher." I am using all evaluation versions for this configuration as we are looking to test and evaluate the products. I was trying it with SQL 2014 because I was running
    into the same error with SQL 2012 and according to "http://blogs.technet.com/b/configmgrteam/archive/2015/03/30/updated-sc2012-configmgr-sp1-and-sc2012r2-configmgr-support-sql-server-2014.aspx" SQL
    2014 is supported with SCCM 2012 R2. SQL is installed locally on the same box. 
    Any suggestions would be appreciated.
    Thanks,
    Tucker
    Update: When running the Pre-Req check these are some of the failed returns.....
    SQL Server Edition: Failed: Configuration Manager primary site and central administration site don't support SQL Server Express Edition
    Not sure why it is recognizing SQL Express as this is a new machine.
    SQL Server service running account: Failed: The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE.  You must configure
    the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
    For the SQL Service I am using a domain account created specifically for this.

    This has nothing to do with moving or restoring. The kb article says "This hotfix provides updated versions of the setup files and enables new installations
    of the System Center 2012 R2 Configuration Manager site database role and the System Center 2012 Configuration Manager SP1 site database role in Microsoft SQL Server 2014"
    Torsten Meringer | http://www.mssccmfaq.de

  • SQL Server Service Packs (2008, 2008R2, 2012)

    Hi all,
    it appears that no one took care of installing Service Packs for our SQL Servers from WSUS and now i have to do it. What i have:
    MS SQL Server 2008 R2 Service Pack 1
    MS SQL Server 2008 Service Pack 1,2,3
    MS SQL Server 2012 Service Pack 1,2
    As you could see some of them a really old.
    1. The fact that everything is running so far without any problems and complains bring the question: Do I have to install Service Packs?
    2. Is it ok if I go directly to the latest Service Pack for each Server or i have to go the "entire road" installing one after another.
    3. What is the best way to do the updates: Install all other security and critical updates, restart the server, then install the service pack and restart again the server. 
    Actually my knowledge for SQL Server and Updates for it are not so big that's why i want to apologies for the stupid questions. Thanks in advance

    1. The fact that everything is running so far without any problems and complains bring the question: Do I have to install Service Packs?
    Hi,
    Yes very much recommended if your SQL server 2008 is not at SP/Sp4 it would not come under extended support purview. If you have 2008 r2  not with SP3 again you are out of extended support.  For 2012 as well apply Sp2 .Mainstarem support for 2008/2008
    R2 has already ended
    2. Is it ok if I go directly to the latest Service Pack for each Server or i have to go the "entire road" installing one after another.
    Hi,
    Yes you can directly upgrade to SQL
    Server 2008 SP4 because SP are cumulative and latest SP will include all fixes present in one released before it . As a fact you can always apply latest SP for any SQL server version for fact that it is cumulative. Dont go for SP3 go for SP4 in 2008 and
    SP3 for 2008 r2
    3. What is the best way to do the updates: Install all other security and critical updates, restart the server, then install the service pack and restart again the server.
    Best way can be referred from below docs
    http://msdn.microsoft.com/en-us/library/dd638062%28v=sql.100%29.aspx
    http://social.technet.microsoft.com/wiki/contents/articles/25632.how-to-install-sql-server-2012-sp2-on-standalone-sql-server-instance.aspx
    Just above doc is for 2012 but will hold true for 2008 as well. SP might require restart of Windows machine on which SQL Server resides.
    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 Article
    MVP

  • SQL Server Setup Error

    Good Evening,
    I've been having an issue today whilst trying to install SQL Server 2012 to a newly built server running Windows Server 2012 R2. Whilst going through the 'Database Engine Configuration' where you assign parts of the installation to different directories.
    We are trying a new method of installing each part of SQL to an SMB file share on our Netapp. After pointing each part of installation to a specific directory and pressing next I receive the error attached
    I can see that it says that you need to give the SQL Server setup account the  Manage Auditing and Security Log policy on the local policy console. I've gone to this policy and added myself (Local Administrator), The server itself, the SQL Server
    Agent account and also the database engine account. I have rebooted the server and tried again running the installation both as myself and Administrator but still get the same error. Please could someone help me with this issue.
    Regards,

    Hello,
    Please read the following article.
    http://msdn.microsoft.com/en-us/library/hh759341.aspx
    Please review security and operating system considerations.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Server 2005 performance decreases with DB size while SQL Server 2012 is fine

    Hi,
    We have a C# windows service running that polls some files and inserts/updates some fields in database.
    The service was tested on a local dev machine with SQL Server 2012 running and performance was quite decent with any number of records. Later on the service was moved to a test stage environment where SQL Server 2005 is installed. At that point database
    was still empty and service was running just fine but later on, after some 500k records were written, performance problems came to light. After some more tests we've founds out that, basically, database operation performance in SQL Server 2005 decreases with
    a direct correlation with the database size. Here are some testing results:
    Run#
    1
    2
    3
    4
    5
    DB size (records)
    520k
    620k
    720k
    820k
    920k
    SQL Server 2005
    TotalRunTime
    25:25.1
    32:25.4
    38:27.3
    42:50.5
    43:51.8
    Get1
    00:18.3
    00:18.9
    00:20.1
    00:20.1
    00:19.3
    Get2
    01:13.4
    01:17.9
    01:21.0
    01:21.2
    01:17.5
    Get3
    01:19.5
    01:24.6
    01:28.4
    01:29.3
    01:24.8
    Count1
    00:19.9
    00:18.7
    00:17.9
    00:18.7
    00:19.1
    Count2
    00:44.5
    00:45.7
    00:45.9
    00:47.0
    00:46.0
    Count3
    00:21.7
    00:21.7
    00:21.7
    00:22.3
    00:22.3
    Count4
    00:23.6
    00:23.9
    00:23.9
    00:24.9
    00:24.5
    Process1
    03:10.6
    03:15.4
    03:14.7
    03:21.5
    03:19.6
    Process2
    17:08.7
    23:35.7
    28:53.8
    32:58.3
    34:46.9
    Count5
    00:02.3
    00:02.3
    00:02.3
    00:02.3
    00:02.1
    Count6
    00:01.6
    00:01.6
    00:01.6
    00:01.7
    00:01.7
    Count7
    00:01.9
    00:01.9
    00:01.7
    00:02.0
    00:02.0
    Process3
    00:02.0
    00:01.8
    00:01.8
    00:01.8
    00:01.8
    SQL Server 2012
    TotalRunTime
    12:51.6
    13:38.7
    13:20.4
    13:38.0
    12:38.8
    Get1
    00:21.6
    00:21.7
    00:20.7
    00:22.7
    00:21.4
    Get2
    01:38.3
    01:37.2
    01:31.6
    01:39.2
    01:37.3
    Get3
    01:41.7
    01:42.1
    01:35.9
    01:44.5
    01:41.7
    Count1
    00:20.3
    00:19.9
    00:19.9
    00:21.5
    00:17.3
    Count2
    01:04.5
    01:04.8
    01:05.3
    01:10.0
    01:01.0
    Count3
    00:24.5
    00:24.1
    00:23.7
    00:26.0
    00:21.7
    Count4
    00:26.3
    00:24.6
    00:25.1
    00:27.5
    00:23.7
    Process1
    03:52.3
    03:57.7
    03:59.4
    04:21.2
    03:41.4
    Process2
    03:05.4
    03:06.2
    02:53.2
    03:10.3
    03:06.5
    Count5
    00:02.8
    00:02.7
    00:02.6
    00:02.8
    00:02.7
    Count6
    00:02.3
    00:03.0
    00:02.8
    00:03.4
    00:02.4
    Count7
    00:02.5
    00:02.9
    00:02.8
    00:03.4
    00:02.5
    Process3
    00:21.7
    00:21.0
    00:20.4
    00:22.8
    00:21.5
    One more thing is that it's not Process2 table that constantly grows in size but is Process1 table, that gets almost 100k records each run.
    After that SQL Server 2005 has also been installed on a dev machine just to test things and we got exactly the same results. Both SQL Server 2005 and 2012 instances are installed using default settings with no changes at all. The same goes for databases
    created for the service.
    So the question is - why are there such huge differences between performance of SQL Server 2005 and 2012? Maybe there are some settings that are set by default in SQL Server 2012 database that need to be set manually in 2005?
    What else can I try to test? The main problem is that production SQL Server will be updated god-knows-when and we can't just wait for that.
    Any suggestions/advices are more than welcome.

    ...One more thing is that it's not Process2 table that constantly grows in size but is
    Process1 table, that gets almost 100k records each run....
    Hi,
    It is not clear to me what is that you are doing, but now we have a better understanding on ONE of your tables an it is obviously you will get worse result as the data become bigger. Actually your table look like a automatic build table by ORM like Entity
    Framework, and it's DDL probably do not much your needs. For example if your select query is using a filter on the other column that [setID] then you have no index and the server probably have to scan the entire table in order to find the records that you
    need.
    Forum is a suitable place to seek advice about a specific system (as I mentioned before we are not familiar with your system), and it is more suitable for general questions. For example the fact that you have no index except the index on the column [setID]
    can indicate a problem. Ultimately to optimize the system will need to investigate it more thoroughly (as it is no longer appropriate forum ... but we're not there yet). Another point is that now we can see that you are using [timestamp] column, an this
    implies that your are using this column as a filter for selecting the data. If so, then maybe a better DDL will be to use clustered index on this column and if needed a nonclustered index on the [setID] if it is needed at all...
    what is obviously is that next is to check if this DDL fit
    your specific needs (as i mentioned before).
    Next step is to understand what action do you do with this table. (1) what is your query which become slowly in a bigger data set. (2) Are you using ORM (object relational mapping, like Entity Framework
    code first), and if so then which one.
    [Personal Site] [Blog] [Facebook]

  • Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager

    Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager?
    when I check on Microsoft site it says
    Reports are not upgraded when you upload a report definition file directly to the report server
    or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was
    created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace.
    This is the only way you can upgrade a report definition file.
    Now here is another confusing statement which says
    You can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server
    2012 report server and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains
    unchanged.
    All I want to know is if I deploy a rdl made in 2008 r2 to 2012 will it work on the report manager of
    2012?
    <o:p>
    </o:p>
    Mudassar

    I have tested this fucntionality and can confirm that ssrs 2008 r2 reports work when you deploy them on new ssrs 2012 report manager .
    No Migration is required .
    I didnt even moved report server dbs .All I did is just deployed reports on the report manager and it worked .
    "You
    can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server 2012 report server and it is automatically upgraded on first use. "
    Microsoft needs to correct this the documentation is misleading
    Mudassar

  • SQL Server Setup has encountered the following error: Method not found:'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()

    Hello,
    When I am installing SQL Server 2008 on win7, I encountered an error: SQL Server Setup has encountered the following error: Method not found:'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()‘
    What's the metter? What can I do to deal with it? 
    I need your speed answers.
    Thanks,
    Vicky Song

    Hello,
    Looking at your issue I am wondering if your media is corrupt. 
    What edition of SQL Server you are trying to install? Did you download that media? 
    If you downloaded it, perhaps you should try to download it again.
    Are you able to install that SQL Server 2008 on another machine without any problem?
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Inplace upgrade SCCM 2012 R2 server OS from 2008 R2 to 2012R2 and SQL 2008R2 to 2012

    Hi
    Is it possible to do inplace upgrade?
    I have Windows Server 2008 R2, SCCM 2012 R2 CU1, SQL 2008 R2, WSUS and MDT 2013.
    Can I upgrade to Windows server 2012 R2 and SQL server 2012?
    Are there any catches which I must know before upgrade?
    Do I start upgrade with OS and then SQL?

    The in-place upgrade of the operating system is not supported...
    For a complete list see:
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_UpgradeInfrastructure
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • How to Custom Report using sql server report builder for SCCM 2012 SP1

    Hi ,
    I am new to database, if i want to create a manual report using sql server report builder for SCCM 2012 SP1, what step should i take.
    i want to create a report in which computer name, total disk space, physical disk serial no come together. i already added class (physical disk serial no.) in hardware inventory classes. refer snapshot

    Hi,
    Here is a guide on how to create custom reports in Configuration Manager 2012, it is a great place to start, change to the data you want to display instead.
    http://sccmgeekdiary.wordpress.com/2012/10/29/sccm-2012-reporting-for-dummies-creating-your-own-ssrs-reports/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Unable to start SSIS Projects : SQL Server 2008R2 Dev edition installed on top on SQL Express 2008 with Advanced Services

    Hello,
    I first installed SQL Serrver Express Edition 2008 with Advanced Services (As a part of some client's software)
    Now I have isntalled SQL Server Developer Edition 2008, by selecting ALL features and client tools.
    Now, with BIDS, I can start SSRS and SSAS Projects, but I can't start SSIS Projects.
    I am getting below error message :
    To design Integration Services packages in Business Intelligence Development Studio, Integration Services has to be installed by one of these editions of SQL Server 2008: Standard, Enterprise, Developer, or Evaluation. To install Integration
    Services, run SQL Server Setup and select Integration Services.
    Please let me know how do I resolve this issue "Without un-installing Express Edition installed earlier on my machine"
    Please help !
    Thanks
    DP

    This is a common pitfall with the SQL Express editions. It cannot co-exist. You
    need to un-install the "Express".
    What works is having a VM with Express Tools if I you (strangely) need them.
    Arthur My Blog

  • SQL ENTERPRISE: The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database

    The error below makes absolutely no sense! I'm using Enterprise Core...yet I'm being told I can't use remote data sources:
    w3wp!library!8!03/05/2015-19:08:48:: i INFO: Catalog SQL Server Edition = EnterpriseCore
    w3wp!library!8!03/05/2015-19:08:48:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The edition of Reporting
    Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.;
    Really? This totally contradicts the documentation found here:
    https://msdn.microsoft.com/en-us/library/ms157285(v=sql.110).aspx
    That article says remote connections are completely supported.
    ARGH! Why does this have to be so difficult to setup?!?

    Hi jeffoliver1000,
    According to your description, you are using Enterprise Core edition and you are prompted that you can’t use remote data sources.
    In your scenario, we neither ignore your point nor be doubt with what you say. But actually we have met the case before that even though the SQL Server engine is Enterprise but the reporting services is still standard. So I would recommend you to find the
    actual edition of reporting services you are using. You can find Reporting Services starting SKU in the Reporting Service logs ( default location: C:\Program Files\Microsoft SQL Server\<instance name>\Reporting Services\LogFiles). For more information,
    please refer to the similar thread below:
    https://social.technet.microsoft.com/Forums/en-US/f98c2f3e-1a30-4993-ab41-acbc5014f92e/data-driven-subscription-button-not-displayed?forum=sqlreportingservices
    By the way, have you installed the other SQL Server edition before?
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • Can I use Microsoft SQL Server Management Studio version 11.0 to write SQL queries for "SQL Server Compact 4.0 Local Database"

    Hi, Can I use Microsoft SQL Server Management Studio version 11.0 to write SQL queries for "SQL Server Compact 4.0 Local Database" ?
    When I use Connect Object Explorer, the "Connect to Server" dialog box which pops up has only 4 selections in the Server Type Drop Down List. They are Database Engine, Analysis Services, Reporting Services & Integration Services. I have read
    somewhere that there should be a compact database option. but I do not see it.
    What I would like to do is use free form SQL Queries against the tables in "SQL Server Compact 4.0 Local Database" .
    Once I have validated these queries, then I will use them in my Visual Studio 2012 C#, ASP.NET application. I created the Local Database using Visual Studio 2012 for use by my application.
    Thank you for your help..
    diana4

    Hello,
    With SSMS 2005 we have had the Option to work with SQL CE database files, but not with higher Version of SSMS.
    You can use the free SQL CE Toolbax instead; see
    http://sqlcetoolbox.codeplex.com/
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

Maybe you are looking for