Answered by:
Help with getting .net Framework 4 running on IIS6 Windows Server 2003

-
Hi all,
My server is Windows Server 2003 R2 - Standard 32-bit - Service Pack 2 with IIS 6.0
We just started using Visual Studio 2012 to convert our existing (and running fine) classic ASP scripts to asp.net. I installed the .net framework 4.0 on the server and I can see it in the IIS Manager, under Web Service Extensions and it is allowed.
When I publish a project to the server and access the page, I get the following:
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.
Source Error:Line 18: during development. Line 19: --> Line 20: <compilation debug="true" targetFramework="4.0"/> Line 21: <!-- Line 22: The <authentication> section enables configuration
Version Information: Microsoft .NET Framework Version:2.0.50727.3649; ASP.NET Version:2.0.50727.3634After looking on line for the past few days and trying various things, I still have this error. One thing of note, I did try the manually run aspnet_isapi.dll from the 4.0.30319 folder and the log is showing 1 failure:
2013-08-29 09:31:50 Failure Creating directory: C:\Inetpub\private\aspnet_client: CreateDirectoryInternal failed with HRESULT 80070003: 'The system cannot find the path specified. '
2013-08-29 09:31:50 Failure Creating list of client site scripts dirs: CreateSiteClientScriptDir failed with HRESULT 80070003: 'The system cannot find the path specified. 'Other than that, everything else in the log was completed.
If anyone can help with this I would greatly appreciate it.
Thank you,
George
Question
Answers
-
The first thing that comes to mind (going from memory from when I've had .net issues in IIS) is have you created a new application pool specifically for the new site?
Failing that as a suggestion, check out http://johan.driessen.se/posts/getting-an-asp.net-4-application-to-work-on-iis6 which goes into detail of issues with .Net 4 on 2003, including various things to determine the root cause, and also http://blog.diegocadenas.com/2010/05/aspnet-4-and-iis6.html which also covers the same thing but perhaps in a little less detail.
If neither of those help you might be better off posting over on http://forums.iis.net which is the IIS specific Microsoft forum (predates this one which is apparently why they have their own separate forum).
- Marked as answer by Justin GuMicrosoft contingent staff, Moderator Friday, September 06, 2013 7:04 AM
All replies
-
The first thing that comes to mind (going from memory from when I've had .net issues in IIS) is have you created a new application pool specifically for the new site?
Failing that as a suggestion, check out http://johan.driessen.se/posts/getting-an-asp.net-4-application-to-work-on-iis6 which goes into detail of issues with .Net 4 on 2003, including various things to determine the root cause, and also http://blog.diegocadenas.com/2010/05/aspnet-4-and-iis6.html which also covers the same thing but perhaps in a little less detail.
If neither of those help you might be better off posting over on http://forums.iis.net which is the IIS specific Microsoft forum (predates this one which is apparently why they have their own separate forum).
- Marked as answer by Justin GuMicrosoft contingent staff, Moderator Friday, September 06, 2013 7:04 AM
-
-