WebService Invoke --> Bad Request

Discussion in 'ASP .Net Web Services' started by Mark, May 5, 2005.

  1. Mark

    Mark Guest

    We have developed a new website and it is running OK on the dev. machine, now
    once we copied these files across to the live machine, it fails to invoke the
    webservice "HTTP status 400: Bad Request". We've got a brand new web server
    WIN2K3 with IIS6.0. Also, I have changed the URL Behavior to Dynamic and I
    have asked the ProxyObject to display the URL and it is pointing to the
    correct path. So, Why is the ASP.NET web app cannot invoke the web service at
    all.

    Any suggestions?

    Regards,
    Mark
     
    Mark, May 5, 2005
    #1
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Samuel
    Replies:
    0
    Views:
    675
    Samuel
    Jul 30, 2003
  2. Brian Birtle
    Replies:
    2
    Views:
    2,618
    John Saunders
    Oct 16, 2003
  3. Standist
    Replies:
    0
    Views:
    1,510
    Standist
    Feb 8, 2006
  4. С»ÒÀÇ

    Why invoke a webservice failed in asp.net ?

    С»ÒÀÇ, Dec 13, 2007, in forum: ASP .Net
    Replies:
    1
    Views:
    743
    Mark Fitzpatrick
    Dec 13, 2007
  5. rantingrick
    Replies:
    44
    Views:
    1,915
    Peter Pearson
    Jul 13, 2010
  6. Me

    Can't invoke a webservice from WSLD now

    Me, Apr 19, 2004, in forum: ASP .Net Web Services
    Replies:
    1
    Views:
    188
    Jan Tielens
    Apr 19, 2004
  7. Asha
    Replies:
    0
    Views:
    453
  8. jhumanski
    Replies:
    15
    Views:
    868
    Rainer Weikusat
    Apr 24, 2012
Loading...