Application Server Extensions for .NET 4 Setup Problems

Question

I've been trying to follow the AppFabric Installation Guide to install Beta 1 on a Windows Server 2008 SP2 (x86) machine.  I had mentioned previously that I had trouble installing Powershell 2.0, but it looks like I already had that installed.

Here's what I'm specifying in the Application Server Extensions for .NET 4 Setup Wizard:
 - Feature Selection: select Worker only (just trying to get this working w/o caching for now)
 - Monitoring Settings: select defaults
 - Persistence Settings: select defaults
 
The setup completes with errors.  I'll include part of the setup log file with the errors below. 

Following the setup log file, things seem to go pretty well until I start seeing some errors related to a config file missing a section declaration.  Here's an example of that:

[21:07:30 Error] Failed to set monitoringFilename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config
Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

Later, the AppServerEventCollectorService fails to start, which also appears to be a config file problem:

Service cannot be started. System.Runtime.InteropServices.COMException (0x80070490): Filename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config
Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

I've tried this a number of times, trying various things but to no avail. 

Thanks,

David Madrian

[21:07:15 Information] Package installed successfully.

[21:07:15 Information]

Creating configuration session

[21:07:15 Information]

Applying settings:

 

[21:07:15 Information]

Starting the execution of: AddEventCollectorServiceUserToAdministratorsGroup

[21:07:15 Information] The default event collector service user already belongs to the default administrators group. AddWindowServiceUserToAdministratorsGroup does not apply. Skipping

[21:07:15 Information] Completed with success the execution of: AddEventCollectorServiceUserToAdministratorsGroup

[21:07:15 Information]

Starting the execution of: AddWorkflowManagementServiceUserToAdministratorsGroup

[21:07:15 Information] The default workflow management service user already belongs to the default administrators group. AddWindowServiceUserToAdministratorsGroup does not apply. Skipping

[21:07:15 Information] Completed with success the execution of: AddWorkflowManagementServiceUserToAdministratorsGroup

[21:07:15 Information]

Starting the execution of: AddConnectionStringToConfig

[21:07:15 Information] Add connection strings: InProgress

[21:07:15 Information] Executing Cmdlet: Remove-ConnectionStringConfig -Root -Name <> -Confirm false

[21:07:25 Information] To perform AddConnectionStringConfig - Persistence

[21:07:25 Information] Executing Cmdlet: Add-ConnectionStringConfig

[21:07:26 Information] Executing Cmdlet: Remove-ConnectionStringConfig -Root -Name <> -Confirm false

[21:07:26 Information] To perform AddConnectionStringConfig - Monitoring

[21:07:26 Information] Executing Cmdlet: Add-ConnectionStringConfig

[21:07:26 Information] Add connection strings: Success

[21:07:26 Information] Completed with success the execution of: AddConnectionStringToConfig

[21:07:26 Information]

Starting the execution of: SetPersistence

[21:07:26 Information] Set root persistence behavior: InProgress

[21:07:26 Information] To perform EnableServicePersistence

[21:07:26 Information] Executing Cmdlet: Set-ServicePersistence -Root - ConnectionStringName <>

[21:07:27 Information] Set root persistence behavior: Success

[21:07:27 Information] Completed with success the execution of: SetPersistence

[21:07:27 Information]

Starting the execution of: UpdateWorkflowManagementServiceConfig

[21:07:27 Information] Configure Workflow Management service: InProgress

[21:07:27 Information] To perform AddDatabaseConfig

[21:07:27 Information] Configure Workflow Management service: Success

[21:07:27 Information] Completed with success the execution of: UpdateWorkflowManagementServiceConfig

[21:07:27 Information]

Starting the execution of: SetMonitoring

[21:07:27 Information] Set root monitoring behavior: InProgress

[21:07:27 Information] To perform SetMonitoring

[21:07:27 Information] Executing Cmdlet: Set-Monitoring -Root -ConnectionStringName <> -MonitoringLevel HealthMonitoring

[21:07:30 Error] Failed to set monitoring

 

