Last week I began to prepare to migrate from SQL Server 2005 to 2008 (x64) by clearing off my staging server and installing SQL Server 2008. I didn’t get far. Based on what I saw, and what I have been reading on the MSDN forums, this is what happened:
- Uninstalled SQL Server 2005
- Started the SQL Server 2008 installer
- .NET Framework 3.5 SP1 was not installed, and it is a prerequisite, so the SQL Server installer attempted to install it first. After that, it attempted to install a hotfix, but did so incorrectly.
- Rebooted, because I was required to do so
- Started the SQL Server installer and was informed that a reboot was required. No amount of rebooting, of course, would allow me to proceed.
There are apparently several possible causes for the problem, each with its own solution. The problem apparently can arise sometimes when .NET Framework 3.5 SP1 was not already installed prior to starting the SQL Server install. Downloading and installing this update first should avoid the problem. Since the full .NET 3.5 SP1 download is large, it should be enough to download just the small “bootstrap” installer if you only have one server to do (or just a few). It will download and install just what you need.
If you already have the problem, you may be able to recover by uninstalling the .NET Framework SP and then downloading and installing it manually. If you have run into this and aren’t able to recover, this thread may help. Pre-installing the SP did not work for me, and I eventually traced the problem to a different program–apparently a printer driver. The above forum thread still helped me by providing location and name of the registry entries for pending file renames. I have run into this “pending rename” issue with a number of different versions of SQL Server, and the only way around it, for better or worse, was to remove the registry entry that was triggering it. While I haven’t seen it in several years now, I guess “it’s baaack.”