.Net Framework 3.0 installation - WCF failure
The most common problem i have seen with the .Net Framework 3.0 installation is failure on Windows Communcation Foundation (which is hidden). The error message that you see is generic and just says that there is a failue and do you want to report this to microsoft.
Again to get more details regarding the failure, please check my other post General installation issues - .Net/ Visual Studio/ TFS / Service Packs.
Usually the failure point will take you to the file dd_wcf_ret*****.txt. If you look up, you see the following text above the "value 3" string
------------------------------------------------------
MSI (s) (2C:54) [17:13:18:781]: Executing op: ActionStart(Name=DD_CA_InstallXwsRegExe_RB_X86.3643236F_FC70_11D3_A536_0090278A1BB8,,)
MSI (s) (2C:54) [17:13:18:781]: Executing op: CustomActionSchedule(Action=DD_CA_InstallXwsRegExe_RB_X86.3643236F_FC70_11D3_A536_0090278A1BB8,ActionType=1345,Source=BinaryData,Target=QuietExec,CustomActionData=C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /u /x /y /v;dummy;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
MSI (s) (2C:54) [17:13:18:781]: Executing op: ActionStart(Name=DD_CA_InstallXwsRegExe_X86.3643236F_FC70_11D3_A536_0090278A1BB8,,)
MSI (s) (2C:54) [17:13:18:781]: Executing op: CustomActionSchedule(Action=DD_CA_InstallXwsRegExe_X86.3643236F_FC70_11D3_A536_0090278A1BB8,ActionType=3073,Source=BinaryData,Target=QuietExec,CustomActionData=C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /r /x /y /v;dummy;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
MSI (s) (2C:A4) [17:13:18:781]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI6.tmp, Entrypoint: QuietExec
MSI (s) (2C:68) [17:13:18:781]: Generating random cookie.
MSI (s) (2C:68) [17:13:18:781]: Created Custom Action Server with PID 1704 (0x6A8).
MSI (s) (2C:7C) [17:13:18:812]: Running as a service.
MSI (s) (2C:7C) [17:13:18:812]: Hello, I'm your 32bit Elevated custom action server.
MSI (s) (2C:54) [17:13:22:828]: User policy value 'DisableRollback' is 0
MSI (s) (2C:54) [17:13:22:828]: Machine policy value 'DisableRollback' is 0
Action ended 17:13:22: InstallFinalize. Return value 3.
--------------------------------------------------------------
Also the file dd_dotnetfx3error.txt would have an entry , something like
[09/20/07,17:21:25] Windows Communication Foundation: [2] Error: Installation
failed for component Windows Communication Foundation. MSI returned error code
1603
[09/20/07,16:23:03] WapUI: [2] DepCheck indicates Windows Communication Foundation
is not installed.
To go around this issue
1) Log into the machine using Windows Administrator credentials. Download the Full .net Framework 3.0 setup from the link
or go to the link https://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en and scroll down to the end, to find links to the full download. The setup file size you would have will be 50.3 MB.
2) Reboot the machine in Windows Diagnostic mode using the steps mentioned in the post
General installation issues - .Net/ Visual Studio/ TFS / Service Packs and try the installation.
3) If the step 2) does not succeed, its a good idea to verify the existing .Net 2.0 installation and see if it is not corrupt. If its corrupt its a good idea is to repair/ un-install/ re-install 2.0 and then try .Net 3.0 installation.
If the steps do not help, you can see in and around the point of failure in the installation log to see what is the action being performed when the failure happened. For ex: there might be an issue with IIS metabase being corrupt in which case you would need to re-install IIS.
I have handled another case recently where un-installing IIS resolved the issue.We were curiuos to know what does the .Net 3.0 installation has to do with the IIS....the reason is
The WCF installation setup configures IIS to support web-hosted activation (where IIS automatically launches a service process when a request is received); however, if IIS is uninstalled, it skips this step.