By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,948 Members | 664 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,948 IT Pros & Developers. It's quick & easy.

HTTP 400 error when calling a web service that is NOT installed in Default Web Site

P: n/a

I am using ASP.NET (framework 1.1), Windows 2003, IIS 6.0. I have a
VB.NET web service client that connects/calls a web service written in
ASP.NET (both applications are installed on the same server).

When the web service is installed in the Default Web Site within IIS,
the web service client has no problems connecting/calling the methods
of the web service.

But, when the web service is installed under a different web site in
IIS (i.e WEBSITE1), I get HTTP error 400 ("The request failed with HTTP
status 400: Bad Request").

Host headers are used as only 1 IP Address is configured for use on the
web server. I am able to ping WEBSITE1 without any problems. Even
when I copy/paste the full URL to my web service WSDL (i.e.
http://WEBSITE1/myService.asmx?WSDL) into a web browser, this works

Is the problem likely to be caused by a setting in the client
application or web service itself or a setting in IIS?

Thanks in advance.


Mar 23 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.