Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The HTTP Filter DLL <path to dll file> failed to load. The data is the error.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a DLL?
This error message can occur if a folder or file is corrupted. It can also be the result of a locked file, a lack of appropriate permissions, or a service that does not stop or start.
Dll: exchfilt.dll - See ME260204.
See ME259817 for information about this event.
ME812077 provides information on this event.
Woodrow Wayne Collins
For Small Business Server 4.5 as per Microsoft this event does not cause problems. See ME228747.
Dll: exchfilt.dll - I've got this error message after removing Exchange 5.5 from a server. Uninstalling Exchange removed the file from the server too. Go to IIS admin and look at the running WEB sites' properties. On ISAPI Filters tab you'll find the registration of the dll. From the name of the dll we can expect it is connected to Exchange so it is not needed any more. I removed it and that solved the problem. This might help in other cases.
This often means that the filter DLL is missing a needed DLL and can't load it. Try placing the related DLL's in either the filter DLL's directory or in C:\WINNT\SYSTEM32 (or equivalent system directory) and restarting IIS.
Dll: exchfilt.dll - You may receive this message when you actually uninstall Exchange 5.5 but forget to delete the "exchfilt" filter from the IIS Web site where you had installed OWA. If you have uninstalled Exchange, just go to the properties of the related(usually default) Web site from IIS Admin and remove the filter from ISAPI filters.
I received this error after installing 2 security updates from Microsoft, MS01-044 and MS01-033. I suspect MS01-033 caused this error. The error occurred after every restart and we are not running Outlook Web Access, which Microsoft suggests is the cause (ME260204). I resolved this issue by going into the Internet Service Manager and stopping both the Default Web Site and Administrative Web Site.
|Private comment: Subscribers only. See example of private comment|
|Links: ME228747, ME259817, ME260204, ME812077|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated