I finally have more than 5 days at home to get some work done which was on the back burner. 1 major task I will complete is to make my home office lab accessible remotely. I’ll do this with either Direct Access (if I can get the consecutive IP addresses), TS Gateway, or Live Mesh failing the previous 2.
I had been using both dedicated lab systems previously for other labs and have installed SQL 2005 which had since been completely uninstalled (or so i thought).
I dedicated 1 physical 64-bit system which supports 4GB of RAM and does not support hardware virtualization to be my DC, SQL server and SCVMM server.
I decided to install SQL 2008 SP1 as the DB host.
The install for SQL 2008 is fairly straightforward and I have done it before on several occasions. I was plagued with several issues… All in all, this fight took 3 days of off and on time.
Firstly, I was not able to change the default path for the Shared Features, I kept running into what I found was a known issue with the RTM installer, see blow:
http://support.microsoft.com/kb/955458
Thing is, this is not consistent. I have used the same install media on this same system with no issue… weirdness…
That was one issue.
Next, the issue was getting Reporting Services installed in SQL 2008. The setup wizard would fail to install RS correctly (it would list the failure). It would still install the SQL Reporting Services windows service and would list it as an installed component in the instance for a repair. Yet, I was unable to get it to work…
After numerous sanity checks and idea bouncing with my colleagues and fellow MVPs Wes MacDonald and Edwin Sarmiento, I figured it was time to remove SQL entirely using whatever ‘manual’ procedures are out there and try again.
The manual uninstall procedure can consist of actually using the uninstaller from Add/Remove programs or Programs and Features but often does not and is not a clean process as this can involve registering/unregistering DLL files, deleting registry keys, etc…
After removing all components of SQL 2008, I scoured the system for any possible remnants of SQL 2005 using this procedure:
http://support.microsoft.com/kb/909967
Interesting, I found a surprise at this step:
Step 2: Run the command to uninstall the SQL Server components
At a command prompt, run the following command:
"%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove"
Somehow, there was an instance of SQL 2005 reporting services hiding in the woodwork! So I removed it…
I diligently made sure that I rebooted my system after every uninstall/reinstall…
Now, when I attempted to reinstall SQL, I still could not get reporting services to install but discovered that when I attempted to run a modify install to add/remove features, I would receive an error stating that although I was asking to modify the default instance of MSSQLSERVER, my instance of MSSQLSERVER had an instance ID of 1.
Wow, somehow the SQL installer was interpreting that there was still a SQL instance in my system somehow. OK, because I am not a SQL guy, I pinged fellow MVP Edwin Sarmiento for another sanity check to determine if simply deleting all SQL files from my system and uninstalling SQL 2008 again should purge my system from any SQL instances. Edwin confirmed yes… and suggested I backup any databases and logs if I wanted to restore the data later which was very diligent of him but I did not need the existing data anyways and so did not mind losing it.
Edwin also informed me that in his experience the RTM installer was ‘buggy’ and I should patch the install by slipstreaming my install media as this has solved many problems for him in the past. Since this seemed reasonable and in line with some of the issues I had been seeing, I went for it.
The procedure to slipstream the SQL 2008 install media is here:
http://blogs.msdn.com/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx
This process took several hours with all of the data copying I needed to do and the media creating in the end needed a dual layer DVD since the slipstreamed media is larger than 4.7GB.
OK, next I made sure after uninstalling all SQL 2008 elements from Programs and Features that I deleted all SQL folders and files from all drives on my system to eliminate the possibility of the system detecting any SQL instances.
Now, I tried again installing this time with the slipstreamed media. I selected database services, reporting services, and management components. The system also did not complain when I changed the default install path for the features and databases. This was a good sign…
I followed through and successfully completed the install with Reporting Services as well this time!
Since I slipstreamed my install media, I also did not need to go back and service pack my install. Hopefully this experience will help someone not lose 3 days like I did!