SQL Server SP1 Setup: Does it really need a beta version of .Net 4?

Posted by OmegaMan at October 7, 2009

Category: Bug Reports

Tags: ,

BabyWaitingI  upgraded my development box to Windows 7 and ignored, whistled past the graveyard as it were, the warning that SQL Server 2008 should be uninstalled due to incompatibilities. Upon the new OS install/upgrade I ventured out and tried to bring up the management studio. Much to my chagrin it crapped out on me, ya chagrin thats it.

So with that darned internet so handy I researched came to the conclusion, from the advice of the internet millions that SP1 should be installed to get it to work on Windows 7. Here is what greeted me for my efforts once as I attemped install:

SP1 2008

Maybe you are reading this in the future where there is a flying car in every drive way and hanging a television on a wall is really passé because the wall is a TV; but as of this writing .Net 4 is only in beta.

So here is the text (a little trick which one can do is that on most dialogs one can do CTRL-C and get the text copied to the clipboard) as received:

—————————
setup.exe – .NET Framework Initialization Error
—————————
To run this application, you first must install one of the following versions of the .NET Framework:

  v4.0.20506

Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework.

So I leave it up to you my small but loyal (?) readership what is going on? Here is what I know

  1. Upgraded from Vista to Windows 7.
  2. Visual Studio 2010 version is installed but doesn’t run. So there is a version of .Net 4 on my system…
    NetVersions
  3. It all worked before I upgraded. 😉

Thoughts?

Share

8 Comments

  1. Justin Etheredge says

    It definitely does not require .NET 4.0 beta 1. My bet is that since VS2010 and .NET 4.0 will not survive a Windows 7 update (see (Scott Hanselman’s) Vista Users – Uninstall Visual Studio 2010 Beta 1 before upgrading to Windows 7. you have a corrupted version of .NET 4.0 beta 1 on your machine and therefore it is causing issues for you.

    (Edit: Updated Link to work)

    Reply
  2. Damien Guard says

    So… Windows 7 has probably interfered with the default version of .NET and/or some components in the system32 folder which is likely meaning SQL is ending up with a later version of .NET framework than it actually wants.

    [)amien

    Reply
  3. Damien Guard says

    Oops.. I’d reinstall .NET Framework 3.5 SP1

    [)amien

    Reply
  4. […] This post was mentioned on Twitter by Ahmed Halwagy. Ahmed Halwagy said: SQL Server SP1 Setup: Does it really need a beta version of .Net 4? http://bit.ly/C42se #sqlserver #.net4.0 […]

    Reply
  5. omegaman says

    Thanks for the thoughts guys.

    My bad for ignoring the warning in the first place. Though the Hanselman article is of note; that one is a good piece of advice.

    I am going to simply move off my data files and re-image my machine. You guys know that us developers go through machines like gypsies.

    My main concern is running SQL Server 2008 locally on Windows Seven on my development box. Is that possible?

    I have Hyper-V running on a server box I have recently built and will test out an install of SS2008 on a Virtual Windows 7 before committing too much time.

    My develoment process needs a local instance of SS because I like to put the databases on an external drive and carry them between two machines when I develop applications for clients.

    Reply
  6. Way2tired says

    Have you tried just uninstalling .Net 4/Vs 10, then trying to re-setup sql 2008? if its getting confused, and you’re already at that ‘well, re-install windows’ state, why not try it?

    Reply
  7. omegaman says

    SQL Server would not uninstall and reported the same dialogue when I tried. I have since blown away my drive and installed a fresh copy of Windows 7 so going the route of uninstall VS2010 beta is an unknown. Thanks for the thought though…

    Reply
  8. JAn says

    Hi…

    I fixed my problem, simply uninstall .net 4 and reinstall it again….

    It will correct any problems you are experiencing.

    Reply

Leave a comment

(required)
(required) (will not be published)

This site uses Akismet to reduce spam. Learn how your comment data is processed.