Filename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config

Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

 

 

   at Microsoft.Web.Administration.Interop.AppHostWritableAdminManager.GetAdminSection(String bstrSectionName, String bstrSectionPath)

   at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)

   at Microsoft.Web.Administration.Configuration.GetSection(String sectionPath, String locationPath)

   at Microsoft.ApplicationServer.Management.WebAdministration.ConfigurationExtension.GetSection(Configuration configuration, String sectionPath, Boolean shouldHandleNonTerminatingExceptions, String locationPath)

   at Microsoft.ApplicationServer.Management.Helpers.MonitoringHelper.SetDefaultEventSourceInfo(Configuration config, EventSourceInfo eventSourceInfo)

   at Microsoft.ApplicationServer.Management.Configuration.MonitoringLevelActivity.DoSet(MonitoringInfo monitoringLevelSpecification)

   at Microsoft.ApplicationServer.Management.Configuration.ConfigurationEditor`1.Set(T itemSpecification, ConfirmationDelegate confirmChanges)

   at Microsoft.ApplicationServer.Management.Commands.ConfigurationCmdlet.ExecuteSet[T](ConfigurationManager configManager, T configInfo, ISupportSet`1 setActivity, ISupportGetSpecific`1 getActivity)

   at Microsoft.ApplicationServer.Management.Commands.SetASAppMonitoringCmdlet.ProcessCommand(ConfigurationManager configManager)

   at Microsoft.ApplicationServer.Management.Commands.ConfigurationCmdlet.ProcessRecordCore()

   at Microsoft.ApplicationServer.Management.Commands.ServerManagementCmdlet.ProcessRecord()

   at System.Management.Automation.Cmdlet.DoProcessRecord()

   at System.Management.Automation.CommandProcessor.ProcessRecord()

Filename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config

Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

 

 

   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecute(Array input, Hashtable errorResults)

   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()

   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Exception has been thrown by the target of an invocation.

   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

   at Microsoft.ApplicationServer.Setup.Configuration.PowerShell.Pipeline.Invoke()

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.SetMonitoring(String connectionString)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.SetMonitoring(ConfigurationSettings settings)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSession.ExecuteAndContinue(ConfigurationAction action)

Failed to set monitoring

 

[21:07:30 Information] Set root monitoring behavior: Error

[21:07:30 Information] Completed the execution of: SetMonitoring

[21:07:30 Information]

Starting the execution of: ChangeEventCollectorServiceIdentity

[21:07:30 Information] To perform GrantLogonAsServiceToAccount

[21:07:30 Information] The event collector service user was not changed. ChangeWindowsServiceIdentity does not apply. Skipping

[21:07:30 Information] Completed with success the execution of: ChangeEventCollectorServiceIdentity

[21:07:30 Information]

Starting the execution of: ChangeWorkflowManagementServiceIdentity

[21:07:30 Information] To perform GrantLogonAsServiceToAccount

[21:07:30 Information] The workflow management service user was not changed. ChangeWindowsServiceIdentity does not apply. Skipping

[21:07:30 Information] Completed with success the execution of: ChangeWorkflowManagementServiceIdentity

[21:07:30 Information]

Starting the execution of: StartEventCollectorWindowsService

[21:07:30 Information] Start Event Collector service: InProgress

[21:07:30 Information] To perform StartWindowsService for AppServerEventCollectorService

[21:07:30 Information] Executing StartWindowsService

[21:07:30 Information] Service's status is Stopped. Starting it.

[21:07:32 Information] Waiting for service to be on Running state.

[21:08:32 Error] Failed to start the Event Collector service

 

Time out has expired and the operation has not been completed.

   at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.StartWindowsService(String windowsServiceName)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.StartEventCollectorWindowsService(ConfigurationSettings settings)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSession.ExecuteAndContinue(ConfigurationAction action)

Failed to start the Event Collector service

 

[21:08:32 Information] Start Event Collector service: Error

[21:08:32 Information] Completed the execution of: StartEventCollectorWindowsService

[21:08:32 Information]

Starting the execution of: StartWorkflowManagementService

[21:08:32 Information] Start Workflow Management service: InProgress

[21:08:32 Information] To perform StartWindowsService for WorkflowManagementService

[21:08:32 Information] Executing StartWindowsService

[21:08:32 Information] Service's status is Stopped. Starting it.

[21:08:34 Information] Waiting for service to be on Running state.

[21:08:37 Information] Start Workflow Management service: Success

[21:08:37 Information] Completed with success the execution of: StartWorkflowManagementService

[21:08:37 Information]

Starting the execution of: AddDistributedCacheConfiguration

[21:08:37 Information] Apply Distributed Cache Configuration: InProgress

[21:08:37 Information] To perform Distributed Cache Configuration with command line /IAS /New ClusterSize=Small LOGFILE="C:\Users\Administrator\AppData\Local\Temp\DistributedCacheAppServerConfig(2008-11-09 21-08-37).log" Provider=System.Data.SqlClient ConnectionString="Data Source=PDC08-CSD;Initial Catalog=DistributedCache;Integrated Security=True" SERVICEPORT=22233 CLUSTERPORT=22234 ARBITRATORPORT=22235 REPLICATIONPORT=22236 UNBLOCKSERVICE=True UNBLOCKFILESHARING=True UNBLOCKREMOTEADMIN=True /quiet

[21:08:40 Information] Distributed Cache Configuration failed with error code: 2

[21:08:40 Error] Failed to apply Distributed Cache Configuration

 

Failed to apply Distributed Cache Configuration

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.AddDistributedCacheConfiguration(ConfigurationSettings settings)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSession.ExecuteAndContinue(ConfigurationAction action)

Failed to apply Distributed Cache Configuration

 

[21:08:40 Information] Apply Distributed Cache Configuration: Error

[21:08:40 Information] Completed the execution of: AddDistributedCacheConfiguration

[21:08:40 Information] 3 errors found during Apply Settings

[21:08:40 Error] Failed to Configure.  Please see the error, fix the problem, and try again.

 

Configuration completed with multiple errors.  The error list and details can be found in the Windows Logs Setup node in the Windows Event Viewer.  Filter for events from the source ASE_Setup.

 

Microsoft.ApplicationServer.Setup.Core.SetupException: Configuration completed with multiple errors.  The error list and details can be found in the Windows Logs Setup node in the Windows Event Viewer.  Filter for events from the source ASE_Setup.

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSetupModule.ApplySettings()

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSetupModule.PostInstall()

   at Microsoft.ApplicationServer.Setup.Client.SetupWorkflow.PostInstall()

   at Microsoft.ApplicationServer.Setup.Client.SetupWorkflow.StartActionPhase()

   at Microsoft.ApplicationServer.Setup.Client.ProgressPage.StartAction()

 

=== Summary of Actions ===

Enabling the following Windows features.                   :  Completed Successfully

Application Server Role     :  Completed Successfully

IIS Management Console                          :  Completed Successfully

Application Server Extensions for .NET 4                      :  Completed Successfully

Configure Application Server Extensions for .NET 4                          :  Failed

Add connection strings     :  Completed Successfully

Set root persistence behavior                :  Completed Successfully

Configure Workflow Management service                  :  Completed Successfully

Set root monitoring behavior                  :  Failed

Start Event Collector service                    :  Failed

Start Workflow Management service    :  Completed Successfully

Apply Distributed Cache Configuration                        :  Failed

 

===== Logging stopped: 2008-11-09 21:08:40-08:00 =====

 

 

Answer 1

Hi Dmadrian,

Are you using .Net Fx version 4.0.21006? Could you please confirm?

Thanks,
Geetanjali.

 

Answer 2

Please try the following pre-req install links instead.

1.  Powershell V2 RC (this is supported for Beta1 release of AppFabric).  The one you downloaded is Powershell V2 RTM, which will be supported for Beta2+ releast of AppFabric.
Powershell V2 RC x86 - https://connect.microsoft.com/windowsmanagement/Downloads/DownloadDetails.aspx?DownloadID=21267

2.  NetFx v4 Beta2.  I see you have an older version of NetFx4.0 install (4.0.10917).  http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx

-Gary

Answer 3

Hi Geetanjali,

It looks like I am using .NET Framework ver. 4.0.21006.  I reinstalled the framework from the link GaryKe provided below, rebooted and tried again, but with the same results.  I'll include my log file in my response to GaryKe below.

David

Answer 4

Hi Gary,

I downloaded the two install items (Powershell 2.0 and .NET Fx 4 Beta 2) from the links you provided, installed them and then tried reinstalling Application Server Extensions.  I selected the same setup options in the App Server Extensions wizard that I described in my original post (Worker only with no caching features)  Unfortunately, it still failed.  I'll paste in the end of the log file with all the errors. 

I'm installing on a machine which had the CTP version of VS2010 on it, which I tried to remove.  If it's not clear what's causing my problems, maybe I need to fully repave my machine and reinstall Windows Svr 2008 etc... 

Let me know if you have any other ideas.  Thanks for your help so far.

David

2008-11-10 04:03:32, Info                  CBS    Pkgmgr: return code: 0x0

=== End Content ===

 

[04:03:32 Information] Package installed successfully.

[04:03:32 Information]

Creating configuration session

[04:03:32 Information]

Applying settings:

 

[04:03:32 Information]

Starting the execution of: AddEventCollectorServiceUserToAdministratorsGroup

[04:03:32 Information] The default event collector service user already belongs to the default administrators group. AddWindowServiceUserToAdministratorsGroup does not apply. Skipping

[04:03:32 Information] Completed with success the execution of: AddEventCollectorServiceUserToAdministratorsGroup

[04:03:32 Information]

Starting the execution of: AddWorkflowManagementServiceUserToAdministratorsGroup

[04:03:32 Information] The default workflow management service user already belongs to the default administrators group. AddWindowServiceUserToAdministratorsGroup does not apply. Skipping

[04:03:32 Information] Completed with success the execution of: AddWorkflowManagementServiceUserToAdministratorsGroup

[04:03:32 Information]

Starting the execution of: AddConnectionStringToConfig

[04:03:32 Information] Add connection strings: InProgress

[04:03:32 Information] Executing Cmdlet: Remove-ConnectionStringConfig -Root -Name <> -Confirm false

[04:03:37 Information] To perform AddConnectionStringConfig - Persistence

[04:03:37 Information] Executing Cmdlet: Add-ConnectionStringConfig

[04:03:37 Information] Executing Cmdlet: Remove-ConnectionStringConfig -Root -Name <> -Confirm false

[04:03:37 Information] To perform AddConnectionStringConfig - Monitoring

[04:03:37 Information] Executing Cmdlet: Add-ConnectionStringConfig

[04:03:37 Information] Add connection strings: Success

[04:03:37 Information] Completed with success the execution of: AddConnectionStringToConfig

[04:03:37 Information]

Starting the execution of: SetPersistence

[04:03:37 Information] Set root persistence behavior: InProgress

[04:03:37 Information] To perform EnableServicePersistence

[04:03:37 Information] Executing Cmdlet: Set-ServicePersistence -Root - ConnectionStringName <>

[04:03:38 Information] Set root persistence behavior: Success

[04:03:38 Information] Completed with success the execution of: SetPersistence

[04:03:38 Information]

Starting the execution of: UpdateWorkflowManagementServiceConfig

[04:03:38 Information] Configure Workflow Management service: InProgress

[04:03:38 Information] To perform AddDatabaseConfig

[04:03:38 Information] Configure Workflow Management service: Success

[04:03:38 Information] Completed with success the execution of: UpdateWorkflowManagementServiceConfig

[04:03:38 Information]

Starting the execution of: SetMonitoring

[04:03:38 Information] Set root monitoring behavior: InProgress

[04:03:38 Information] To perform SetMonitoring

[04:03:38 Information] Executing Cmdlet: Set-Monitoring -Root -ConnectionStringName <> -MonitoringLevel HealthMonitoring

[04:03:39 Error] Failed to set monitoring

 

Filename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config

Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

 

 

   at Microsoft.Web.Administration.Interop.AppHostWritableAdminManager.GetAdminSection(String bstrSectionName, String bstrSectionPath)

   at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)

   at Microsoft.Web.Administration.Configuration.GetSection(String sectionPath, String locationPath)

   at Microsoft.ApplicationServer.Management.WebAdministration.ConfigurationExtension.GetSection(Configuration configuration, String sectionPath, Boolean shouldHandleNonTerminatingExceptions, String locationPath)

   at Microsoft.ApplicationServer.Management.Helpers.MonitoringHelper.SetDefaultEventSourceInfo(Configuration config, EventSourceInfo eventSourceInfo)

   at Microsoft.ApplicationServer.Management.Configuration.MonitoringLevelActivity.DoSet(MonitoringInfo monitoringLevelSpecification)

   at Microsoft.ApplicationServer.Management.Configuration.ConfigurationEditor`1.Set(T itemSpecification, ConfirmationDelegate confirmChanges)

   at Microsoft.ApplicationServer.Management.Commands.ConfigurationCmdlet.ExecuteSet[T](ConfigurationManager configManager, T configInfo, ISupportSet`1 setActivity, ISupportGetSpecific`1 getActivity)

   at Microsoft.ApplicationServer.Management.Commands.SetASAppMonitoringCmdlet.ProcessCommand(ConfigurationManager configManager)

   at Microsoft.ApplicationServer.Management.Commands.ConfigurationCmdlet.ProcessRecordCore()

   at Microsoft.ApplicationServer.Management.Commands.ServerManagementCmdlet.ProcessRecord()

   at System.Management.Automation.Cmdlet.DoProcessRecord()

   at System.Management.Automation.CommandProcessor.ProcessRecord()

