Error on IIS connector: "BonCode-Tomcat-CFM-Handler" has a bad module "ManagedPipelineHandler" in its module list

[Luis Majano]

I cannot get IIS latest with Railo 3 (latest) to work:

HTTP Error 500.21 - Internal Server Error

Handler "BonCode-Tomcat-CFM-Handler" has a bad module "ManagedPipelineHandler" in its module list

Anybody help on this?

[Jordan Michaels]

Hey Luis,

This is the version that came bundled with the Windows Installer? What
version of IIS are you using? What version of Windows?

I've never heard of anything like that happening before, but I wonder if
it's an incompatibility with an older version of .NET or something along
those lines?

I'd suggest giving the BonCode Connector a quick uninstall and
re-install. You can uninstall the BonCode Connector specifically from
the Windows Add-Remove Programs list.

Are you using .NET on the system? If not, it may be useful to clean out
any current .NET installs you have on the server already in case they're
older but not old enough to trip the BonCode Installer to install a
newer version (which it will do if it sees you don't have the .NET libs
it needs).

Then go here and grab a fresh copy of BonCode Connector:
http://tomcatiis.riaforge.com

... and let us know if you get the same error?

Warm Regards,
Jordan Michaels

[Luis Majano]

This is the version that came bundled with the Windows Installer? What
version of IIS are you using? What version of Windows?

 

Yes Jordan.

Windows Web Server 2008 R2

IIS 7.5

 

I've never heard of anything like that happening before, but I wonder if
it's an incompatibility with an older version of .NET or something along
those lines?

What version of .Net should I have installed? Sorry, I am not a big Windows guy.

Under the IIS sites, there is a Default App Pool and it says .Net version 2.0

 

I'd suggest giving the BonCode Connector a quick uninstall and
re-install. You can uninstall the BonCode Connector specifically from
the Windows Add-Remove Programs list.

Are you using .NET on the system? If not, it may be useful to clean out
any current .NET installs you have on the server already in case they're
older but not old enough to trip the BonCode Installer to install a
newer version (which it will do if it sees you don't have the .NET libs
it needs).

Should I install .Net 4.5?

[Luis Majano]

Jordan,

I installed .Net 4.5 and then ran the installer from the location you requested.  I know get this:

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

[Igal]

well, this error message is not telling much (on purpose).

follow the instructions in that error message to enable the full error so you can see what's going on.  you can later on disable the customErrors again.

[Bilal]

Luis:

The initial message "bad module" is a good indicator that the .net extensibility framework failed to install or the .net version used in your application pool is incorrect (have most likely been modified from default).

There is a brief mention on this in the trouble shooting section:

http://boncode.net/connector/webdocs/Tomcat_Connector.htm#_Toc332876581

To make things work,

the current BonCode connector will need an application pool in integrated mode supporting .net version 3.5. 

Unfortunately, Microsoft will still identify this as version 2.0.50727.

It should look like attached image.

Everything that is needed will be installed by the connector installer, thus, you should not need to download anything unless you were prompted to or did a manual install. 

Here is the order of checks:

a) Check for .net framework 3.5 feature (in server administrator) 

b) Check the Application Pool for the IIS site. Make sure it is .net Version 2.0.50727 and Managed Pipeline mode is "Integrated" (as attached image)

c) Check for role services, IIS should have the .net extensibility feature installed. If not, try to install it and see what errors you get in Event Log.

If you are getting other errors at that point my guess is that you had some changes to IIS you are no longer aware of that we will need to work through.

Best,

Bilal

[Luis Majano]

Thanks for the update guys.

I verified that .Net Extensibility was NOT installed. I went to the add role features and tried to add ASP .Net with .Net Extensibility and the installer fails with an error code.  Tried it by itself and same issue.  Rebooted, tried again and it failed. 

Searched the error ode that took me to microsoft for a fix it download. Did and tried again and failed.  So I am really not confident anymore that IIS is ok. 

So I will try to uninstall it first and report back.

[Luis Majano]

Guys quick question.

If before I install the connector, the .Net extensibility is not installed, should I install that first or let the connector run first.

[Bilal]

The connector installer will do all the work and may be easiest.

[Luis Majano]

Ok Guys,

Still same issue.  On a vanilla iis install with the .Net Extensibility not installed by default, I installed Railo without the connector, downloaded the latest from the link provided and installed.  Then it gives that exception.

I also tried adding the extensibility manualy and fails.  I am really at a loss here.  Any comments?

http://ortus-temp.s3.amazonaws.com/iis_install1.mp4
http://ortus-temp.s3.amazonaws.com/iis_install2.mp4

[Bilal]

Luis:

I see that you are using Amazon AMIs; we had some issue a while back with certain Amazon Amis; they did not install certain roles and role features. Thus, elements of IIS and Active Directory could not be installed.

We had to change the base image in this fashion:

a) Change the page file for the OS. It was set to 512KB when it should have been 8GB; this prevented installation from succeeding.

b) We had to increase the CPU priority of the "Trusted Platform Installer" process to high. This is the process windows uses to add/remove system components.

The connector installer uses the underlying Platform installer to add features to IIS on Win 2008+.

Whether the above or something else is the issue would need to be determined.

At this point we will have to troubleshoot your OS image.

What is the Event Log message in Windows after the attempted install, or when you try to add the feature via Server Manager UI tool?

