Answered by:
ASP 2.0 Web Components failure on installation

Question
-
Hi all - Installing the Standard edition here. I have .NET 2.0 installed on a 2003 Enterprise SP1 box. ASP 2.0 50727.
The installation fails during the deployment stage. Specifically at the stage where it is registering the ASP 2.0 service extensions. I have enabled ASP 2.0 extensions in IIS but she still fails. Here is a copy of the ICSSetup_commands.log:
MSI (s) (D8
4) [08:22:46:763]: Executing op: CustomActionSchedule(Action=CA_RegisterPerfCounters_Dlx,ActionType=1025,Source=BinaryData,Target=RegisterPerfCounters,CustomActionData=C:\Program Files\Office Communications Server 2007\Web Components\Group Expansion\Bin\DlxPerf.dll|/n /i /s)
MSI (s) (D8:EC) [08:22:46:763]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIB8.tmp, Entrypoint: RegisterPerfCounters
MSI (s) (D84) [08:22:47:138]: Executing op: ActionStart(Name=CA_SetPerfRegKeySecurity_DlxPerf,Description=Adding permissions to local group 'RTC Component Local Group' on DL Expansion performance counters registry key,)
Action 8:22:47: CA_SetPerfRegKeySecurity_DlxPerf. Adding permissions to local group 'RTC Component Local Group' on DL Expansion performance counters registry key
MSI (s) (D84) [08:22:47:138]: Executing op: CustomActionSchedule(Action=CA_SetPerfRegKeySecurity_DlxPerf,ActionType=1025,Source=BinaryData,Target=SetPerfRegKeySecurity,CustomActionData=DlxPerf|RTC Component Local Group)
MSI (s) (D8:F0) [08:22:47:138]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIB9.tmp, Entrypoint: SetPerfRegKeySecurity
MSI (s) (D84) [08:22:47:217]: Executing op: ActionStart(Name=CA_Register_2.0_With_IIS,Description=Registering ASP.NET 2.0 with IIS,)
Action 8:22:47: CA_Register_2.0_With_IIS. Registering ASP.NET 2.0 with IIS
MSI (s) (D84) [08:22:47:217]: Executing op: CustomActionSchedule(Action=CA_Register_2.0_With_IIS,ActionType=1025,Source=BinaryData,Target=ExecuteCommand,CustomActionData=Cmd.exe /D /C ASPNet_RegIIS.exe -ir|C:\WINDOWS\system32\Cmd.exe|C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
MSI (s) (D8:00) [08:22:47:217]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIBA.tmp, Entrypoint: ExecuteCommand
MSI (s) (D84) [08:23:14:419]: Executing op: ActionStart(Name=CA_GroupExpansion_VirtualDir_Install_2.0_ScriptMap,Description=Installing ASP.NET 2.0 script map for GroupExpansion virtual directory,)
Action 8:23:14: CA_GroupExpansion_VirtualDir_Install_2.0_ScriptMap. Installing ASP.NET 2.0 script map for GroupExpansion virtual directory
MSI (s) (D84) [08:23:14:419]: Executing op: CustomActionSchedule(Action=CA_GroupExpansion_VirtualDir_Install_2.0_ScriptMap,ActionType=1025,Source=BinaryData,Target=ExecuteCommand,CustomActionData=Cmd.exe /D /C ASPNet_RegIIS.exe -s W3SVC/1/ROOT/GroupExpansion/|C:\WINDOWS\system32\Cmd.exe|C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
MSI (s) (D8:6C) [08:23:14:435]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIBB.tmp, Entrypoint: ExecuteCommand
MSI (s) (D84) [08:23:16:982]: Executing op: ActionStart(Name=CA_Allow_WebServiceExtension_ASP.NET_2.0,Description=Enabling ASP.NET 2.0 Web Service Extension,)
Action 8:23:16: CA_Allow_WebServiceExtension_ASP.NET_2.0. Enabling ASP.NET 2.0 Web Service Extension
MSI (s) (D84) [08:23:16:982]: Executing op: CustomActionSchedule(Action=CA_Allow_WebServiceExtension_ASP.NET_2.0,ActionType=1025,Source=BinaryData,Target=ExecuteCommand,CustomActionData=CScript.exe //U //Nologo IISExt.vbs /EnExt "ASP.NET v2.0.50727"|C:\WINDOWS\system32\CScript.exe|C:\WINDOWS\system32\)
MSI (s) (D8:08) [08:23:16:982]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIBC.tmp, Entrypoint: ExecuteCommand
Error 29024. Error 0x80004005 occurred while executing command 'C:\WINDOWS\system32\CScript.exe'. For more details, check log file 'C:\DOCUME~1\ADMINI~1.GOS\LOCALS~1\Temp\LCSSetup_Commands.log'.
MSI (s) (D8!48) [08:23:22:825]: Product: Office Communications Server 2007 Public Beta, Web Components -- Error 29024. Error 0x80004005 occurred while executing command 'C:\WINDOWS\system32\CScript.exe'. For more details, check log file 'C:\DOCUME~1\ADMINI~1.GOS\LOCALS~1\Temp\LCSSetup_Commands.log'.Action ended 8:23:22: InstallFinalize. Return value 3.
MSI (s) (D84) [08:23:22:841]: User policy value 'DisableRollback' is 0
MSI (s) (D84) [08:23:22:841]: Machine policy value 'DisableRollback' is 0
MSI (s) (D84) [08:23:22:841]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=914703063,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (D84) [08:23:22:841]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (D84) [08:23:22:841]: Executing op: DialogInfo(Type=1,Argument=Office Communications Server 2007 Public Beta, Web Components)
MSI (s) (D84) [08:23:22:841]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (D84) [08:23:22:841]: Executing op: RegisterBackupFile(File=C:\Config.Msi\2b706cb.rbf)
Action 8:23:22: Rollback. Rolling back action:
Rollback: Enabling ASP.NET 2.0 Web Service Extension
Any help on this one would be great, I have tried re-installing .Net, re-installing IIS 6.0 etc... Thanks!
Chris
Thursday, April 5, 2007 4:06 PM
Answers
-
Sorry for the late response on this one.
The issue was fixed with a complete re-build of the server and a fresh install. The machine was built fresh in the last three months, however it was being used as an Intranet server and a Windows media server. As such, there was just too many unknowns. With no media server or previous web sites on the device; it came up no problem. Thank-you all for your help on this one. Fantactic product!!!
49th
Thursday, April 12, 2007 3:11 PM
All replies
-
Hello,
From yopu error message it looks like the command that failed was - CScript.exe //U //Nologo IISExt.vbs /EnExt "ASP.NET v2.0.50727"|C:\WINDOWS\system32\CScript.exe|C:\WINDOWS\system32\)
The IISExt.vbs command is a internal script located in c:\windows\system32 and it will always have to be run from this command prompt at least for our testing.
The /EnExt switch will enable all files for a web service extension with the specified web extension ID e. g. "ASP.NET v2.0.50727". So lets play around with this some ans see whwere the problem maybe.
Use the following command c:\windows\system32>cscript IISExt.vbs /ListExt - Is "ASP.NET v2.0.50727". Aready listed here?
c:\windows\system32>cscript IISExt.vbs /? will give you alist of the switches and their description
Use the following command c:\windows\system32>cscript IISExt.vbs /EnExt "ASP.NET v2.0.50727" - This comand will try to enable all files for the web service extension "ASP.NET v2.0.50727" - Let's see if the command fails outside of the setup program
Please read the folowing KB articles
HOW TO: List Web Server Extensions and Extension Files in IIS 6.0
<_http://support.microsoft.com/kb/328505/en-us>The WebSvcExtRestrictionList is an element in the \system32\inetsrv\metabase.xml file which is used to manage the Web Extensions. The IISExt.vbs command is allowing us to manipulate these extensions in the metabase.xml file. The metabas.xml file is the IIS 6.0 metabase. A repository of IIS configuration information. We need to determine if our issue resides with access to metabase.xml
Internet Information Services (IIS) 6.0 Resource Kit Tools
The metabase explorer is part of the IIS Reskit listed above. This shouldlet you view the contents of WebSvcExtRestrictionList
Friday, April 6, 2007 9:45 PM -
Sorry for the late response on this one.
The issue was fixed with a complete re-build of the server and a fresh install. The machine was built fresh in the last three months, however it was being used as an Intranet server and a Windows media server. As such, there was just too many unknowns. With no media server or previous web sites on the device; it came up no problem. Thank-you all for your help on this one. Fantactic product!!!
49th
Thursday, April 12, 2007 3:11 PM -
Thanks for the reply and I am glad the issue is resolved for you.Friday, April 13, 2007 11:47 PM
-
Just a note, I too had this issue, where the server was being used for other websites.
Removing any host header values for the default site fixed the issue.- Proposed as answer by TylerMcDowall Saturday, June 13, 2009 10:09 PM
Saturday, June 13, 2009 10:09 PM -
I solve the problem runnig this commands:
MSDOS:
cd c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
aspnet_regiis.exe -i -enable
cd c:\WINDOWS\system32
cscript IISExt.vbs /EnExt "ASP.NET v2.0.50727"
Run the setup again.
Bruno Estrozi - MCSE +S +M/MCTS/MCITP - Unified Communications Specialist | http://brunoestrozi.com.brTuesday, October 20, 2009 2:55 PM