Filename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config

Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

 

 

   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecute(Array input, Hashtable errorResults)

   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()

   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Exception has been thrown by the target of an invocation.

   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

   at Microsoft.ApplicationServer.Setup.Configuration.PowerShell.Pipeline.Invoke()

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.SetMonitoring(String connectionString)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.SetMonitoring(ConfigurationSettings settings)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSession.ExecuteAndContinue(ConfigurationAction action)

Failed to set monitoring

 

[04:03:39 Information] Set root monitoring behavior: Error

[04:03:39 Information] Completed the execution of: SetMonitoring

[04:03:39 Information]

Starting the execution of: ChangeEventCollectorServiceIdentity

[04:03:39 Information] To perform GrantLogonAsServiceToAccount

[04:03:39 Information] The event collector service user was not changed. ChangeWindowsServiceIdentity does not apply. Skipping

[04:03:39 Information] Completed with success the execution of: ChangeEventCollectorServiceIdentity

[04:03:39 Information]

Starting the execution of: ChangeWorkflowManagementServiceIdentity

[04:03:39 Information] To perform GrantLogonAsServiceToAccount

[04:03:39 Information] The workflow management service user was not changed. ChangeWindowsServiceIdentity does not apply. Skipping

[04:03:39 Information] Completed with success the execution of: ChangeWorkflowManagementServiceIdentity

