|
Home > Archive > IIS Index Server > May 2004 > Problems installing XML iFilter
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problems installing XML iFilter
|
|
| jwalton@cix.compulink.co.uk 2004-05-05, 4:35 am |
| One of my client's sites is hosted on a dedicated IIS server, by a company
who are very security conscious (i.e. "obsessed"). I am not permitted any
kind of remote administration.
The server very successfully runs my asp search application based upon the
MS Indexing Service. I have now enhanced the application to use an XML
metadata "database", and I need to use the MS XML iFilter. My attempts to
get the hosting company to install it have met with dismal failure. When
they get to the registration step, they get an error message;
specifically:
at (called from the folder where dll is installed):
regsvr32 xmlfilter.dll
they get:
LoadLibrary("xmlfilter.dll") failed
- A dynamic link library (DLL)initialization routine failed.
Server is probably Win2000 Server (or maybe Win2000 Advanced Server). I do
not know state of SPs.
Any suggestions please for a way forward?
Best Regards, John Walton
| |
| jwalton@cix.compulink.co.uk 2004-05-06, 3:35 am |
| In article <c7a8v6$drp$1@thorium.cix.co.uk>, jwalton@cix.compulink.co.uk
() wrote:
(see original)
Has no expert here any ideas *please* ? I am rather desperate!
Best Regards, John Walton
| |
| jwalton@cix.compulink.co.uk 2004-05-06, 7:34 am |
| Further information: I have written and run a little diagnostic on the
offending server, and discovered that I can only successfully "create
object" for the MS XML component, as follows:
MSXML2.DOMDocument.4.0 can be used.
MSXML2.DOMDocument.3.0 can NOT be used.
MSXML2.DOMDocument.2.6 can NOT be used.
MSXML2.DOMDocument can NOT be used.
Microsoft.XMLDOM can be used.
I note from the MS XML iFilter documentation that MSXML 3.0 is needed (
current presumably when the filter was written). Is it likely that the
iFilter explicitly uses the "3.0" object by name, and that is the reason
why it cannot be installed (registered) on the server?
Best Regards, John Walton
| |
| DougWallace 2004-05-11, 5:42 pm |
| You may want to give up on the Microsoft iFIlter. We have been using an XML
iFIlter from QuiLogic. It is far more robust.
<jwalton@cix.compulink.co.uk> wrote in message
news:c7d6hq$p5l$1@thorium.cix.co.uk...
> Further information: I have written and run a little diagnostic on the
> offending server, and discovered that I can only successfully "create
> object" for the MS XML component, as follows:
>
> MSXML2.DOMDocument.4.0 can be used.
> MSXML2.DOMDocument.3.0 can NOT be used.
> MSXML2.DOMDocument.2.6 can NOT be used.
> MSXML2.DOMDocument can NOT be used.
> Microsoft.XMLDOM can be used.
>
> I note from the MS XML iFilter documentation that MSXML 3.0 is needed (
> current presumably when the filter was written). Is it likely that the
> iFilter explicitly uses the "3.0" object by name, and that is the reason
> why it cannot be installed (registered) on the server?
>
> Best Regards, John Walton
|
|
|
|
|