[posted and mailed, please reply in news]
Rob Hindman (robhindman@hotmail.com) writes:
[quoted text, click to view] > I have an extended stored procedure on SQL Server 7 (a C++ DLL) that I
> am migrating to SQL Server 2000. The extended sproc calls the
> SoapToolkit 2.0 sp2. This works great on SQL Server 7, but fails on
> SQL Server 2000. The call to mssoapinit() fails with 0x80004001
> (-2147467263 in decimal). This error means that the method is not
> implemented.
>
> My current theory is that the extended stored procedure is trying to
> load the MSXML DLL, which partitially succeeds - I think that probably
> an older version of MSXML (I have read that it is MSXML 2.6) is loaded
> by SQL Server 2000, so the ISOAPClientPtr interface can't really be
> correctly accessed...
>
> Has anyone seen something like this before? Does this theory seem
> plausible? Does anyone know how to determine which version of MSXML
> SQL Server 2000 is using? (I have used Visual Studio 6.0's "Depends"
> tool to try to see which DLLs the "sqlservr.exe" file loads, but it
> does not indicate that MSXML is loaded.)
I guess that this is what they call an advanced question...
You might get some better assistance in microsoft.public.sqlserver.xml.
I can only add my own speculations. SQL7 does not support XML at all,
so it is not likely to load any XML DLLs. SQL2000 has XML support and
may load XML DLL, and it may not be the one you want. What could be
worth trying is to download the most recent version of SQLXML, I think
this is 4.0. I don't really know how that affects SQL Server.
Also, check @@version for which version of SQL Server you are using.
8.00.760 is SP3, which is the latest service pack. You may have better
luck with that version, in case you are using RTM (8.00.194) now.
--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se
Books Online for SQL Server SP3 at