[04:03:39 Information]

Starting the execution of: StartEventCollectorWindowsService

[04:03:39 Information] Start Event Collector service: InProgress

[04:03:39 Information] To perform StartWindowsService for AppServerEventCollectorService

[04:03:39 Information] Executing StartWindowsService

[04:03:39 Information] Service's status is Stopped. Starting it.

[04:03:40 Information] Waiting for service to be on Running state.

[04:04:40 Error] Failed to start the Event Collector service

 

Time out has expired and the operation has not been completed.

   at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.StartWindowsService(String windowsServiceName)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationOperations.StartEventCollectorWindowsService(ConfigurationSettings settings)

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSession.ExecuteAndContinue(ConfigurationAction action)

Failed to start the Event Collector service

 

[04:04:40 Information] Start Event Collector service: Error

[04:04:40 Information] Completed the execution of: StartEventCollectorWindowsService

[04:04:40 Information]

Starting the execution of: StartWorkflowManagementService

[04:04:40 Information] Start Workflow Management service: InProgress

[04:04:40 Information] To perform StartWindowsService for WorkflowManagementService

[04:04:40 Information] Executing StartWindowsService

[04:04:40 Information] Service's status is Stopped. Starting it.

[04:04:41 Information] Waiting for service to be on Running state.

[04:04:42 Information] Start Workflow Management service: Success

