Unrecognized attribute processRequestInApplicationTrust

[Abel Chan]

Hi all,

I have a 2003 R2 server. When I tried to run a .NET framework 1.1 ASP.NET
application, I am getting the following error message:

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
'processRequestInApplicationTrust'.
Source Error:
Line 66: </namespaces>
Line 67: </pages>
Line 68: <trust level="WSS_Minimal" originUrl=""
processRequestInApplicationTrust="false"/>
Line 69: <machineKey
validationKey="BA46B67FB93892E81FEB33A886FAB6DAC3B 0473F50466269"
decryptionKey="AE3A2638BFA3DE3F920A7479F069EA11453 B7D76B52D203B"
validation="SHA1"/>
Line 70: </system.web>
Source File: c:\inetpub\wwwroot\web.config Line: 68

I check my IIS and I have selected the 1.1 framework from the ASP.NET tab.
The 1.1 ASP.NET application runs fine on my 2000 server. Is this a setup
issue?

BTW, I also tried to convert the application to .NET framework 2.0 but I am
getting the following errors from Event Viewer. Not sure whether they are
related.

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1062
Date: 11/3/2006
Time: 3:59:42 AM
User: N/A
Computer: BIZTALKDEV1
Description:
It is not possible to run two different versions of ASP.NET in the same IIS
process. Please use the IIS Administration Tool to reconfigure your server to
run the application in a separate process.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

[Walter Wang [MSFT]]

Hi,

I believe the element is new in ASP.NET 2.0 which means you must configure
your web site to run using ASP.NET 2.0 instead of ASP.NET 1.1:

#trust Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-gb/lib...93(VS.80).aspx
processRequestInApplicationTrust is new in the .NET Framework version 2.0.
As for the error you mentioned in event log, you can find the cause and
explanation here:

#How ASP.NET Works with IIS 6.0 (IIS 6.0)
http://www.microsoft.com/technet/pro.../Library/IIS/f
1a39358-5ab8-4dc1-a60d-eedea7360780.mspx
This error occurs when more than one version of ASP.NET is configured to
run in the same process. Different versions of the .NET Framework and run
time cannot coexist side by side within the same process. Therefore, an
ASP.NET application that uses one version of the run time must not share a
process with an application that uses a different version. This error
commonly occurs when two or more applications are mapped to different
versions of ASP.NET but share the same application pool.

You can find the solution here:

#Configuring an ASP.NET Application for an ASP.NET Version (IIS 6.0)
http://www.microsoft.com/technet/pro.../Library/IIS/d
2cc4557-dbe7-46f9-9b63-df1d09f17c6a.mspx
See section "Application Pooling in IIS 6.0"

For more information about Side-By-Side support for ASP.NET (IIS 6.0):
#Side-By-Side Support for ASP.NET (IIS 6.0)
http://www.microsoft.com/technet/pro.../Library/IIS/2
44cad41-0474-4bbc-a7d6-bcc4461aac72.mspx
The .NET Framework provides support for side-by-side execution, which
allows multiple versions of an assembly or application to be installed on
the same computer, at the same time. Since multiple versions can be
installed simultaneously, managed applications can select which version to
use without affecting other applications that use a different version.
Let me know if this answers your questions.

Sincerely,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Abel Chan]

Hi Walter,

Thanks for your help on this posting. I was able to track down the issue
with you response.

1) When I created the ASP.NET 1.1 application, I was assigning it to run in
a Application Pool that it has .NET 2.0 application in it. That causes the
error.

2) I have Windows SharePoint Service installed on the server. I have to add
<trust level="Full" /to the web.config file. I thought <trust
level="Full" /is by default and not sure why I need to explicitly do that.
Any idea?

Anyway, my ASP.NET 2.0 is working now. Thanks.

Abel


"Walter Wang [MSFT]" wrote:

Hi,

I believe the element is new in ASP.NET 2.0 which means you must configure
your web site to run using ASP.NET 2.0 instead of ASP.NET 1.1:

#trust Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-gb/lib...93(VS.80).aspx
processRequestInApplicationTrust is new in the .NET Framework version 2.0.
As for the error you mentioned in event log, you can find the cause and
explanation here:

#How ASP.NET Works with IIS 6.0 (IIS 6.0)
http://www.microsoft.com/technet/pro.../Library/IIS/f
1a39358-5ab8-4dc1-a60d-eedea7360780.mspx
This error occurs when more than one version of ASP.NET is configured to
run in the same process. Different versions of the .NET Framework and run
time cannot coexist side by side within the same process. Therefore, an
ASP.NET application that uses one version of the run time must not share a
process with an application that uses a different version. This error
commonly occurs when two or more applications are mapped to different
versions of ASP.NET but share the same application pool.

You can find the solution here:

#Configuring an ASP.NET Application for an ASP.NET Version (IIS 6.0)
http://www.microsoft.com/technet/pro.../Library/IIS/d
2cc4557-dbe7-46f9-9b63-df1d09f17c6a.mspx
See section "Application Pooling in IIS 6.0"

For more information about Side-By-Side support for ASP.NET (IIS 6.0):
#Side-By-Side Support for ASP.NET (IIS 6.0)
http://www.microsoft.com/technet/pro.../Library/IIS/2
44cad41-0474-4bbc-a7d6-bcc4461aac72.mspx
The .NET Framework provides support for side-by-side execution, which
allows multiple versions of an assembly or application to be installed on
the same computer, at the same time. Since multiple versions can be
installed simultaneously, managed applications can select which version to
use without affecting other applications that use a different version.
Let me know if this answers your questions.

Sincerely,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Abel,

Thank you for letting me know that you've solved the problem.

As for the trust level, you're right that by default it's "full", it's set
in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONF IG\web.config, you can
verify that. I'm not sure if SharePoint requires explicitly set it again or
not since I'm not familiar with it, you might need to post a new post in
related newsgroups, I'm sure my colleagues will be of help. Thanks.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.