You are viewing limited content. For full access, please sign in.

Question

Question

500.21 error when running Laserfiche Forms

Forms
Updated July 29, 2014
asked on July 28, 2014

In our test environment, after installing Laserfiche and Workflow, I attempted to install Laserfiche Forms, after installing all of the necessary pre-requisites (IIS, ASP.NET, IIS Authentication).  When I did, and I tried to access Laserfiche Forms, I experienced the following error:

 

HTTP Error 500.21 - Internal Server Error

Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

I have tried uninstalling and reinstalling forms, and I have also attempted to uninstall and reinstall IIS and .NET (enabling directory browsing), but I still can't seem to get this working.  One blog post said to try switching to Integrated Mode, but despite modifying this, I didn't get any further either.

 

One thing I haven't tried, when uninstalling and reinstalling Forms/IIS/ASP.NET, is cleaning the registry after uninstalling, however if there might be something I could try before attempting this again, I'd appreciate any suggestions anyone might have!

 

Marty Gaffney - Network Technician

Town of Okotoks

 

0 0

Answer

SELECTED ANSWER
replied on July 28, 2014

Marty,

 

Please go to IIS > Application Pools > FormsAppPool, make sure that .NET Framework version is 4.0.30319 and the Managed pipeline mode is set to Integrated.

 

Were you installing IIS after installing .NET Framework? You may try executing the following script from command prompt:

 

32-bit OS: %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

64-bit OS:  %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

 

Regards

1 0

Replies

replied on July 29, 2014

I couldn't remember what sequence I had installed the various add-ons, I think it was IIS then .NET but I'm not sure.  I was 99% sure I ran the above command on my machine previously, but this time it appears to have fixed it - thanks as always!  Through a blog post I thought I had changed the Application Pools from Classic to Integrated, good to know there's a graphical front end for this (if I ever need to dig around in here again).

 

I also ran into a "form invocation" error when trying to configure the default Web page (and AD synchronization settings) for Forms, but a repair of the Forms installation, as well as manually restarting the Forms Routing service, appears to have fixed this issue as well.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...