[04:04:42 Information] Completed with success the execution of: StartWorkflowManagementService

[04:04:42 Information] 2 errors found during Apply Settings

[04:04:42 Error] Failed to Configure.  Please see the error, fix the problem, and try again.

 

Configuration completed with multiple errors.  The error list and details can be found in the Windows Logs Setup node in the Windows Event Viewer.  Filter for events from the source ASE_Setup.

 

Microsoft.ApplicationServer.Setup.Core.SetupException: Configuration completed with multiple errors.  The error list and details can be found in the Windows Logs Setup node in the Windows Event Viewer.  Filter for events from the source ASE_Setup.

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSetupModule.ApplySettings()

   at Microsoft.ApplicationServer.Setup.Configuration.ConfigurationSetupModule.PostInstall()

   at Microsoft.ApplicationServer.Setup.Client.SetupWorkflow.PostInstall()

   at Microsoft.ApplicationServer.Setup.Client.SetupWorkflow.StartActionPhase()

   at Microsoft.ApplicationServer.Setup.Client.ProgressPage.StartAction()

 

=== Summary of Actions ===

Enabling the following Windows features.                      :  Completed Successfully

Application Server Role                :  Completed Successfully

IIS Management Console              :  Completed Successfully

Application Server Extensions for .NET 4                          :  Completed Successfully

