I'm gonna SHOOT the @#$% server!

Ok, I've had it with this thing!!! I'm running Windows Server 2003, SQL
Server 2000 with SP2 and SQLXML 3.0 SP2. I've configured a virtual directory
using the SQLXML IIS utility and all is well. BUT... when I try connecting
to the web service via VS.NET, I keep getting this...
ERROR: 400.100 Bad Request
HResult: 0x80004005
Source: Microsoft SQL isapi extension
Description: The virtual name could not be recognized
I even get that if I try browsing the WSDL file directly from IE.
Now I've checked the security, I've checked the configuration, I've checked
it all but to no avail! I'm gonna take a #@.$% hammer to this box!!!
Now the odd thing is if I disable the application on that virtual directory
(thus stopping the maaping through the DLL, I can properly browse the WSDL
file. HUH?
So... anyone got any ideas and if not, any bullets or a large mallet?
Mark
Please don't shoot.
I forwarded your problem to one of the people of the SQLXML team and hope he
will reply to you.
Best regards
Michael
"Mark A. Donohoe" <Mark (at) MarkDonohoe.com> wrote in message
news:D27F9BE8-F783-41E8-83B8-8A3393EDF2F4@.microsoft.com...
> Ok, I've had it with this thing!!! I'm running Windows Server 2003, SQL
> Server 2000 with SP2 and SQLXML 3.0 SP2. I've configured a virtual
> directory
> using the SQLXML IIS utility and all is well. BUT... when I try
> connecting
> to the web service via VS.NET, I keep getting this...
> ERROR: 400.100 Bad Request
> HResult: 0x80004005
> Source: Microsoft SQL isapi extension
> Description: The virtual name could not be recognized
> I even get that if I try browsing the WSDL file directly from IE.
> Now I've checked the security, I've checked the configuration, I've
> checked
> it all but to no avail! I'm gonna take a #@.$% hammer to this box!!!
> Now the odd thing is if I disable the application on that virtual
> directory
> (thus stopping the maaping through the DLL, I can properly browse the WSDL
> file. HUH?
> So... anyone got any ideas and if not, any bullets or a large mallet?
> Mark
|||Hi there,
Do you have the SOAP Toolkit 2.0 installed? SqlXml 3.0 SP2 requires it for
using web services. However, if you can wait a bit longer, we will be
releasing SP3 which removes that dependency so SOAP Toolkit is no longer
needed.
Thanks,
Irwin
Irwin Dolobowsky
Program Manager, SqlXml
http://blogs.msdn.com/irwando
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark A. Donohoe" <Mark (at) MarkDonohoe.com> wrote in message
news:D27F9BE8-F783-41E8-83B8-8A3393EDF2F4@.microsoft.com...
> Ok, I've had it with this thing!!! I'm running Windows Server 2003, SQL
> Server 2000 with SP2 and SQLXML 3.0 SP2. I've configured a virtual
> directory
> using the SQLXML IIS utility and all is well. BUT... when I try
> connecting
> to the web service via VS.NET, I keep getting this...
> ERROR: 400.100 Bad Request
> HResult: 0x80004005
> Source: Microsoft SQL isapi extension
> Description: The virtual name could not be recognized
> I even get that if I try browsing the WSDL file directly from IE.
> Now I've checked the security, I've checked the configuration, I've
> checked
> it all but to no avail! I'm gonna take a #@.$% hammer to this box!!!
> Now the odd thing is if I disable the application on that virtual
> directory
> (thus stopping the maaping through the DLL, I can properly browse the WSDL
> file. HUH?
> So... anyone got any ideas and if not, any bullets or a large mallet?
> Mark