7/23/2014 (10 years ago) | |
Clarify | |
Any | |
7/23/2014 (10 years ago) | |
Windows (Any) | |
Any |
Trying to access a Dovetail web application (such as Dovetail Seeker or Dovetail Agent) can throw an error.
ASP.NET 4 applications that are configured as children of applications that run earlier versions of ASP.NET might fail to start because of configuration or compilation errors.
The following example shows a directory structure for an affected application.
/parentwebapp (configured to use ASP.NET 2.0 or ASP.NET 3.5)
/childwebapp (configured to use ASP.NET 4)
The application in the childwebapp folder will fail to start on IIS 7 or IIS 7.5 and will report a configuration error. The error text will include a message similar to the following:
The requested page cannot be accessed because the related configuration data for the page is invalid.
The configuration section ‘configSections’ cannot be read because it is missing a section declaration.
On IIS 6, the application in the childwebapp folder will also fail to start, but it will report a different error. For example, the error text might state the following:
The value for the ‘compilerVersion’ attribute in the provider options must be ‘v4.0’ or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the ‘targetFramework’ attribute from the element of the Web.config file
In one particular customer scenario, the only change needed was to add the inheritInChildApplications="false" attribute to the location element within the web.config file of the parent website that Agent and Seeker are running under.
Example:
<location path="" inheritInChildApplications="false" >
More details are available in this article:
http://www.asp.net/whitepapers/aspnet4/breaking-changes#0.1__Toc256770150
This is due to configuring your Dovetail web application (an ASP.NET 4 web app) as a child application when the parent web app is a ASP.NET 2.0 or ASP.NET 3.5 Application
The following article discusses how to resolve this issue:
http://www.asp.net/whitepapers/aspnet4/breaking-changes#0.1__Toc256770150
You must be logged in to post a comment.
Login