Mega Problems installing SQL Server 2008 R2 Developer

  • I normally install SQL Server 2008 R2 Developer without any problems, for example on an unupdated version of Windows XP. I have also installed it on Windows 7 which may have had the initial 500-600MB or so of updates although I am not sure if these help with a new installation of SQL Server 2008 R2 Developer. I think that version may have had Visual Studio 2010 or 2008 on it first, although I can't remember the sequence of installs.

    I had a problem of not being able to go into SSIS a few days ago. This may have been something to do with SQL Server 2012 RC being uninstalled and problems with shared .dll's. After much irritation I did a clean install of Windows 7 SP1.

    I then tried to install SQL Server 2008 R2 Developer on Windows 7 HP (without initial updates) but this came up with errors. I barely slept over the weekend as the whole reinstallation process of my laptop has taken ages.

    If I try to install Visual Studio 2008, on its own, a msg appears:

    An earlier version of Microsoft Visual Studio 2008 has been detected on the system that must be updated to SP1 before installation can proceed. Please update all other versions of Visual Studio 2008 to SP1 by visiting Microsoft Update and then install Visual Studio 2008 Express SP1.

    At the same time Visual Studio 2008 SP1 (which I downloaded as does not install now) I get the following message:

    A compatible version of Visual Studio 2008 was not detected on the system. This update is designed for only the Microsoft Visual Studio 2008 (ENU) product family, and is not compatible with any Express editions.

    Should this not install without problems on a Windows 7 HP SP1 that has not been updated? The initial Windows Updates don't seem to have anythhing to do with impacting on this installation and are just security updates for Visual C++ 2005-2008.

    If this happens again I will just have to try to problem solve, but I would rather do another install now on a clean install of Windows 7 as the whole process of trying to fix the existing setup and previous setup is way to complicated and I have seen solutions involving copying shared .dll's, going into the registry and restore points (I tried the shared .dll's and restore points with no luck). I don't favour these solutions and would like to see if there is something that can be installed first as once SQL Server is installed it is very difficult to uninstall or correct.

    Many thanks for any suggestions to how to prepare for a clean install of SQL Server 2008 R2 Developer on a clean install of Windows 7 HP SP1.

  • I resolved the installation problems in the following way:

    •Windows 7 HP SP1 clean install.

    •Get all updates from Windows update.

    •Start install of SQL Server 2008 R2 Developer (in my case from USB drive).

    •Run System Configuration Checker within setup.

    •Start Installing SQL Server.

    Error msg appears: “Another version of Microsoft Visual Studio 2008 has been detected on this system that must be updated to SP1. Please update all Visual Studio 2008 installations to SP1 level, by visiting Microsoft Update” but installation continues. Installs but without SSMS, Integration Services etc.

    •Run SP1 for SQL Server 2008 R2 SP1 (SQLServer2008R2SP1-KB2528583-x64-ENU) and SQL Server 2008 R2 SP2 (SQLServer2008R2SP2-KB2630458-x64-ENU). These files were previously downloaded as exe’s.

    •Run Visual Studio 2008 SP1 (VS2008SP1ENUX1512962) previously downloaded and saved as an iso on a dvd.

    •Install SQL Server again. Add Features (select all features that were missing from the first install).

    •Run SQL Server 2008 R2 SP2 (SQLServer2008R2SP2-KB2630458-x64-ENU) again.

    •Bingo!

    I imagine that SQL Server 2008 R2 SP2 (SQLServer2008R2SP2-KB2630458-x64-ENU) could have been installed at the end and it was not necessary to install SQL Server 2008 R2 SP1 (SQLServer2008R2SP1-KB2528583-x64-ENU), but this sequence of events worked for me.

Viewing 2 posts - 1 through 1 (of 1 total)

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