Error 2214: The HTTP Filter DLL %1 failed to load. The data is the error.

Hardcore

unread,

Dec 20, 2002, 4:09:26 PM12/20/02

to

Anyone ever seen the w3svc event below?

2214 The HTTP Filter DLL %1 failed to load. The data is
the error.

I am trying to load up a 3rd party ISAPI filter (ATG
Dynamo ConnectionModule for IIS) and am not even getting
past stage 1...

HELP!!!

Lisa Cozzens [MSFT]

unread,

Dec 20, 2002, 4:44:04 PM12/20/02

to

When you view the event, there should be a section called "Data." What is
listed in there?

Thanks,
Lisa

--------------------
> Content-Class: urn:content-classes:message
> From: "Hardcore" <mhar...@depoint.com>
> Sender: "Hardcore" <mhar...@depoint.com>
> Subject: Error 2214: The HTTP Filter DLL %1 failed to load. The data is
the error.
> Date: Fri, 20 Dec 2002 13:09:26 -0800
> Lines: 10
> Message-ID: <01a601c2a86c$13d648e0$d5f82ecf@TK2MSFTNGXA12>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
> Thread-Index: AcKobBPT+vH+4b6CRK69cwUhlxzKUQ==
> Newsgroups: microsoft.public.inetserver.iis
> NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
> Path: cpmsftngxa06!TK2MSFTNGP08!cpmsftngxa09
> Xref: cpmsftngxa06 microsoft.public.inetserver.iis:237463
> X-Tomcat-NG: microsoft.public.inetserver.iis

-----
Please do not send email directly to this alias. This is an online
account name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers
no rights. You assume all risk for your use.

Hardcore

unread,

Dec 20, 2002, 4:57:23 PM12/20/02

to

Hi Lisa,

Depending on whether I choose 'Bytes' or 'Words,' here is
what I see...

Bytes-
0000: 7e 00 00 00 ~...

Words-
0000: 0000007e

Thanks!

Matt

>.
>

Lisa Cozzens [MSFT]

unread,

Dec 30, 2002, 3:26:12 PM12/30/02

to

Hi Matt,

Is the ISAPI filter showing up as loaded? You can check by opening the
Internet Services Manager -> Right click on server name -> Properties ->
Edit button next to WWW Service -> ISAPI Filters. Make sure the filter is
listed and that it's showing with a green up arrow next to it. If it has a
red down arrow, verify that the executable path is correct by clicking on
the filter and clicking the Edit button.

Thanks,
Lisa

--------------------
> Content-Class: urn:content-classes:message

> From: "Hardcore" <mhar...@dewpoint.com>
> Sender: "Hardcore" <mhar...@dewpoint.com>
> References: <01a601c2a86c$13d648e0$d5f82ecf@TK2MSFTNGXA12>
<HdO9MDHqCHA.896@cpmsftngxa09>
> Subject: RE: Error 2214: The HTTP Filter DLL %1 failed to load. The data
is the error.
> Date: Fri, 20 Dec 2002 13:57:23 -0800
> Lines: 74
> Message-ID: <01e201c2a872$c68cf5a0$d5f82ecf@TK2MSFTNGXA12>

> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"

> Content-Transfer-Encoding: quoted-printable

> X-Newsreader: Microsoft CDO for Windows 2000
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300

> Thread-Index: AcKocsaMU+Okl+uySz2FxFL51Y+hsg==

> Newsgroups: microsoft.public.inetserver.iis
> NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164

> Path: cpmsftngxa06!cpmsftngxa10!cpmsftngxa09
> Xref: cpmsftngxa06 microsoft.public.inetserver.iis:237469
> X-Tomcat-NG: microsoft.public.inetserver.iis

Matt Hartman

unread,

Dec 30, 2002, 6:08:37 PM12/30/02

to

Lisa,

Thanks for getting back so quickly.. To answer your
question, the ISAPI is NOT being loaded at all (hence the
error mesasage). If I use the GUI interface I can see the
red down arrow (the paths are completely correct both in
the registry and the GUI).

What I am assuming is IIS and/or Windows does not like the
dll (used for ATG Dynamo 5.6.1 - very popular).

Does this ring any bells?

Thanks so much,
Matt

>.
>

Lisa Cozzens [MSFT]

unread,

Dec 31, 2002, 1:15:37 PM12/31/02

to

Hi Matt,

You mentioned that the path is correct in the registry -- are you seeing
the DLL listed in the registry under
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3svc\Parameters\Filter
DLLs? If so, please use regedt32 to (carefully!) remove the value of that
key. The key should still exist in the registry, but it needs to have an
empty value. The reason for this is that this is a legacy registry key used
only with IIS 3 and earlier. IIS 4 and later don't obtain information on
ISAPI filters from that key. (I'm assuming, of course, that you're not
running IIS 3 or earlier. If you are, I would highly recommend installing
the NT Option Pack so you can get on IIS 4, if for no other reason than the
lack of security patches for IIS 3.)

Also, try registering the DLL using regsvr32.

