May 25, 2010 at 3:41 am
There are numerous people who have reported they cannot install .Net 3.5 SP1 on top of a .Net 2.0 installation. Typically this can happen if there has been a lot of install and uninstall activity between the two .Net installs.
Most often this happens when people upgrade Visual Studio. There are a lot of posts on some of the VS forums about this problem. (More people have VS than SQL, so most of the posts are in VS forums.) There is a tool from Microsoft that is supposed to repair the .Net 2.0 installation so you can put .Net 3.5 SP1 on top of it, but my experience is this tool does not always work.
We had this problem on our developer boxes when we upgraded to VS 2008. 90% of the boxes upgraded without any problem. About half of the remaining boxes allowed the upgrade to proceed after running the repair tool. For the rest of the boxes (including mine :() we had to re-install Windows.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 6, 2010 at 9:57 am
Hi,
has anyone found a solution to this problem?
I also need help.
September 7, 2010 at 12:09 am
Dear Friend,
please check prerequisite SQL Server 2008 on your system ...
please refer the belwo URL
http://msdn.microsoft.com/en-us/library/ms143506.aspx
Varinder Sandhu
http://varindersandhus.blogspot.com/
Varinder Sandhu,
http://www.varindersandhu.in/
September 10, 2010 at 2:33 am
I had the same problem and was trying to install the 32bit SQL2008 Enterprise Eval onto the 64bit Windows Server 2008 Enterprise Eval. Got the same error as everyone else.. "Microsoft .NET Framework 3.5 Installation has failed SQL Server 2008 Requires.NET framework 3.5 to be installed"
I removed all .NET framework installations and downloaded the 64bit SQL2008 Enterprise eval ran the installation and let SQL setup install .NET Framework 3.5 and it worked for me.
Hope this Helps
Andrew
September 20, 2010 at 4:00 am
I am glad this worked for Andrew, but I would be cautious about doing this work on a Production box.
Doing repeated install /uninstall / install processes can leave your system in a state that is not reproducible unless you follow exactly the same sequence of installs and uninstalls. If you have to rebuild a production box then typically you will just install a working set of software, and not repeat all of your old uninstalls and reinstalls. This could mean your rebuilt box might behave differently to your old box.
My advice is if you have this type of install failure on a Production box then start by rebuilding the operating system and install just what you need to the new OS. This way you know that whatever you end up using is reproducible if the current hardware fails.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 20, 2010 at 4:25 am
I absolutely agree with EdVassie, I meant to imply that the problem for me was that the 32bit version did not work with the 64bit system, not that you should necessarily be un-installing and re-installing.
October 25, 2010 at 12:38 pm
I got same issue on windows server2008. I fixed it by enabling the windows powershell 2.0 and then restarting the server.
Viewing 7 posts - 46 through 53 (of 53 total)
You must be logged in to reply to this topic. Login to reply