Re: Shoot the @#%$ Server - Part 2
From: at (Mark)
Date: 10/16/04
- Next message: at: "SQLXML, SOAP, VS.NET 2003 and Default Params"
- Previous message: billr: "Re: IIS Virtual Server for SQLServer ... not authorised to view"
- In reply to: Irwin Dolobowsky [MS]: "Re: Shoot the @#%$ Server - Part 2"
- Next in thread: Irwin Dolobowsky [MSFT]: "Re: Shoot the @#%$ Server - Part 2"
- Reply: Irwin Dolobowsky [MSFT]: "Re: Shoot the @#%$ Server - Part 2"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 15 Oct 2004 21:07:08 -0700
Ok... it's now working. Common sense told me to specify the actual file but
apparently the syntax you provided works.
Couple things for ou to be aware of though. I actually wasn't manually
specifying the WSDL file and instead was using VS.NETs ability to look on the
local machine. It found the service fine, but when you tried to browse it to
connect to it, you get the messages that I posted. If however you manually
type the URL you provided and *don't* use the built-in browsing feature, it
works. Not exactly the most intuitive solution I might add. I wasted a good
seven hours tracking down something that didn't need to be had the browse
worked.
Also, I saw you mention in another post that SP3 is coming soon. How long
until that happens?
Thanks again! I'm glad it's up.
Mark
"Irwin Dolobowsky [MS]" wrote:
> The correct path should be:
>
> http://SomeServer/SqlXmlVDir/SoapVname?wsdl to get the WSDL file.
>
> --
> 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:4BBAAEAB-ABB8-4C12-9235-42BA1CFCA0ED@microsoft.com...
> > When I try to browse the wsdl file directly (i.e.
> > http://SomeServer/vdir/MyProcs.wsdl) I get the first error message.
> > That's
> > setting the Path value to a period (.) to place the wsdl file directly in
> > the
> > v-dir. If I change the path to say 'sp' (so the url becomes
> > http://SomeServer/vdir/sp/MyProcs.wsdl) I get the second error message.
> > I've
> > never tried it with 'http://Server/nwind2/soap?wsdl' as I'm not sure which
> > is
> > which there. I'm assuming nwind2 is the vdir and soap is the path for the
> > v-name? If so, what is the vname? ...and if SOAP is the path for the
> > v-name, then in my case since I placed the WSDL files directly in the
> > v-dir's
> > root, would it just be http://Server/nwind2?wsdl?
> >
> > Mark
> >
> > "Bertan ARI [MSFT]" wrote:
> >
> >> Can you connect the web service via IE?
> >>
> >> The first error message indicates that there is simply no matching SQLXML
> >> vdir on the system.
> >>
> >> The second one is indicating that you are trying to access another path
> >> in
> >> SOAP vname which shows that you are putting something after the soap
> >> vdir.
> >>
> >> Actually all you need to put:
> >>
> >> http://Server/nwind2/soap?wsdl
> >>
> >> in VS.NET to setup the webservice.
> >>
> >> Thanks
> >>
> >> --
> >> Bertan ARI
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Mark A. Donohoe" <Mark (at) MarkDonohoe.com> wrote in message
> >> news:23856A3A-9854-4183-9EB6-317245A31FD1@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
> >> >
> >> > This is what I get if I use '.' as the path (i.e. this places the WSDL
> >> right
> >> > in the virtual directory.) However, if I try specifying a path
> >> > property
> >> of
> >> > say 'SPs' which is under the virtua directory, I get this...
> >> >
> >> > HResult: 0x80004005
> >> > Source: Microsoft SQL isapi extension
> >> > Description: There should be no path or parameters after a SOAP
> >> > vname.
> >> >
> >> > 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???
> >> >
> >> > I give up!!!
> >> >
> >> > So... anyone got any ideas and if not, any bullets or a large mallet?
> >> >
> >> > Mark
> >>
> >>
> >>
>
>
>
- Next message: at: "SQLXML, SOAP, VS.NET 2003 and Default Params"
- Previous message: billr: "Re: IIS Virtual Server for SQLServer ... not authorised to view"
- In reply to: Irwin Dolobowsky [MS]: "Re: Shoot the @#%$ Server - Part 2"
- Next in thread: Irwin Dolobowsky [MSFT]: "Re: Shoot the @#%$ Server - Part 2"
- Reply: Irwin Dolobowsky [MSFT]: "Re: Shoot the @#%$ Server - Part 2"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
