Cannot debug call to web service

lvanvugtlvanvugt Posts: 774Member
edited 2018-10-10 in NAV Three Tier
We want to debug an external web service call as the NAV process, that as called via a NAV web service, does not work right. What ever we do, we cannot get the debugger activated. We see data changing in the database, but the debugger is never triggered.

If we trigger the process manually, by either running the codeunit or using the UI, the debugger is triggered. And even if we trigger trigger the web service using SOAP UI, the debugger is also triggered.

BTW: the Event Log is properly logging errors.

We seem to run out of options, but maybe any of you has some useful hint(s). Thanx in advance.
Luc van Vugt, fluxxus.nl
Never stop learning
Van Vugt's dynamiXs
Dutch Dynamics Community

Answers

  • SanderDkSanderDk Posts: 269Member
    I have previous testet NAV webservice throw Webservicestudio, in NAV I added a break point, and set debugger to Debug Next. It trigger my break point at run time.
    What version are you debugging?
    For help, do not use PM, but use forum instead, perhaps other people have the same question, or better answers.
  • lvanvugtlvanvugt Posts: 774Member
    Hi Sander, we have been debugging a lot in that way, but this one seems to "disobey" us ;-)

    Version NAV 2018 (CU6).
    Luc van Vugt, fluxxus.nl
    Never stop learning
    Van Vugt's dynamiXs
    Dutch Dynamics Community
  • frankmortensenfrankmortensen Posts: 37Member
    Do you have multiple service tiers attached to the database?
    If so - then you might be debugging from the wrong service tier.
  • lvanvugtlvanvugt Posts: 774Member
    Do you have multiple service tiers attached to the database?
    Yes
    If so - then you might be debugging from the wrong service tier.
    No.
    Luc van Vugt, fluxxus.nl
    Never stop learning
    Van Vugt's dynamiXs
    Dutch Dynamics Community
  • lvanvugtlvanvugt Posts: 774Member
    OK, solved it. Trusting on my colleague which in hindsight I shouldn't have done. Apparently the two ways were calling two different functions. Breakpoints set on one were not hit by the other.
    Luc van Vugt, fluxxus.nl
    Never stop learning
    Van Vugt's dynamiXs
    Dutch Dynamics Community
Sign In or Register to comment.