Http Error 500.21
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums IIS 7 and Above ASP.NET Administration HTTP Error 500.21 - Internal Server Error Handler "ScriptHandlerFacto... HTTP Error 500.21 - Internal Server Error Handler "ScriptHandlerFactory" has a bad module "ManagedPipelineHandler" in its module list [Answered]RSS 8 replies Last post Sep 17, 2013 11:19 PM by thuyvk ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply mpregos 1 Post HTTP Error 500.21 - Internal Server Error Handler "ScriptHandlerFactory" has a bad module "Manage... Nov 16, 2009 03:30 AM|mpregos|LINK Hi to everybody. I'm new to IIS + ASP and i need desperately yout help. I want to create WebService and use them via.asp WebPage. So, i create a WebServices dir to defaultIIS website directory(C:/inetpub/www/.....) andvia VS 2008 (Hosting on Windows64bit - 7 Proffesional) create new web services application. Thedeafault ,sayHello. So far so good...... When i create a WebPage via .asp andadd perform -->add Web Reference -->locate the WebServicethe following error come up: Handler "ScriptHandlerFactory" has a bad module "ManagedPipelineHandler" in its module list Google-it i found that the erorr could be in configuration of IIS but i can't find what is wrong??? Thanks Reply ksingla 1068 Posts Microsoft Re: HTTP Error 500.21 - Internal Server Error Handler "ScriptHandlerFactory" has a bad module "Ma... Nov 16, 2009 08:28 PM|ksingla|LINK Try suggestions in this thread. Thanks, Kanwal Reply Kelevra 1 Post Re: HTTP Error 500.21 - Internal Server Error Handler "ScriptHandlerFactory" has a bad module "Ma... Aug 20, 2010 08:18 PM|Kelevra|LINK Honestly I thought I was turning mad!!!! Abou
Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL https://forums.iis.net/t/1162666.aspx?HTTP+Error+500+21+Internal+Server+Error+Handler+ScriptHandlerFactory+has+a+bad+module+ManagedPipelineHandler+in+its+module+list+ / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product http://www.codeproject.com/Questions/412385/i-get-HTTP-Error-when-i-access-a-web-site-p Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Ask a Question All Questions All Unanswered FAQ i get HTTP Error 500.21 when i access a web site project deployed using iis 7 Rate this: Please Sign up or sign in to vote. See more: IIS7 ASP.NET IIS Deployment when i acces from my browser an web site project deployed using using iis7 i get the current error. HTTP Error 500.21 - Internal Server Error The list of modules manager "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" As i search there are two solutions -Install ASP.NET if you're using a managed code. -Make sure the module name of
with NET connectors » Solution for HTTP Error 500.21 - Internal Server Error - Bad module "ManagedPipelineHandler" on IIS 7.5 13 comments - This problem http://www.itcsolutions.eu/2010/09/06/solution-for-http-error-500-21-internal-server-error-bad-module-managedpipelinehandler-on-iis-7-5/ has been encountered after the production server has been upgraded to Windows http://www.winsysadminblog.com/2011/08/fixing-http-error-500-21-internal-server-error-handler-webservicehandlerfactory-integrated-has-a-bad-module-managedpipelinehandler-in-its-module-list-on-iis/ Sever 2008 R2 and the ASP.NET solution has been moved on the .NET 4.0 platform. The ASP.NET application was put to run in a ASP.NET v4.0 with Integrated Managed Pipeline application pool. The application was updated using Visual Studio 2010.After installing the necessary IIS 7.5 roles and features and publishing the website, http error i have encountered this error HTTP Error 500.21 - Internal Server Error Handler "WebServiceHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list. In the Visual Studio Development Server the site was running fine, until we tested the Crystal Reports………, but this is another problem. If I change the application pool to Classic .NET AppPool the problem does not persist, but it is http error 500.21 not the solution. On the error page, most likely causes are: manged handler is used; however, ASP.NET is not istalled or is not installed completely; there is a typographical error in the configuration for the handler module list. The first suggestion is the most likely to be true and after searcing the Web I found the source of the problem: installing SQL Server 2008, after installing Visual Studio 2010 may corrupt IIS Machine level configuration files: Installing VS2010 before VS2008 Results In Corrupt IIS Machine Level Configuration Files Solutions for this problem are: silent repair of the 4.0 .NET Framework for 32 bit servers with .Net Framework version 4.0.30319 run the command (in command prompt):%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart for 64 bit servers with .Net Framework version 4.0.30319 run the command:%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart install the ASP.NET version and configure IIS to use it open command prompt (Start -> cmd) and for 32 bit servers run the command%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe /i open command prompt (Start -> cmd) and for 64 bit servers run the command%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe /i Tags: ASP.NET, IIS, Windo
500.21 - Internal Server Error Handler "WebServiceHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list on IIS. I was recently developing some .net web applications at work and finally took the plunge of setting up a server to host them after I was happy that we had reached the point where they were usable applications. So after setting up Server 2008 R2, I went ahead and enabled IIS with asp.net configuration enabled along with a host of other modules enabled to support what we were after. Gave the server a reboot and everything was up and ready to go. Moved over to my development machine and instructed Visual Studio to publish an application to this newly setup web server, everything up until this point had worked perfectly, the web app published without any errors. So I opened up Internet explorer and low and behold error, page cannot be displayed. So I’m like maybe it’s a permissions thing, remoted into the web server and viewed it as a localhost and got Error 500.21 - Internal Server Error Handler "WebServiceHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler". I had gone ahead and configured an application pool for the web apps we were going to use, and everything seemed OK. I then remembered something, in the good old IIS 6 days you had to run a .net registration program to notify IIS you had it installed and register the handlers for .net, but thinking to myself this is now 2008 R2, come on, it couldn't be that. I opened up an elevated command prompt window and navigated to C:\Windows\Microsoft.NET\Framework\v4.0.30319 and ran aspnet_regiis.exe -i causing asp.net to register itself with IIS and enable the handlers required to run .net pages. After running this command I rebooted IIS and bang the web application started working. An easy fix but a pity that it couldn't have run automatically when I insist on installing asp.net under the IIS configuration. Share this post with others:EmailLinkedInFacebookGoogleTwitterRedditMorePrintTumblrPinterest Related 48,609 views Posted on August 6, 2011August 6, 2011 by John 24 Comments Posted in IIS, Microsoft, Programming, Web Development Post navigation Speeding up LAN