{"id":37,"date":"2010-06-05T08:52:37","date_gmt":"2010-06-05T12:52:37","guid":{"rendered":"http:\/\/www.obieta.com\/?p=37"},"modified":"2010-06-05T08:52:37","modified_gmt":"2010-06-05T12:52:37","slug":"sql-server-2008-install-nightmare","status":"publish","type":"post","link":"https:\/\/obieta.com\/?p=37","title":{"rendered":"SQL Server 2008 Install Nightmare"},"content":{"rendered":"<p><span style=\"font-size: 16pt;\"><strong><a class=\"TitleLinkStyle\" rel=\"bookmark\" href=\"http:\/\/mark.michaelis.net\/Blog\/SQLServer2008InstallNightmare.aspx\">SQL  Server 2008 Install Nightmare<\/a><\/strong><\/span><br \/> It all started with an installation of Visual Studio 2008 SP1, which  included SQL Server Express 2005.\u00a0 From there I wished to install SQL  Server 2008 Standard on the default port and upgrade SQL Server 2005  Express to SQL Server 2008 express.\u00a0 Unfortunately, this proved to be a  troublesome desire.\u00a0 I have no idea what the cause is exactly, except  that I was not the only one on my team to have issues.<\/p>\n<p>At this  point, I am not sure the order that things occurred exactly, but I have a  host of error messages and ways to handle them.\u00a0 I can&#8217;t say it will  work for you &#8211; I sure hope you didn&#8217;t have to go through all these to  install SQL Server 2008 &#8211; but I did so I decided to share the  experience.<\/p>\n<p><strong><a title=\"Uninstall\" name=\"Uninstall\"><\/a>Uninstall procedure:<\/strong><\/p>\n<p>The most important step with any failed SQL Server 2008 installation  is uninstalling the failed attempt &#8211; yes, SQL Server 2008 needs to be  uninstalled if an installation fails as it doesn&#8217;t automatically roll  back.<\/p>\n<p>At the moment there is no complete knowledge base article  on how to manually uninstall SQL Server 2008.\u00a0 However, there are  instructions for <a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fsupport.microsoft.com%2fkb%2f909967\" target=\"_blank\" rel=\"noopener noreferrer\">how to uninstall an instance of SQL Server 2005  manually<\/a> and there is a lot of similarity with SQL Server 2008, so  review and follow those instructions were it makes sense.\u00a0 Below is a  list of the steps I followed:<\/p>\n<ol>\n<li>Uninstall the the  installation from <strong>Programs and Features<\/strong>\/<strong>Add  Remove Programs<\/strong>, selecting <strong>Microsoft SQL Server 2008<\/strong> and double clicking to run the uninstaller. (You always need to begin  with this step or the command line equivalent.)\u00a0 Do not use the Windows  Installer Cleanup Tool to remove SQL Server 2008 without first trying to  do so from <strong>Programs and Features<\/strong>\/<strong>Add Remove  Programs<\/strong>. During the uninstall, you can choose (via series of  check boxes), which components of SQL Server 2008 to uninstall &#8211;  including any shared components for when you have multiple instances.\u00a0  In the case of multiple instances, each instance needs to be uninstalled  independently.<\/li>\n<li>Run<br \/> <span style=\"font-family: Consolas;\">SC.EXE query |  find \/i &#8220;SERVICE_NAME: MSSQL&#8221;<\/span><br \/> to verify that there are no  services instances for SQL Server that should have been deleted but  weren&#8217;t.\u00a0 Any items that appear unexpectedly, should be removed with the  command<br \/> <span style=\"font-family: Consolas;\">SC.EXE<\/span> delete &lt;service name&gt;<br \/> Where service name is the name  of the service returned by <span style=\"font-family: Consolas;\">sc.exe query.<\/span><br \/> If  <span style=\"font-family: consolas;\">SC.EXE<\/span> fails to uninstall the services and  there are no other instances of SQL Server installed, delete registry  keys <span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServer<\/span>,  <span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSSQLSERVER<\/span> and <span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSQLAgent<\/span><\/li>\n<li>Search for <span style=\"font-family: consolas;\">&lt;Instance Name&gt;<\/span> in <span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall<\/span>.\u00a0  If you find any, usually on a value called <span style=\"font-family: consolas;\">InstanceId<\/span>,  run<br \/> <span style=\"font-family: consolas;\">MSIEXEC \/X &lt;GUID&gt;<\/span><br \/> where  the <span style=\"font-family: consolas;\">&lt;GUID&gt;<\/span> is the key name  containing the <span style=\"font-family: consolas;\">InstanceId<\/span> value.<\/li>\n<li>Delete  the following registry keys\/values if they exist\n<ul>\n<li><span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL  Server&lt;Feature&gt;.&lt;Instance Name&gt; <\/span><\/li>\n<li><span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL  Server&lt;Instance Name&gt;<\/span><\/li>\n<li><span style=\"font-family: consolas;\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft  SQL ServerInstance NamesSQL&lt;Instance Name&gt;<\/span><\/li>\n<\/ul>\n<\/li>\n<li>Delete  <span style=\"font-family: consolas;\">%ProgramFiles%Microsoft SQL  Server&lt;Feature&gt;.&lt;Instance Name&gt;<\/span> if it exists.<\/li>\n<li>Finally,  search for the <span style=\"font-family: consolas;\">&lt;Feature&gt;.&lt;Instance  Name&gt;<\/span> in the registry and consider deleting any remaining  items. In some cases this involves deleting the value because the other  values within the same key are for a different instance.\u00a0 In other  cases, the entire key will need to be deleted because there is no other  instance data within the key.\u00a0 Hopefully, you won&#8217;t encounter anything  significant, but this is a good final step.<\/li>\n<\/ol>\n<p><span style=\"font-family: consolas;\">&lt;Feature&gt;<\/span> has a value like <span style=\"font-family: consolas;\">MSSQL10<\/span> or <span style=\"font-family: consolas;\">MSAS10<br \/> &lt;Instance  Name&gt;<\/span> is the name of the SQL Server instance you are trying  to uninstall.<\/p>\n<p>Pheww, now that we have completely  uninstalled, lets review potential errors you might encounter:<\/p>\n<p><strong>Error<\/strong>:  A later version of Microsoft SQL Server Compact is already installed.<\/p>\n<blockquote>\n<p>Strange, since all I wanted was to install the SQL  Server 2008 Tools.\u00a0 Here are the steps to correct:<\/p>\n<\/blockquote>\n<ol>\n<li>\n<ol>\n<li>Uninstall all parts of the SQL Server Compact Framework 3.5  SP1.<\/li>\n<li>Rerun SQL Server 2008 install.<\/li>\n<li>After installing  SQL Server 2008 Tools, downloaded and reinstalled the SQL Server  Compact Framework SP1.\u00a0 The tools are located here:<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<ul>\n<li>\n<ul>\n<li><a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyID%3ddc614aee-7e1c-4881-9c32-3a6ce53384d9\">SQL  Server Compact 3.5 SP1 for desktop<\/a><\/li>\n<li><a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyID%3dfce9abbf-f807-45d6-a457-ab5615001c8f%26DisplayLang%3den\">SQL  Server Compact 3.5 SP1 for Devices<\/a><\/li>\n<li><a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyID%3dfa751db3-7685-471b-ac31-f1b150422462%26DisplayLang%3den\">SQL  Server Compact 3.5 SP1 Server Tools (Merge Replication Serve2r Side  Config)<\/a><\/li>\n<li><a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyId%3d07829770-73A7-41E4-880D-E74B1A353623%26displaylang%3den\">SQL  Server Compact 3.5 SP1 Books Online and Samples<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Error:<\/strong> The following error has occurred:  Could not open key: <span style=\"font-family: 'Courier New';\">UNKNOWNComponentsCBFF54E0ED12B0946A1C52E5E82ABC38E7BEEF5F746F8AB9076051A5574<\/span>.\u00a0  Verify that you have sufficient access to that key, or contact your  support personnel. (Errors could be for other GUIDs as well)<\/p>\n<p><strong><img loading=\"lazy\" style=\"border-width: 0;\" src=\"http:\/\/mark.michaelis.net\/Blog\/content\/binary\/SQLServer2008InstallNightmare_F264\/image23.png\" border=\"0\" alt=\"The  following error has occurred: Could not open key:  UNKNOWNComponentsCBFF54E0ED12B0946A1C52E5E82ABC38E7BEEF5F746F8AB9076051A5574.   Verify that you have sufficient access to that key, or contact your  support personnel.\" width=\"616\" height=\"177\" \/><\/strong><\/p>\n<p>Errors could be  for other GUIDs as well including <span style=\"font-family: 'Courier New';\">UNKNOWNComponents493032C95B52CBD448DD2B5A52C50E9A3EC761FD7E06AE4499CE52705CF173EA<\/span>.<\/p>\n<blockquote>\n<p>This error is a permissions error in the registry.\u00a0 If  you search the registry for the first GUID you will find the key is  likely mapped to <span style=\"font-family: 'Courier New';\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData&lt;user  SID&gt;Components&lt;GUID&gt;<\/span>.\u00a0 Beneath this key is a sub key  for the second GUID.\u00a0 However, selecting the subkey will result in an  access denied message.<\/p>\n<p>To correct the problem:<\/p>\n<p>1. Verify  that you are running RegEdit as administrator (to avoid UAC issues with  Windows Vista and Windows 3008+).<\/p>\n<p>2. Edit the permission of the  parent key(<span style=\"font-family: 'Courier New';\">HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData&lt;user  SID&gt;Components<\/span>) and click the <strong>Advanced<\/strong> button. (Optionally, you could edit the permissions on the parent GUID (<span style=\"font-family: 'Courier New';\">CBFF54E0ED12B0946A1C52E5E82ABC38<\/span> in my  example) but the same problem is likely to exist with other keys so you  may as well deal with this in mass.)<\/p>\n<p><a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fmark.michaelis.net%2fBlog%2fcontent%2fbinary%2fSQLServer2008InstallNightmare_F264%2fimage.png\"><img loading=\"lazy\" style=\"border-width: 0;\" src=\"http:\/\/mark.michaelis.net\/Blog\/content\/binary\/SQLServer2008InstallNightmare_F264\/image_thumb.png\" border=\"0\" alt=\"image\" width=\"473\" height=\"252\" \/><\/a><\/p>\n<p>3.\u00a0 From  the Advanced dialog, select the <strong>Owner<\/strong> tab and check the  <strong>Replace owner on subcontainers and objects<\/strong> check box.\u00a0  Also, verify that System is the owner (else add System and be sure to  select it so it will become the owner).<\/p>\n<p>4. Next  click <strong>Apply<\/strong>.<\/p>\n<p>4.\u00a0 You may be  presented with an error dialog, &#8220;Registry Editor could not set owner on  the key currently selected, or some of its subkeys.&#8221;\u00a0 You can safely  ignore this warning as long as you are then able to view the subkey.\u00a0 If  not :(, you may have to follow the same process but in safe mode or  download <a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2ftechnet.microsoft.com%2fen-us%2fsysinternals%2fbb896653.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">Process Explorer<\/a> and search for any process that is  holding onto the key so that you can shut it down.\u00a0 (The idea that a  process is preventing you from viewing the key is a stretch in my mind  but I have had heard the Platform team of Microsoft&#8217;s product support  group suggest this.)<\/p>\n<p>5.\u00a0 Lastly, select the  &#8220;Effective Permissions&#8221; tab and verify that both your own User Id and  the System user have <strong>Full Control<\/strong>.\u00a0 If not, add both  users via the <strong>Permissions<\/strong> tab.<\/p>\n<p>If  this still fails, consider resetting registry permissions back to the  default settings using the following command:<\/p>\n<pre class=\"csharpcode\">    Registry security: secedit \/configure \/cfg %windir%infdefltbase.inf \/db defltbase.sdb \/verbose \/areas REGKEYS<\/pre>\n<p>.csharpcode, .csharpcode pre { \tfont-size: small; \tcolor: black; \tfont-family: consolas, &#8220;Courier New&#8221;, courier, monospace; \tbackground-color: #ffffff; \t\/*white-space: pre;*\/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt  { \tbackground-color: #f4f4f4; \twidth: 100%; \tmargin: 0em; } .csharpcode .lnum { color: #606060; }<\/p>\n<\/blockquote>\n<p><strong>Error:<\/strong> SQL Server setup has encountered the  following error. sku<\/p>\n<blockquote>\n<p><a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">Manually  uninstall<\/a> SQL Server 2008 installation and try installing again.<\/p>\n<\/blockquote>\n<p><strong>Error:<\/strong> Error 1316.A network error occurred while  attempting to read file <span style=\"font-family: 'Courier New';\">ssceruntime-enu.msi<\/span>.<\/p>\n<blockquote>\n<p><a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fconnect.microsoft.com%2fSQLServer%2ffeedback%2fViewFeedback.aspx%3fFeedbackID%3d363055\" target=\"_blank\" rel=\"noopener noreferrer\">Connect mentions this error<\/a>.\u00a0 I followed a similar  procedure.<\/p>\n<ol>\n<li>Extract the <span style=\"font-family: 'Courier New';\">ISO<\/span> file or copy the SQL  Server CD onto the local drive.<\/li>\n<li>Copy the .<span style=\"font-family: 'Courier New';\">&lt;platform&gt;SetupSSCERuntime.msi<\/span> file to  <span style=\"font-family: 'Courier New';\">SSCERuntime-enu.msi<\/span> within the same  directory.\u00a0 This seemed appears to work around the error.\u00a0 I haven&#8217;t  tested this exhaustively, but I suspect this is a 64-bit problem only so  the &lt;platform&gt; directory is most likely <span style=\"font-family: 'Courier New';\">x64<\/span>.  (Please comment and let me know if you see this on other platforms.)<\/li>\n<\/ol>\n<\/blockquote>\n<p><strong>Error<\/strong>: Error result: -2068578301<\/p>\n<blockquote>\n<p><a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">Manually  uninstall<\/a> SQL Server 2008 installation and try installing again<\/p>\n<\/blockquote>\n<p><strong>Error<\/strong>: SQL Server installation failed. To continue,  investigate the reason for the failure, correct the problem, uninstall  SQL Server, and then rerun SQL Server Setup.<\/p>\n<blockquote>\n<p>Sometimes, the error log points to a <a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fwww.microsoft.com%2fproducts%2fee%2ftransform.aspx%3fProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.2\" target=\"_blank\" rel=\"noopener noreferrer\">message indicating there was a network error<\/a>.\u00a0  During the occasions that I encountered this error message within the  log, my installation failed with two red X icons in the concluding  dialog, only one of which had a corresponding message (I wish I had  taken a screen shot.)\u00a0 The solution for me was to <a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">manually uninstall<\/a>.<\/p>\n<\/blockquote>\n<p><strong>Error<\/strong>: Could not find the Database Engine startup  handle.<\/p>\n<blockquote>\n<p>This error appears after an installation completes unsuccessfully and  a different error dialog appeared earlier in the installation.\u00a0 <a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">Manually uninstall<\/a> all the instance related installations items, address the previous  dialog, and re-attempt the install.<\/p>\n<\/blockquote>\n<p><strong>Error (during repair):<\/strong> The SQL Server feature  &#8216;SQL_Engine_Core_Inst&#8217; is not in a supported state for repair, as it was  never successfully configured. Only features from successful  installations can be repaired. To continue, remove the specified SQL  Server feature.<\/p>\n<blockquote>\n<p>This error appears if you attempt a repair of a failed installation.\u00a0  The work around it to <a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">manually uninstall<\/a> the all items related to the instance, and re-attempt the install by  addressing the original error.<\/p>\n<\/blockquote>\n<p><strong>Error:<\/strong> A MOF syntax error occurred.<\/p>\n<blockquote>\n<p><a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">Manually  uninstall<\/a> and then re-attempt the install.<\/p>\n<\/blockquote>\n<p><strong>Error<\/strong>: SQL Express 2008 ERROR: Failed to generate a  user instance of SQL Server and<br \/> <strong>Error:<\/strong> Failed to  generate a user instance of SQL Server due to a failure in starting the  process for the user instance. The connection will be closed.&#8221;<\/p>\n<blockquote>\n<p>Okay, admittedly this error doesn&#8217;t appear during install, but it is  an install related error none the less.<\/p>\n<p>Recently I upgraded my SQL Express 2005 instance (installed by Visual  Studio 2008) to SQL Server Express 2008.\u00a0 (Visual Studio 2008 Express  editions will automatically be upgraded when installing Service Pack 1,  but not so with all other instances.)\u00a0 After upgrading, none of my data  driven unit tests were successfully passing.\u00a0 Instead, they were failing  with the message:<\/p>\n<blockquote>\n<p>The unit test adapter failed to connect to the data source or to read  the data. For more information on troubleshooting this error, see &#8220;<a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fgo.microsoft.com%2ffwlink%2f%3fLinkId%3d62412\" target=\"_blank\" rel=\"noopener noreferrer\">Troubleshooting Data-Driven Unit Tests<\/a>&#8221; in the MSDN  Library.<br \/> Error details: Failed to generate a user instance of SQL  Server due to a failure in starting the process for the user instance.  The connection will be closed.&#8221;<\/p>\n<\/blockquote>\n<p>It took some sleuthing to determine the solution.\u00a0 Firstly, I checked  the error files located in my <span style=\"font-family: 'Courier New';\">%USERPROFILE%Local  SettingsApplication DataMicrosoftMicrosoft SQL Server  DataSQLEXPRESS<\/span> (the connecting user&#8217;s SQL Express data  directory) directory.\u00a0 That indicated errors were in loading the <span style=\"font-family: consolas;\">modal.mdf<\/span> and corresponding log file within afore  mentioned directory.\u00a0 However, when connecting to the SQL Express  instance from SQL Server Management Studio, there were no such issues.\u00a0  This was because the instances connected to by SQL Server Management  Studio were in the <span style=\"font-family: 'Courier New';\">%PROGRAMFILES%Microsoft SQL  Server<\/span> directory.<\/p>\n<p>Generally, when a new MDF file is connected to by SQL Express, it  copies the master, model, MSDB, and tempdb databases (mdf and log files)  into the connecting user&#8217;s SQL Express data directory.\u00a0 (This is  frequently why the first time connecting for each user takes longer.)\u00a0  Such a copy was unnecessary in my case because the databases already  existed.\u00a0 Unfortunately, the databases were from the SQL Server Express  2005 instance, and not the upgraded database from SQL Server 2008  Express.<\/p>\n<p>To correct the problem, I<\/p>\n<ol>\n<li>Shut down SQL Server Express<\/li>\n<li>Deleted the users SQL Express directory &#8220;%USERPROFILE%Local  SettingsApplication DataMicrosoftMicrosoft SQL Server  DataSQLEXPRESS&#8221;<\/li>\n<li>Restarted SQL Server Express:<\/li>\n<\/ol>\n<p>Here&#8217;s a cmd script for what is needed:<\/p>\n<blockquote>\n<p>SC.EXE stop &#8220;MSSQL$SQLEXPRESS&#8221;<br \/> CHOICE \/C:N \/D:N \/N \/T:5<br \/> <span style=\"font-family: 'Courier New';\">RD \/S \/Q &#8220;%USERPROFILE%Local SettingsApplication  DataMicrosoftMicrosoft SQL Server DataSQLEXPRESS&#8221;<br \/> <\/span>SC.EXE  start &#8220;MSSQL$SQLEXPRESS&#8221;<\/p>\n<\/blockquote>\n<\/blockquote>\n<p><strong>More Errors<\/strong>:<\/p>\n<blockquote>\n<p>Unfortunately, this is not anything even close to an exhaustive list  of errors.\u00a0 If you have other messages I have not covered, the key place  to check is <span style=\"font-family: Consolas;\">%Programfiles%Microsoft sql  server100Setup bootstrapLog&lt;<\/span><var><span style=\"font-family: Consolas;\">DateTime&gt;<\/span>.<\/var> To begin, open the <span style=\"font-family: Consolas;\">Summary_&lt;computername&gt;_&lt;DateTime&gt;.txt<\/span> file to see an overview of the results.\u00a0 If that doesn&#8217;t help, consider  reviewing one of the <span style=\"font-family: consolas;\">Detail*.txt<\/span> files.\u00a0  These errors are all addressed in <a href=\"http:\/\/mark.michaelis.net\/Blog\/ct.ashx?id=e0b70f97-72df-4bc6-8775-8523483c38a2&amp;url=http%3a%2f%2fsupport.microsoft.com%2fkb%2f909967\" target=\"_blank\" rel=\"noopener noreferrer\">KB909967 &#8211; How to troubleshoot SQL Server 2008 Setup  issues<\/a>.<\/p>\n<p>Another item that seemed to cause instability in my SQL Server 2008  installation was mounting the SQL Server 2008 iso file (especially  mounting it over the network).\u00a0 I recommend that you extract the ISO  into a local directory and then installing from the local directory.<\/p>\n<p>Overwhelmingly, the correction is to <a href=\"http:\/\/mark.michaelis.net\/Blog\/#uninstall\">manually uninstall<\/a> the attempted install instance.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>SQL Server 2008 Install Nightmare It all started with an installation of Visual Studio 2008 SP1, which included SQL Server Express 2005.\u00a0 From there I wished to install SQL Server 2008 Standard on the default port and upgrade SQL Server 2005 Express to SQL Server 2008 express.\u00a0 Unfortunately, this proved to be a troublesome desire.\u00a0 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[6,1],"tags":[],"_links":{"self":[{"href":"https:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/posts\/37"}],"collection":[{"href":"https:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=37"}],"version-history":[{"count":0,"href":"https:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/posts\/37\/revisions"}],"wp:attachment":[{"href":"https:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}