Web Verifier HTTP Error 500.21 "Handler "PageHandlerFactory-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list"
(Doc ID 2998327.1)
Last updated on JANUARY 17, 2024
Applies to:
Oracle WebCenter Forms Recognition - Version 12.2.1.4.0 to 12.2.1.4.0 [Release 12c]Information in this document applies to any platform.
Symptoms
A WebCenter Forms Recognition 12.2.1.4.0 system was upgraded from Windows 2012 to Windows 2016. After upgrade the following error occurs when opening Web Verifier:
HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list
Most likely causes:
- Managed handler is used; however, ASP.NET is not installed or is not installed completely.
- There is a typographical error in the configuration for the handler module list.
- During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.
Things you can try:
- Install ASP.NET if you are using managed hanlder.
- Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format moudles="StaticFileModule,DefaultDocumentModule,DirectoryListingModule".
- Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.)
- As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)
Detailed Error Information:
Module IIS Web Core
Notification ExecuteRequestHandler
Handler PageHandlerFactory-Integrated-4.0
Error Code 0x8007000d
Requested URLhttp://:80/webverifier/BatchView.aspx
Physical Path E:\WFR\WebCenter Forms Recognition Web Server\BatchView.aspx
Logon Method Negotiate
Logon User \
More Information:
IIS core does not recognize the module.
Handler "PageHandlerFactory-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list
Most likely causes:
- Managed handler is used; however, ASP.NET is not installed or is not installed completely.
- There is a typographical error in the configuration for the handler module list.
- During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.
Things you can try:
- Install ASP.NET if you are using managed hanlder.
- Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format moudles="StaticFileModule,DefaultDocumentModule,DirectoryListingModule".
- Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.)
- As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)
Detailed Error Information:
Module IIS Web Core
Notification ExecuteRequestHandler
Handler PageHandlerFactory-Integrated-4.0
Error Code 0x8007000d
Requested URLhttp://:80/webverifier/BatchView.aspx
Physical Path E:\WFR\WebCenter Forms Recognition Web Server\BatchView.aspx
Logon Method Negotiate
Logon User \
More Information:
IIS core does not recognize the module.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |