Skip to main content
Participating Frequently
November 2, 2023
Question

Adding a second IIS site & adding the site to the CF connector throws 500 error on isapi_redirect.dl

  • November 2, 2023
  • 2 replies
  • 895 views

Hi,

 

The full error of course is:

HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\cf2021cloud\config\wsconfig\2\isapi_redirect.dll" failed

 

I am setting up a new server,  and  I have one site running under IIS with cold fusion and works swimingly. 

It's magic number is 1 and all is well. The problem occured when I created a new IIS site and ran the cf connector and chose add. The connector did its thing and created the jakarta virtual dir etc and added an isapi filter pointing to magic number 2 this time.

 

I have checked permissions across the board and confirmed paths, the simple stuff. my question is really is there something I missed when adding a second IIS site after cf was already connected ? I didnt see a way to edit my original connector or anyting, looked like I needed to add a second one. IM struggling to find docs related to this problem - ive posted a screen shot of the error. also showing the directories just confirming they exist I guess.

The properties files look good to me and there is nada in the IIS logs to help. It's seems like its like an IIS permissions problem rather than a cf problem but I thought maybe somebody had some ideas. 

 

Thanks 

 

Patrick 



This topic has been closed for replies.

2 replies

Charlie Arehart
Community Expert
Community Expert
November 2, 2023

If the issue is not the bit level of the app pool, consider then a permissions issue (also related to the app pool). View what is the identity for the app pool (listed as a column on the IIS application pools page). Is it simply "application pool identity", which is the default, or is it something else?

 

Then check the permissions of the config/wsconfig/2 folder. Does it list either that user, or (if the user was "application pool identity") does it list either of the groups iusrs or iis_iusrs? The user needs at least read access, but also write access for the isapi_redirect.log file there.

 

Finally the user also needs read access to the website root. 

 

Any of these could be different for the working site compared to the failing one, because of things done outside of and before you created the new connector. 

/Charlie (troubleshooter, carehart. org)
Participating Frequently
November 2, 2023

Thank you for your help Charlie. The new App Pool being used is set to 32 bit false, I also think this has to do with permissions. Im going to dig into that now and will update you?

 

Question: Would it make sense to remove both connectors and add a new one and select all sites? Or maybe use the working" connector for the new site?

Charlie Arehart
Community Expert
Community Expert
November 2, 2023

Well, it may or may not. To be clear the permissions are not "in the connector" but in the app pool used by the site. Changing what connector the site uses won't change the permissions of the app pool.

 

But if somehow the permissions of the pool are such that it WOULD work with the old connector, changing it to use that could help.

 

As for creating a new one, that's more iffy, as we don't know what permissions that would have by default. You may find that now the old working site would stop.

 

Really, it's better to work to diagnose and understand a problem like this, rather than "try some fix". Note how I've given pointers to do that. It's far too common in most forums and social media for people to suggest darts when what's needed is a flashlight. Of course, it takes time (and more words) to do that work. But as I note above, some "fixes" will only make things worse, and sometimes irrevocably so.

 

Always best to takes backups or make snapshots before such changes. But that takes time also...and when it comes to permissions, those can change for files as they are copied to other folders. That's another vote for looking before leaping.

 

BTW, I write such things to help all who may read this, now or in the (perhaps distant) future. It's never personal (unless I make it clearly so, which is rare). Some can take admonitions the wrong way. We're just here to help each other. 

/Charlie (troubleshooter, carehart. org)
Charlie Arehart
Community Expert
Community Expert
November 2, 2023

First, check if the application pool for this failing site is set to run as a 32-bit app pool. If so, unless you need it to be thatf (or some reason other than cf), change it 32-bit false. Test the site again, then let us know how it goes.

 

You can Google to find details of how to do the above, including making sure you're checking/changing the correct app pool. Or let us know of challenges. 

/Charlie (troubleshooter, carehart. org)