Home Dashboard Directory Help
Search

.NET Framework 3.5 sp1 istallation fails on Windows Server 2008 r2 and Windows 7 by Maxim Osipov


Status: 

Closed
 as Won't Fix Help for as Won't Fix


3
0
Sign in
to vote
Type: Bug
ID: 534192
Opened: 2/17/2010 4:39:06 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

If setup contains .NET Framework 3.5 sp1 bootstrapper it fails on Windows Server 2008 r2 and Windows 7 with message "You must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5 SP1". Tab "Details" contains the following:
Component .NET Framework 3.5 SP1 has failed to install with the following error message:
"Asia"

The following components failed to install:
- .NET Framework 3.5 SP1

See the setup log file located at 'C:\Users\ADMINI~1\AppData\Local\Temp\2\VSDFC09.tmp\install.log' for more information.
Details
Sign in to post a comment.
Posted by PRADIIP SINGH on 8/30/2011 at 5:52 AM
I had the same issue when u was trying to install the SQL server 2008 but idid fix this issue following the below post.


http://blog.webhostingdiscussion.net/webhosting/you-must-use-the-role-management-tool-to-install-or-configure-microsoft-net-framework-3-5.htm
Posted by Doug_Ivison on 7/26/2011 at 4:23 PM
If you're getting the error message "You must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5 SP1.", and it's making an install fail, note that you can follow the steps at this link:
http://blogs.msdn.com/b/sqlblog/archive/2010/01/08/how-to-install-net-framework-3-5-sp1-on-windows-server-2008-r2-environments.aspx

I used "Method 1: Using Server Manager Interface".

(In my case: I needed Visual C# 2008 Express, to be compatible with our vendor-provided software. The install for Visual C# 2008 Express was failing, until I followed the steps above, to enable features for .NET Framework 3.5 sp1.)
Posted by Microsoft on 2/19/2010 at 2:23 PM
Ah. Glad that it worked for you. Given that we're at our final milestone for Visual Studio 2010, we don't have plans to fix this for the next release. We will document this behavior on MSDN as a workaround.

I'm going to close this issue. If you have additional questions, feel free to send me an email. My email is candyc@microsoft.com. Thank you.

Candy Chiang
Program Manager
Visual Studio
Posted by Maxim Osipov on 2/18/2010 at 11:46 PM
Thank you for your answer.

I've done exactly like you said to solve the problem. And it works perfectly. Sorry, I forgot to mention this fact when opening the bug.
I just thought you could modify DotNetfx35setup.exe the way it runs command line "ocsetup Netfx3" itself and nobody needs to add his own additional EXE and change package.xml.
Posted by Microsoft on 2/18/2010 at 11:52 AM
Hi,

Thank you for reporting this issue. Given that .NET Framework 3.5 SP1 is enabled by default on Windows 7, we suspect that not a lot of people will hit this issue. If they do, the error message is actionable and should guide them to the resolution.

If you want to enable .NET Framework 3.5 SP1 automatically with the bootstrapper, you would have to modify the product.xml of the 3.5 bootstrapper package by doing the following:
- Create an EXE that runs this command line "ocsetup Netfx3"
- Navigate to \Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFX35SP1
- Drop the EXE in that directory
- Navigate under the en folder and open the package.xml with admin privilage
- Add a <Command> element inside <Commands> to run the EXE

Please let us know if you have additional questions. We will leave this bug opened for another 3 days.

Thank you.
Posted by Microsoft on 2/17/2010 at 10:40 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Microsoft on 2/17/2010 at 7:02 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.