I don't know of any known issues with ATG Dynamo and IIS. Have you tried
reinstalling, or at least recopying the DLL? Perhaps a couple bits got
mixed up during the original installation.

Hope this helps,
Lisa

--------------------
> Content-Class: urn:content-classes:message

> From: "Matt Hartman" <mhar...@dewpoint.com>
> Sender: "Matt Hartman" <mhar...@dewpoint.com>
> References: <01a601c2a86c$13d648e0$d5f82ecf@TK2MSFTNGXA12>
<HdO9MDHqCHA.896@cpmsftngxa09>
<01e201c2a872$c68cf5a0$d5f82ecf@TK2MSFTNGXA12>
<JJTmSGEsCHA.896@cpmsftngxa09>

> Subject: RE: Error 2214: The HTTP Filter DLL %1 failed to load. The data
is the error.

> Date: Mon, 30 Dec 2002 15:08:37 -0800
> Lines: 151
> Message-ID: <2da101c2b058$62560390$8bf82ecf@TK2MSFTNGXA05>

> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> X-Newsreader: Microsoft CDO for Windows 2000
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300

> Thread-Index: AcKwWGJWfhG+YB8CQqisCOJI/o4RCQ==
> Newsgroups: microsoft.public.inetserver.iis
> Path: cpmsftngxa06
> Xref: cpmsftngxa06 microsoft.public.inetserver.iis:238140
> NNTP-Posting-Host: TK2MSFTNGXA05 10.40.1.49
> X-Tomcat-NG: microsoft.public.inetserver.iis

Wade A. Hilmo [MS]

unread,

Dec 31, 2002, 10:58:19 PM12/31/02

to

Hi Matt and Lisa,

There are three cases were IIS will fail to load a filter:

1. The filter is not registered in the metabase. In this case, you won't
see the filter in the MMC, and you won't see an event, so that is clearly
not what's happening here.

2. IIS's call to load the dll fails. This can happen for a number of
reasons. If IIS can't find the dll, can't access the dll, or if the OS
can't load it for some reason, a failure will occur here. Also, it's
possible that the filter is found and actually loaded, but the filter's
entry point function (often called DllMain) returns FALSE.

3. The dll is found and loaded correctly, but its GetFilterVersion function
returns FALSE. In this case, IIS immediately unloads the filter.

In cases 2 and 3 above the hex data in the event log ("the data is the
error") will be relevant. In the case where the OS cannot load the filter,
this value will correspond to a Win32 error code explaining the failure. In
the case where the filter's entry point or GetFilterVersion function returns
FALSE, the value will correspond with whatever last error the filter set.

If you can post the actual data from the error code, we may be able to tell
you what it means.

Thank you,
-Wade Hilmo,
-Microsoft

"Lisa Cozzens [MSFT]" <lcoz...@online.microsoft.com> wrote in message
news:516qciPsCHA.3108@cpmsftngxa06...

Matt

unread,

Jan 2, 2003, 10:38:30 AM1/2/03

to

Hi Wade,

Here is the data/error message:

Words-
0000: 0000007e

Thanks!

Matt

>.
>

Wade A. Hilmo [MS]

unread,

Jan 2, 2003, 11:22:38 AM1/2/03

to

Hi Matt,

The second one is correct. The error is 0000007e in hex. If you convert
that to decimal, you get error 125. Looking up error 126 shows that it is
ERROR_MOD_NOT_FOUND. It is almost certain that this error is being
generated by the OS before the filter dll is ever touched. There are two
possible causes for it. First, if the path you've set for the filter is
incorrect, this error will result. If you can verify for certain that the
filter dll does live exactly at the path you've specified, then the error
means that some dll that the filter depends on cannot be found.

Troubleshooting the second issue is a bit less straight forward. The most
common cause that I've seen is when someone writes an MFC dependent dll in
debug mode and then deploys it on a production server (where the debug MFC
dlls aren't present). Since it sounds like you acquired the dll from a 3rd
party, I'm suspecting that this is not the case here. My first suggestion
is to contact them to see if they can tell you exactly what dlls they depend
on. If that doesn't yield good results, you can diagnose this problem
yourself by using a dependency walker tool. Microsoft ships one called
"depends.exe" with a number of products, like Visual C++, and in Windows
Resource Kits. Alternately, if you search the web for "depends.exe", you'll
see lots of tools available (I don't know anything about any of them that
weren't shipped by Microsoft, so I can't recommend or endorse any in
particular).

Thank you,
-Wade Hilmo,
-Microsoft

"Matt" <mhar...@dewpoint.com> wrote in message
news:065a01c2b275$0050ac80$d6f82ecf@TK2MSFTNGXA13...

Matt [YM]

unread,

Jan 2, 2003, 5:34:02 PM1/2/03

to

Wade,

Honestly, you rock. depends walked me thru and pointed out
the missing dll, msvcp60

On a side note, This happened on a fresh install of Win2k
Pro (all Windows Update up to date).. Most machines I have
seen have this dll (only this one was missing). Oh well,
no biggie I guess.

Thanks to all from MS who helped us on this, it was a
pleasure.

Happy new year!

>.
>