Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Framework 4.0 Installation might take a long time to install when topology includes Trusted Domains (aspnet_regiis.exe)
Article ID: 2591399 - View products that this article applies to.
Install framework 4.0 on a workstation or server which is a member of a domain
Network traces will show a LSA RPC call for LookupName to a DC (domain controller) with slow response to the query.
The problem is caused by a dependency to query for account information on a DC and potentially trusted domains for domain joined machines.
Resolving the trusted domain communication is beyond the scope of this article. To work around the problem as it applies to the installation of the Framework 4.0 consider the following:
· Save the installation files for the Framework 4.0 on the local machine. Temporarily disconnect it from the network during the installation.
· Follow the instructions on KB 818024
(http://support.microsoft.com/kb/818024). Depending on the target operating system either change the registry entry or apply the hotfix.
· Allow installation to proceed while waiting through the additional time.
(http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx)for more information on ASP.NET IIS Registration Tool (Aspnet_regiis.exe).
(http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718)- Microsoft .NET Framework 4 (Standalone Installer)
(http://support.microsoft.com/kb/818024)- KB 818024 How to restrict the lookup of isolated names in external trusted domains by using the LsaLookupRestrictIsolatedNameLevel registry entry
The MSI verbose log, usually found in the %temp% user folder might look like this:
MSI (s) (90:AC) [16:37:34:907]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI33DE.tmp, Entrypoint: QuietExec05/09/11 16:37:35 DDSet_Entry: QuietExec05/09/11 16:37:35 DDSet_Status: CustomActionData: 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru;15;C:\Windows\Microsoft.NET\Framework64\v4.0.30319\'05/09/11 16:37:35 DDSet_Status: Command line: 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru'05/09/11 16:37:35 DDSet_Status: Directory: 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\'05/09/11 16:37:35 DDSet_Status: Successfully created process.05/09/11 16:37:35 DDSet_Status: Redirected process output:[----------BEGIN----------[Start installing ASP.NET (4.0.30319)]---------- END ----------]05/09/11 17:37:35 DDSet_Error: Process forcibly terminated: Time=3600.0029 exceeded maximum time of 3600.0000 seconds.05/09/11 17:37:35 DDSet_CARetVal: 000005b4:(null)05/09/11 17:37:35 DDSet_CARetVal: 800705b4:Failed to run 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_05/09/11 17:37:35 DDSet_Exit: QuietExecMSI (s) (90:9C) [17:37:35:169]: Executing op: ActionStart(Name=CA_RegIIS_x86,,)CustomAction CA_RegIIS_amd64 returned actual error code 1603 but will be translated to success due to continue markingMSI (s) (90:9C) [17:37:35:187]: Executing op: CustomActionSchedule(Action=CA_RegIIS_x86,ActionType=1089,Source=BinaryData,Target=QuietExec,CustomActionData=C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe
The 3600 second time out might not always be exceeded.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.