Configure Application Server Extensions for .NET 4                          :  Failed

Add connection strings                  :  Completed Successfully

Set root persistence behavior                          :  Completed Successfully

Configure Workflow Management service                       :  Completed Successfully

Set root monitoring behavior                           :  Failed

Start Event Collector service     :  Failed

Start Workflow Management service          :  Completed Successfully

 

===== Logging stopped: 2008-11-10 04:04:42-08:00 =====

Answer 5

Hi Dimadrian,

Your logs still point to the older version of .Net Fx (v4.0.10917) as below,

[04:03:39 Error] Failed to set monitoring

 

Filename: \\?\C:\Windows\Microsoft.NET\Framework\v4.0.10917\CONFIG\web.config

Error: The configuration section 'microsoft.applicationServer/monitoring' cannot be read because it is missing a section declaration

 

 

   at Microsoft.Web.Administration.Interop.AppHostWritableAdminManager.GetAdminSection(String bstrSectionName, String

Could you please install .Net version 21006.

Also you can check the value of the reg key = 'Version' to check the .Net version being used on your machine before proceeding to installation of the product. Here is the reg path,
Hkey_Local_Machine/Software/Microsoft/Net Framework Setup\NDP\V4\Full

Thanks,
Geetanjali.

Answer 6

Hi Geetanjali,

It looks like I have both .NET Framework v4.0.10917 and v4.0.21006 installed on my system.  Here's what's in my registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\

There are the values under the path above:

  - CDF
    - v4.0
  - v2.0.50727
  - v3.0
  - v3.5
  - v4
    - Client
    - Full
  - v4.0
  - v4.0.10917  (there are no subkeys under this)

The value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\Full\Version is 4.0.21006

Even though I have the right version of the Framework on my machine, it seems like the setup is somehow trying to use the old version.  Maybe the easiest thing is if I can fully remove the 4.0.10917 version of the framework, but I don't know how to do that (on Windows Server 2008).  If this is a valid approach, do you happen to know how I can fully remove any traces of this older version of the .NET framework? 

Thanks again,

David

Answer 7

Hi David

Could you please delete the folder C:\Windows\Microsoft.NET\Framework\v4.0.10917 & C:\Windows\Microsoft.NET\Framework64\v4.0.10917 completely and try to install the product?  More details below-

Framework version  v4.0.10917  should have not been present as required framework  4.0.21006  can be installed only after uninstallation of older version v4.0.10917.  Please follow these steps:

1. Make sure that version v4.0.10917  of framework is completely uninstalled by looking at uninstall software from control panel.
2. If the previous version is already uninstalled then ensure that registry and othe files are completely cleaned up by a) makeing sure that  v4.0.10917  registry hive is completly removed. b) Remove the folders C:\Windows\Microsoft.NET\Framework\v4.0.10917 and C:\Windows\Microsoft.NET\Framework64\v4.0.10917, if they exists.
3. Install the product again.

Answer 8

Cleaning up the old installation of the .NET Framework definitely made a difference.  I was able to finally get an error-free install.  I didn't install any of the cache functionality, but hopefully that will go smoothly.

Thanks for all the help!