2008 SQL Server Dev Edition Installation Error

  • I am trying to install 2008 SQL Server Dev Edition onto a Desktop and am getting an error that I not sure what it is telling me.

    Install:

    - pre-reg's passed

    - selected named instance

    - Analysis Services added current user

    - Reporting Services native mode

    After getting thru all the selections configuring install I get the following error, was wondering if somebody could help, thanks. Also know disk is good since I installed on laptop to verify that

    install would work.

    Any help appreciated

    ...............................................................

    TITLE: SQL Server Setup failure.

    ------------------------------

    SQL Server Setup has encountered the following error:

    There was an error generating the XML document.

    Error code 0x84B10001.

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

  • There should be logs in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap (or similar) that might give more details of what happened. Post any relevent errors here so we can see.

  • Thanks I will check that out, really appreciate the info.

  • DNA_DBA -

    I checked the log files from my 2008 SQl server install. I found an error in the Detail.txt but not sure what it is telling me and wondered if you would take a look ?

    thanks

    (error from detail.txt)

    2010-04-07 22:38:19 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException

    2010-04-07 22:38:19 Slp: Message:

    2010-04-07 22:38:19 Slp: There was an error generating the XML document.

    2010-04-07 22:38:19 Slp: Stack:

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.FlushCache(Boolean removeAllCachedObj)

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.FlushCache()

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Configuration.InstallWizard.SummaryController.SaveData()

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.PageLeaving(PageChangeReason reason)

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Control.OnClick(EventArgs e)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Button.OnClick(EventArgs e)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Control.WndProc(Message& m)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.ButtonBase.WndProc(Message& m)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Button.WndProc(Message& m)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Control.ControlNativewindow.OnMessage(Message& m)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)

    2010-04-07 22:38:19 Slp: at System.Windows.Forms.Nativewindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    2010-04-07 22:38:19 Slp: Inner exception type: System.InvalidOperationException

    2010-04-07 22:38:19 Slp: Message:

    2010-04-07 22:38:19 Slp: There was an error generating the XML document.

    2010-04-07 22:38:19 Slp: Stack:

    2010-04-07 22:38:19 Slp: at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)

    2010-04-07 22:38:19 Slp: at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o, XmlSerializerNamespaces namespaces)

    2010-04-07 22:38:19 Slp: at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o)

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)

    2010-04-07 22:38:19 Slp: Inner exception type: System.Security.Cryptography.CryptographicException

    2010-04-07 22:38:19 Slp: Message:

    2010-04-07 22:38:19 Slp: The system cannot find the file specified.

    2010-04-07 22:38:19 Slp:

    2010-04-07 22:38:19 Slp: Stack:

    2010-04-07 22:38:19 Slp: at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)

    2010-04-07 22:38:19 Slp: at Microsoft.SqlServer.Common.SqlSecureString.WriteXml(XmlWriter writer)

    2010-04-07 22:38:19 Slp: at System.Xml.Serialization.XmlSerializationWriter.WriteSerializable(IXmlSerializable serializable, String name, String ns, Boolean isNullable, Boolean wrapped)

    2010-04-07 22:38:19 Slp: at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterSQLRSConfigurationPublic.Write7_SQLRSConfigurationPublic(String n, String ns, SQLRSConfigurationPublic o, Boolean isNullable, Boolean needType)

    2010-04-07 22:38:19 Slp: at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterSQLRSConfigurationPublic.Write8_SQLRSConfigurationPublic(Object o)

    2010-04-07 22:38:40 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100407_223501\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_

    2010-04-07 22:38:40 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100407_223501\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_

    2010-04-07 22:38:40 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100407_223501\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_

    2010-04-07 22:38:46 Slp: There was an error generating the XML document.

    2010-04-07 22:38:47 Slp: Watson bucket for exception based failure has been created

    2010-04-07 22:38:47 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine

    2010-04-07 22:38:47 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed

    2010-04-07 22:38:47 Slp: Sco: Attempting to get registry value DW0200

    2010-04-07 22:38:48 Slp: Submitted 1 of 1 failures to the Watson data repository

    2010-04-07 22:39:00 Slp:

    2010-04-07 22:39:00 Slp: ----------------------------------------------------------------------

    2010-04-07 22:39:00 Slp:

    2010-04-07 22:39:00 Slp: Error result: -2068774911

    2010-04-07 22:39:00 Slp: Result facility code: 1201

    2010-04-07 22:39:00 Slp: Result error code: 1

  • I am having the same problem? Any solutions?

  • There are a few possible causes...

    1) Faulty install media. This does not often happen, and given the other messages is not likely to be the cause of your problem.

    2) Slow drive holding the install media. If your install media is on a slow network drive, copy it to a local drive. I have seen many install failures where a slow drive was the culprit. If you have a .msi file that fails to install this is an indicator of a slow drive

    3) Slow server. If you are running on a virtual server, try giving it more CPU resource. If you have a service startup failure this could be due to a slow server or lack of memory.

    4) Lack of memory. Without knowing anything about your server configuration, I think this may be the cause of your problem. Monitor memory usage with Task Manager, and if you have less than 100MB free then you should add more memory or stop other tasks that are using memory.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • Well it turns out the issue was an old copy of windows. I bumped up the memory in this process to 4gb and still had the issue. Just had a feeling about the older copy of Windows so I installed a new XP windows on the box and the install went just fine. Unfortunately the box died 2wks later. I purchased a new Dell and installed SQL 2008 on it and all is good. Thanks for the help.

  • After doing some more research online, I was only able to get the install to work after logging on to the box using a user account that had Admin privileges other than the built in Admin account. Weird.

  • That is very strange but glad to hear you got it installed.

    THanks again

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply