Connecting to NAV Web Services from Windows Mobile 6.5

It is kind of embarrassing that I write a post about how to connect to NAV Web Services from Windows Mobile 6, when Windows Mobile 6.5 has been out for almost half a year (that’s how much a gadget person I am:-))

I just downloaded the 6.5 SDK from here and tried out the exact same application as I wrote for Windows Mobile 6 in this post and everything seems to work just fine, so please follow the steps in this post to see how to connect from Windows Mobile 6.5 to NAV Web Services.


Is it faster?

My tests on 6.5 is only on the emulator – but as far as I can see, it is definitely faster. The 1.5 second from Windows Mobile 6 is now down to 0.9 second and 0.8 second with PreAuthenticate set to true.

I will still do some more investigations on performance from Windows Mobile Web Services.


Freddy Kristiansen
PM Architect
Microsoft Dynamics NAV

Comments (4)

  1. Hi Freddy,

    HAve you found any more info on this, we are also having issue with speed with a mobil app we have written for NAV.


  2. primeap says:


    we have a BIG Problem!

    The Setup

    Three Tiers on three Machines. That means, that SQL Server is on different Machine than Service Tier.

    Delegation is Set up und running. That's allright.

    A .NET Mobile Client that consumes the service.

    The Error

    Say, you have a Codeunit with a Function that you publish as Webservice (registerInvoice) ok?

    Somewhere in the navision code you have an ERROR("The Code yx is missing"). ok?

    In this case a SoapException in the mobile client is thrown.

    Good, until now we had no problem with connecting to service and sql server and do some other

    consumation of nav services..

    As soon as there is a soap exception (as a result of the errormessage in the nav code), the connection to sql server is not working anymore!!


    The only thing that brings the client to connect again to sql server. is to run the url ex.( … 20(Schweiz)%20AG/Codeunit/MobileDatenerfassung)of the webservice

    in the browser. After that it works again?!!?

  3. drofla says:

    @primeap I've had this issue, but only when trying to consume NAV web services from outside the LAN (Well, I supposed you could have messed up the 3-tier configuration too I've made that mistake more times than I care to mention) By and large _our_ Windows Mobile devices are used for warehousing functions so it isn't usually a problem – you may need to create a proxy, you'll find freddy has blogged about this in the past if you search for it.

  4. rifmetroid says:


    Did you get a solution for this problem except to write a proxy? We are struggling with the same problem here. Only from the Mobile Device you can't connect after an nav-error or a restart of the webservices. If we connect with the same code from another pc, then it works again… This is really disappointing.

Skip to main content