IIS6 isapi filter
in [IIS]
|
From: David Wang [Msft] on 17 Feb 2005 22:31 I repeat: Until you troubleshoot based on the error code, you are just making random changes that may/not actually solve anything. Anyways, let's just concentrate on troubleshooting the actual issue and not get frustrated by your random guesses at the problem. Really, IIS is telling you what is wrong; you just have to learn to listen to it. Starting from the error event itself -- If you look up Win32 Error 0x7E on MSDN or Google (0x7E in hex is 126 in decimal), via "net helpmsg 126" (or winerror or any such error code lookup tool easily found in the platform SDK, via a web search, etc) it returns: The specified module could not be found. This means either: 1. The actual Filter DLL you configured IIS to load is not there 2. A DLL which the filter DLL depended on is not located on the server. To troubleshoot #1 Make sure that the full path to the Filter DLL is correctly matched in IIS configuration To troubleshoot #2 Run "DEPENDS.EXE" from the platform SDK on your Filter DLL, and it should quickly tell you what DLL(s) are missing. Based on your description, I would first try: dir C:\isapi_filter\yISAPI_AUTH_001.dll and see if that succeeds. yISAPI_AUTH_001.dll seems like an odd name that may have a typo (extra "y") in it. If the above works, then run DEPENDS.EXE yISAPI_AUTH_001.dll on the DLL file itself and look for any red boxes (which signify missing linkages). Classic user mistakes at this point include: 1. compiling the filter DLL as debug (instead of retail), which causes the DLLs to link against debug runtime libraries that are *not* on any normal server that has not been set up for debugging 2. compiling the filter DLL against a newer version of C/MFC/ATL libraries that are not on the server (i.e. if you compile on VS.Net or VS.Net 2003, you will have linkage against v7.0 or v7.1 libraries while the OS would obviously not have them ). Classic user mistake #1 happens when you install VS.Net to a development machine, which installs the debug runtime DLLs on the machine such that everything magically works on that machine, but as soon as you copy it to a real server (which usually does not have VS.Net installed), it fails. Classic user mistake #2 happens when you lose track of what your Filter DLL actually depends on (which is a user error -- you always must know what you are compiling and taking a dependency on, especially if you wish to deploy the DLL to another machine. The provider of the filter DLL must give correct deployment instructions, including dependencies, since they are responsible ). If your problem does not match any of the above symptoms and classic remedies, we will need to gather more details about your particular DLL source code and server setup. -- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "Charlie" <test(a)test.ca> wrote in message news:edw5phQFFHA.1836(a)tk2msftngp13.phx.gbl... I've installed the Latest SDK's and set my XP env to win2003 server like so: SetEnv.Bat /SRV32 /DEBUG same problem and error though "David Wang [Msft]" <someone(a)online.microsoft.com> wrote in message news:uTt3OxJFFHA.628(a)TK2MSFTNGP15.phx.gbl... > Can you please post the "data" of error event ID 2214 (it is a number). > That number will tell me what is wrong and how to fix it. > > Until you troubleshoot based on the error code, you are just making random > changes that may/not actually solve anything. > > -- > //David > IIS > http://blogs.msdn.com/David.Wang > This posting is provided "AS IS" with no warranties, and confers no rights. > // > "Charlie" <test(a)test.ca> wrote in message > news:u5BYWxHFFHA.3312(a)TK2MSFTNGP15.phx.gbl... > I commented out the function to write to the file, so that's not the problem > > It's something else.... > (same error though) > > > > "Charlie" <test(a)test.ca> wrote in message > news:%2318QwlHFFHA.1348(a)TK2MSFTNGP14.phx.gbl... > > I have a VERY simple isapi filter on my WinXP Pro localhost working just > > fine, all it does is append a line to a text file when a request comes in. > > > > I moved it to Win2k3 / IIS6 and I get the following event log errors: > > > > 1. > > ------------------------------------------ > > Event Type: Error > > Event Source: W3SVC-WP > > Event Category: None > > Event ID: 2268 > > Date: 2/16/2005 > > Time: 5:40:34 PM > > User: N/A > > Computer: NONE-1GS5PYKZ3T > > Description: > > Could not load all ISAPI filters for site/service. Therefore startup > > aborted. > > ------------------------------------------- > > > > 2. > > ------------------------------------------- > > Event Type: Error > > Event Source: W3SVC-WP > > Event Category: None > > Event ID: 2214 > > Date: 2/16/2005 > > Time: 5:40:34 PM > > User: N/A > > Computer: NONE-1GS5PYKZ3T > > Description: > > The HTTP Filter DLL C:\isapi_filter\yISAPI_AUTH_001.dll failed to load. > The > > data is the error. > > ------------------------------------------- > > > > p.s. > > from frustration, I've set file and directory permissions to full control > to > > almost everyone where the isapi dll is and where the file is that I append > > to. > > > > > > > > > > > |