Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

HTTP/1.1 400 Bad Request

(0) ShareShare
ReportReport
Posted on by

Hello All,

I am trying to access NAV webservice using SOUP UI 2.5.1.

I am able to import the WSDL but when trying to hit the request I am getting below error :

HTTP/1.1 400 Bad Request
Content-Length: 0
Server: Microsoft-HTTPAPI/2.0
Date: Wed, 10 Dec 2014 11:08:19 GMT
Connection: close

error log : ERROR:java.lang.Exception: Failed to access [http://www.soapui.org/appindex/soapui_start.php?version=2.5.1]

I have gone through one blog suggesting to hit the request with proxy setting on.

I set the proxy and hit it again but this time I am getting error :

HTTP/1.1 401 Unauthorized
Content-Length: 0
Server: Microsoft-HTTPAPI/2.0
WWW-Authenticate: NTLM
Date: Wed, 10 Dec 2014 11:10:09 GMT
Cache-Control: proxy-revalidate
Connection: close
Proxy-support: Session-based-authentication

Any suggestion or help to resolve this would be appreciated!!

Thanks!!

Pooja

*This post is locked for comments

  • Ignacio Ocampo Profile Picture
    Ignacio Ocampo 15 on at
    RE: HTTP/1.1 400 Bad Request

    Hi Pooja I'm developing a new service to do NTLM authentication https://www.nafiux.com/wasp/ if I can help you please let me know

  • keoma Profile Picture
    keoma 32,675 on at
    RE: HTTP/1.1 400 Bad Request

    it seems that soapui can't work with windows authentication. so contact the soapui forum or use an alternative tool.

  • Suggested answer
    RE: HTTP/1.1 400 Bad Request

    Try setting maxReceivedMessageSize on the server too, e.g. to 4MB:

       <binding name="MyService.MyServiceBinding"

              maxReceivedMessageSize="4194304">

    The main reason the default (65535 I believe) is so low is to reduce the risk of Denial of Service (DoS) attacks. You need to set it bigger than the maximum request size on the server, and the maximum response size on the client. If you're in an Intranet environment, the risk of DoS attacks is probably low, so it's probably safe to use a value much higher than you expect to need.

  • RE: HTTP/1.1 400 Bad Request

    Hello All,

    As you all are suggesting to use NAV credentials but I am using Window Authentication.

    So I guess windows credentials should use to hit the service.

    Please correct me If my understanding is wrong.

    Also ServicesUseNTLMAuthentication  is already true.

    Please advise further.

    Thanks!!

  • Suggested answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: HTTP/1.1 400 Bad Request

    i tested with soapui vs. 5.0.0.

    stopped nav service, just set value ServicesUseNTLMAuthentication in config file customsettings.config (nav service folder) to true. restarted the nav service.

    then created a soap project in that tool with following nav web service url: localhost/.../SystemService

    this url works by default (without publishing any nav object as web service).

    in second page of project wizard set the authentication values (nav credentials, i.e. username, password, domain) and got a ready to use project.

    works also with type generic project.

    ------------------------------------------------

    project properties:

    WSS Time To Live: 100

    WSS Password Type: None

    ------------------------------------------------------

    global settings:

    http: add authentication info to outgoing request

    proxy: no proxy

    wsdl: disable all checkboxes (no caching, ...)

    -----------------------------------------------------

    try also using ip address instead of servername in the url.

  • RE: HTTP/1.1 400 Bad Request

    I use soapUI 4.5.2 and this work with on the Request Properties the Authorisation Type on "Global HTTP Settings" and the Username , Password and Domain with the right values.

    The request begins with:

    <s:Envelope xmlns:s="schemas.xmlsoap.org/.../&quot;><s:Body xmlns:xsi="www.w3.org/.../XMLSchema-instance&quot; xmlns:xsd="www.w3.org/.../XMLSchema&quot;><ProcessRequest xmlns="urn:microsoft-dynamics-schemas/codeunit/Webservice"><request><![CDATA[

    XML-data

    and ends with:

    ]]></request>

    <response>NULL</response></ProcessRequest></s:Body></s:Envelope>

  • keoma Profile Picture
    keoma 32,675 on at
    RE: HTTP/1.1 400 Bad Request

    follow msdn.microsoft.com/.../ms953968.aspx

  • RE: HTTP/1.1 400 Bad Request

    Hi Sandeep,

    Thanks for the link but I am not using JAVA anywhere to hit the request.

    Also I am using IE10 as browser.

    Please let me know any other resolution.

    Regards,

    Pooja

  • Suggested answer
    RE: HTTP/1.1 400 Bad Request

    Hi Pooja,

    Refer below link.

    http://www.mibuso.com/forum/viewtopic.php?f=32&t=57191&view=next

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,409 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans