web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / NAV debugger crashes o...
Microsoft Dynamics NAV (Archived)

NAV debugger crashes on windows 7

(0) ShareShare
ReportReport
Posted on by M.H.M.M. van den He... 750

Tried to find an answer already on several forums, but still no response.

Problem Description: I'm having a problem while debugging Navision NL5.00 SP1 Build26084 on a Windows 7 Enterprise Laptop. It also happens when i'n using this version but also older versions from within Windows XP mode.
I connect with my client to a SQL server (SQL2005).

The error message is as follows: An error occurred durring connection to the microsoft dynamics debugger and the connection has been lost.
When this happens the debugger jumps to the next breakpoint if there is one, otherwise Navision continues running.
I tried to disable the windows firewall and Forefront. That didn't help.

Thanks for your reply,

*This post is locked for comments

I have the same question (0)
  • Sandra Keys Profile Picture
    Sandra Keys on at

    The issue you are experiencing could be caused by the fact that NAV 5.0SP1 build number 26084 is not supported to run on Windows 7.  If you wish to run NAV 5.0 SP1 on either Windows 7 or Server 2008 R2, you need to install Upate 2.  Update 2 for NAV 5.0 SP1 was released on March 2, 2010. 

    Please use one of the following links to download Update 2 for NAV 5.0 SP1.  Hopefully loading Update 2 will take care of the error you are receiving. This release has now been completed, and is available on PartnerSource:https://mbs.microsoft.com/partnersource/downloads/releases/MicrosoftDynamicsNAV50SP1.htm And CustomerSource:

    https://mbs.microsoft.com/customersource/downloads/servicepacks/MicrosoftDynamicsNAV50SP1.htm

     

    Best Regards,

     

    Sandy  

     

  • M.H.M.M. van den Heijkant Profile Picture
    M.H.M.M. van den He... 750 on at

    Downloaded the full version, and installed the new client. But that didn't help.

    Didn't expect it would help because the same issue exists when this version or older versions are running in Windows XP mode. Only when these versions run from within the Virtual PC, no issue exist. But this is a Windows XP installation, so no problems there. Only extra info I can give now is, by using TCPView, one can see that when the connection is lost between the navision client and the debugger, a new tcp port is chosen, and the connection is restored. But it then jumps to the next breakpoint or if there is no breakpoint, the navision client continues to run.

  • Sandra Keys Profile Picture
    Sandra Keys on at

    Sorry to hear that upgrading to NAV 5.0 SP1 Update 2 executables did not fix the issue.  Since the issue does not occur when the NAV Debugger runs in a Virtual environment, it sounds like something environmental in your machine is causing the issue.  What are the differences in the programs, etc. that are installed on your environment and the Virtual environment?  This could help point you to the cause of the issue.

    Below are the other suggestions I found - some I believe you have already tried:

    1)  NAV debugger uses a TCP port to communicate with NAV. So could it be that there is no port available OR the debugger itself is not allowed through the firewall.  Every time the debugger connects to C/SIDE it uses a different TCP port. It uses
    sockets to talk with Navision.

    The client and the debugger uses the first available port. The Windows Sockets DLL selects a usable port for the debugger , and passes 0 as the port value. A port value greater than 1024 is then chosen. This is done so it is possible to have several
    debugging sessions running at the same time.

    I suggest you check the security settings and temporarily allow everything and test the debugger. If the error goes away, then the problem is in the firewall.

    2)  There was another issue where it was discovered that a Citrix based add-in was interferring with the Debugger.  The partner removed the add-in "Advanced Gateway Client" and the Debugger started working correctly again. So you may want to look for some unusual programs on your machine that could be causing the issue.

    3) Are older versions of NAV installed on this machine?  If so in which order were they installed?  It is suggested to have only the latest version of NAV installed and just copy the files from the older versions to their own folders and not to run the regular installation routine.  You would need to uninstall all older versions of NAV and then install only the latest version that you are working with.  This way all the necessary files should be updated with the latest available ones and should not cause any conflicts.  

    If none of the above helps, then I suggest submitting a support incident to the NAV Support group for further troubleshooting.  Indepth troubleshooting is outside the scope of the Community forum.

    Best Regards,

     Sandy

  • M.H.M.M. van den Heijkant Profile Picture
    M.H.M.M. van den He... 750 on at

    We've found the cause for the issue reported.

    On our HP laptops we've installed about every HP tool available for download.
    Among these tools is "HP ProtectionTool Security manager".
    Included with this software are apshook.dll (Application Protection Hook) and itclient.dll (SSO Hook), both from Bioscript.
    By using an external tool called YAPM (YetAnotherProcessMonitor) we found these dll's were being used by atdebug.exe.
    So when "HP ProtectionTool Security manager" was removed, together with 5 other tools from HP, because of certain dependencies, the dll's were gone.
    Navision Debugger worked stable after the software was removed.
    Navision 4 SP3 to Navision 6.0 SP1 run smoothly in Windows 7, and also older (and new) versions are running without any issues when in Windows XP Mode.
    Mind you, we've tried disabling about all non Microsoft software and services without any result, but we are glad we finally found the culprit.

    To add some extra info. The laptops have Windows Enterprise 64 bit installed. But Navision is a 32 bit application.
    So maybe there is an issue with these dll's together with atdebug.exe in a 64 bit OS. I've noticed there were 64 bit versions of these dll's installed, but of cause not used by atdebug.exe

  • Sandra Keys Profile Picture
    Sandra Keys on at

    Mr. Heijkant,

    Thank you very much for sharing the information regarding the cause of the NAV Debugger in NAV 5.0 SP1 crashing on Windows 7.  This could be very helpful information to others and I do very much appreciate your sharing the information with the NAV family.

     Best Regards and thank you once again.

    Sandy 

     

     

     

     

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans