Calling LoadLibraryEx on ISAPI filter “E:\ColdFusion10\config\wsconfig\2\isapi_redirect.dll” failed

[2Charlie]

Why am I getting this error when I've used the wsconfig within my "site-name" folder to bind my site to ColdFusion? It keeps looking for the isapi_redirect.dll inside of wsconfig\2\ instead wsconfig\1\ folder. Where do I look to make this correction?

[carl type3]

Hi,

Whats in ColdFusion11\config\wsconfig\wsconfig.properties file?

HTH, Carl.

[2Charlie]

This is what is showed.

#ColdFusion Web Server Configuration File

#Fri Nov 20 16:32:01 CST 2015

1=IIS,2,true,"",bitness64

1.srv=localhost,author

[carl type3]

This part "1=IIS,2" - two here says refer to  ColdFusion11\config\wsconfig\2 for ISAPI information.

Perhaps make a copy of wsconfig\wsconfig.properties then change 2 for 1. Restart IIS to re-read properties files.

Regards, Carl.

[2Charlie]

Tried that it still points to two instead of one with the same error.

[carl type3]

Odd. Wonder what is in ColdFusion11\config\wsconfig\1\isapi_redirect.properties file.

[2Charlie]

Here is what it showed:

extension_uri= /jakarta/isapi_redirect.dll

log_file= E:\ColdFusion10\config\wsconfig\1\isapi_redirect.log

log_level= info

worker_file= E:\ColdFusion10\config\wsconfig\1\workers.properties

worker_mount_file= E:\ColdFusion10\config\wsconfig\1\uriworkermap.properties

iis_buffer_enable= true

[carl type3]

Pardon my CF11 paste typo's before.

So appears CF webserver configuration files are ok.

Perhaps Windows IIS configuration file worth checking.

What you got in isapiCgiRestriction section of Windows\System32\inetsrv\config\applicationHost.config file?

Here is an example:

  <isapiCgiRestriction>

                <add path="E:\ColdFusion10\config\wsconfig\1\isapi_redirect.dll" allowed="true" description="tomcat_All" />

  </isapiCgiRestriction>

Again, Carl.

[2Charlie]

Here is what I have.

<isapiCgiRestriction notListedIsapisAllowed="false" notListedCgisAllowed="false">

                <clear />

                <add path="C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" allowed="true" groupId="ASP.NET v4.0.30319" description="ASP.NET v4.0.30319" />

                <add path="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" allowed="true" groupId="ASP.NET v4.0.30319" description="ASP.NET v4.0.30319" />

                <add path="E:\ColdFusion10\config\wsconfig\1\isapi_redirect.dll" allowed="true" groupId="tomcat_cspotadmin.uwec.edu" />

                <add path="E:\ColdFusion10\config\wsconfig\2\isapi_redirect.dll" allowed="true" groupId="tomcat_author-prod.uwec.edu" />

                <add path="C:\opt\shibboleth-sp\lib64\shibboleth\isapi_shib.dll" allowed="true" groupId="ShibGroup" description="Shibboleth Web Service Extension" />

</isapiCgiRestriction>

[2Charlie]

I commented out the following line and it's still show the same error.

<add path="E:\ColdFusion10\config\wsconfig\2\isapi_redirect.dll" allowed="true" groupId="tomcat_author-prod.uwec.edu" />

[carl type3]

CF10 has not been updated recently? Some of the updates run a newer version tomcat. Perhaps the ISAPI.dll is an older version between the site that works and the site that fails?

[2Charlie]

It has update 13 installed. We have another ROP with update 13 and it works fine.

[2Charlie]

Where is this tomcat set? Its entry type is showing as inherited.

[2Charlie · Accepted solution]

It seems I have to delete the wsconfig folder and recreate the coldFusion instances. There seemed to be some corruption or misconfiguration in one of the wsconfig folder.

[Vishnu22410012h6s8]

can you please tell the steps you followed to fix this issue after deleting the wsconfig folder?

[Vishnu22410012h6s8]

Sorry I couldn't understand what you mean by "recreate the colfusion instances."

[Charlie Arehart]

Vishnu, the author (2Charlie) was indeed unclear in referring to "instances", after discussing removal of the wsconfig folder.

First, to be clear "instances" are a feature in cf enterprise, developer, and trial where you can create one or more cf instances, beyond the original cfusion instance. This is not an option in cf standard.

But I don't think 2Charlie meant that. Instead, after removing wsconfig (which may not have been necessary), it WOULD of course be necessary to "recreate the CONNECTORS", which is simply about running the wsconfig tool, and connecting any site or all sites to your cf instance. 

That said, and to solve your problem, I have my doubts whether it's necessary to delete either the wsconfig OR connector's (let alone instances). 

When I see this error, it's usually a reflection of some unexpected misconfiguration, usually either in IIS or about file/folder permissions. 

First, if you're comfortable with iis configuration, check if the app pool used by the failing site is set to 32- or 64-bit.

You also haven't said what version of CF you're using, and whether your cf connector is 32- or 64-bit (which can be chosen in the wsconfig tool). For most, it would be 64-bit by default, so the app pool should match that. 

Next, what's the identity for the iis app pool? There are various possibilities, and with that there would be a needed corresponding access defined for that user or all iis users to the cf wsconfig folder(s). Again, normally these things just work, so when they are amiss there's something that's been done to change from defaults. As such, there are too many possible permutations to anticipate what you may find and how best to resolve it. 

Also, with unusual problems like this, an important question is whether things WERE working and then something changed. If so, what changed? 

But let's start with just my first question, about the bit-level. The answer may be there. 

And someone else, like Carl, who's still active here, may reply with yet another suggestion. 

(Finally, if you'd not noticed, you're resurrecting a thread from over 6 years ago though indeed, most problems from then do tend still to happen now. )