ManagedPipelineHandler - HttpStatus 500 Notification 128 Internal Server Error - Microsoft ASP.Ne...
Feb 06, 2017 12:58 PM|bwarner@servicead-in.com|LINK
We have designed a ASP.Net WebAPI written in C# hosted on IIS 7.0 - REST style architecture. This is working in several environments, but is failing on a SBS 2008 environment with IIS 7.0. This interface must work with a Application Pool that is Enabled
to work with 32-Bit Applications.
We have this Webservice working in 2012 Essential Server and a 2008R2 Standard both with IIS 7.5.
The initial errors as logged with Failed Requests showed 500.19 errors. These were failures with the Static/DynamicCompressionModules. These were cleared-up by deleting these modules. After these errors cleared, an error with HTTPStatus 500, ModuleName:
ManagedPipelineHandler, Notification: 128, HTTPReason: Internal Server Error displayed. The Notification is EXECUTE_REQUEST_HANDLER with ErrorCode: The operation completed successfully. (0x0).
Fiddler reports:
HTTP/1.1 500 Internal Server Error Cache-Control: no-cache Pragma: no-cache Content-Type: application/json; charset=utf-8 Expires: -1 Server: Microsoft-IIS/7.0 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Date: Sun, 05 Feb 2017 00:59:43 GMT
Content-Length: 235
{"Message":"Retrieving the COM class factory for component with CLSID {22E885D7-FB0B-49E3-B905-CCA6BD526B52} failed due to the following error: 80040154 Class not registered (Exception from RESULT: 0x80040154 (REGDB_E_CLASSNOTREG))."}
But the DCOM object is registered. We have also tried:
1 Post
ManagedPipelineHandler - HttpStatus 500 Notification 128 Internal Server Error - Microsoft ASP.Ne...
Feb 06, 2017 12:58 PM|bwarner@servicead-in.com|LINK
We have designed a ASP.Net WebAPI written in C# hosted on IIS 7.0 - REST style architecture. This is working in several environments, but is failing on a SBS 2008 environment with IIS 7.0. This interface must work with a Application Pool that is Enabled to work with 32-Bit Applications.
We have this Webservice working in 2012 Essential Server and a 2008R2 Standard both with IIS 7.5.
The initial errors as logged with Failed Requests showed 500.19 errors. These were failures with the Static/DynamicCompressionModules. These were cleared-up by deleting these modules. After these errors cleared, an error with HTTPStatus 500, ModuleName: ManagedPipelineHandler, Notification: 128, HTTPReason: Internal Server Error displayed. The Notification is EXECUTE_REQUEST_HANDLER with ErrorCode: The operation completed successfully. (0x0).
Fiddler reports:
HTTP/1.1 500 Internal Server Error Cache-Control: no-cache Pragma: no-cache Content-Type: application/json; charset=utf-8 Expires: -1 Server: Microsoft-IIS/7.0 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Date: Sun, 05 Feb 2017 00:59:43 GMT Content-Length: 235
{"Message":"Retrieving the COM class factory for component with CLSID {22E885D7-FB0B-49E3-B905-CCA6BD526B52} failed due to the following error: 80040154 Class not registered (Exception from RESULT: 0x80040154 (REGDB_E_CLASSNOTREG))."}
But the DCOM object is registered. We have also tried:
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i5265 Posts
MVP
Moderator
Re: ManagedPipelineHandler - HttpStatus 500 Notification 128 Internal Server Error - Microsoft AS...
Feb 06, 2017 07:03 PM|Rovastar|LINK
I don't know but I think it might be something to do with how the COM objects are created.
IIS7.0 will run on Windows 2008 (not R2) are often 32bit. What version of you running?
I expect this is causing issues for you. Maybe something is created for x64 rather than x86.
You could try running it in classic app pool too.
https://www.leansentry.com/