Integrated managed pipeline mode error

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
6/17/2008 3:32:00 AM
Gravatar
Total Posts 2

Integrated managed pipeline mode error

Hi,

When starting mojoportal on a Windows 2008 hosting site at Discount.ASP I get the following error:

HTTP Error 500.22 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode. Detailed Error InformationModule ConfigurationValidationModule
Notification BeginRequest
Handler StaticFile
Error Code 0x80070032
Requested URL http://www.eaprocessmap.com:80/mojoportal2209513
Physical Path E:\web\eaprocessm2\htdocs\mojoportal2209513
Logon Method Not yet determined
Logon User Not yet determined
Most likely causes:
This application defines configuration in the system.web/httpModules section.
Things you can try:
Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS.
If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.
Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application.
(Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name) Links and More Information

Can anybody help me please?

6/17/2008 3:52:47 AM
Gravatar
Total Posts 2

Re: Integrated managed pipeline mode error

Hi,

Solved the problem by changing to classic mode in IIS.

 

You must sign in to post in the forums. This thread is closed to new posts.