Depending on schedules we could walk through a interactive skype session and post resolution here or you can create an account on the new machine for troubleshooting and sent me the access to my regular email (bilal dot soylu at gmail dot com) for me take a look.

Best,

Bilal

[Luis Majano]

Hi Bilal,

They finally re-installed IIS with .Net extensibility and .Net enabled.

I did another install of the connector and the installer ran correctly this time.  I checked the handler mappings and they are there.  However, the web.config is empty.  Does the connector need write capabilities to the document root web.config? What exactly needs to exist inside of the web.config for this to work?

As I restarted and tried again and still get:

HTTP Error 500.21 - Internal Server Error

Handler "BonCode-Tomcat-CFM-Handler" has a bad module "ManagedPipelineHandler" in its module list

I verified and the default pool is in integrated mode and using 2.0.50727 now.  Am I missing something?

[Luis Majano]

Here are some images

[Igal]

I was getting this error when I uninstalled the BonCode connector and then tried to reinstall it.

I believe that the problem is that the the system is missing .NET3.5;  in my case I couldn't even reinstall .NET3.5 on that machine because I had .NET4.0 there but that was a Microsoft issue, and not a connector one.

[Luis Majano]

.Net 4.5 is isntalled on the machine, do I need to uninstall it?

[Igal @ getRailo.org]

are you able to install .NET3.5 without uninstalling the newer version?

-- 
Igal Sapir
Railo - Open Source CFML Engine
http://getrailo.org

[Luis Majano]

I thought it was installed by default since IIS was installed with the ASP.Net role.  Also the defaultPool reports the 2.0 version as well.

[Igal @ getRailo.org]

on my machine I have v2.0 and v4.0 but not v3.5 or at least that's what I see in IIS.

the weird part is that when I go to:  %windir%\Microsoft.NET\Framework

I see v3.5 as well.

anyway, I'm not sure.  maybe Bilal will answer this when he sees this thread.


Igal

[Bilal]

All of this looks normal.

The .net framework version 3.5 identifies itself as 2.x to IIS.

The connector installer checks for version 3.5 dlls and will let you know if anything is needed.

Thus, most likely it is installed.

No special permissions should be needed for the connector to work unless you want to log activity. Then the permissions need to be given to IIS user to access log directory.

You can verify that you have unblocked the .dll files if you have installed in site-by-site mode:

http://boncode.net/connector/webdocs/Tomcat_Connector.htm#_Toc332876574 

From the error you received though I am guessing that some other configuration have taken place on this IIS machine and are still not quite right.

Let's see whether we can clean the web.config elements.

I would backup existing web.config files and, then delete them from current location.

Now try to use a cfm page?

If you receive a 404, add a handler manually (you can also run the connector installer again if you like to do this).

What do you see now?

Best,

Bilal

[Jordan Michaels]

I recently encountered this issue myself and after screwing with it for several hours I was able to correct it by removing everything related to .NET from the add/remove programs list. To be thorough, I also removed IIS at the same time. I rebooted. Reinstalled IIS, then ran the Railo installer, (with the boncode connector included) and everything seemed to work okay after that. There's probably some conflict between .net 4+ and the version that the BonCode connector needs.

-Jordan

[Bilal]

This error seems to be common when we have multiple installation of .net framework. When the order of .net installs is such that a prior version (e.g. 3.5) is installed after a more current version (e.g. 4.5) was already installed. This will "confuse" IIS as to the default Application pool handler. IIS is uncertain which version of .net to activate in all cases.

The solution is to remove all .net frameworks, then install them in the order of release version (e.g. first 3.5 then 4.5).

The connector can work with any of the ones that are 3.5+.

The connector installer will not install a .net framework if a compatible one is already there.

You can of course remove the whole stack (.net and IIS) and redo as well to reset things.

-Bilal

[Jordan Michaels]

Another update on this. I just ran into this issue again this afternoon and I was able to *quickly* address it by modifying the .NET version for the application pool for the site. Apparently the default .NET version for application pools for new sites is 2.0 (microsoft logic??). I switched the version of the Application Pool from 2.0 to 4.0, restarted the Application pool for the site, and everything came up peachy. It's a lot faster than uninstalling/re-installing. Just in case anyone else finds this thread via Google as I just did (again).

-Jordan

[Igal Sapir]

You can set the default for new sites on that server to be v4.0

--
Did you find this reply useful? Help the Railo community and add it to the Railo Server wiki at https://github.com/getrailo/railo/wiki
---
You received this message because you are subscribed to the Google Groups "Railo" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/railo/4bb69890-b149-43d5-9e67-2b0adf0969e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jordan Michaels]

Thanks Igal. I guess my frustration is that if the newest version is installed and available, why isn't the newer version the default already? It's cool though. It's just my Win7 box at home. I was having fun with a project and wanted to work on it at home this weekend. ;)

Thanks again,

-Jordan

[Igal @ getRailo.org]

my best advice to you would be: replace IIS with nginx.

it's one of the best decisions I made in the last couple of years with
respect to my servers.

--
Igal Sapir
Railo Core Developer
http://getRailo.org/

[Robert Zehnder]

+10000000

[Jordan Michaels]

Understood my friend. The only reason I have that windows box is to
satisfy my gaming addiction, but this weekend I was getting some pretty
good fun points from my new project. I don't use windows for production
servers myself, and for my Linux servers I'm happy with Apache.

Warm Regards,
Jordan Michaels