I have a situation where the code never shows up in the debugger. The debugger opens but, no code and the Debug menu drop down is grayed out. Only by closing the debugger (many times) can I finally gain control of the system again. I am programming a local db in version 3.7. I have tried 3.6 with the same results. I have unintalled and reinstalled the client. I have also deleted the ZUP file. I am using a Developers License. Help! [xx(]
If your OS Windows XP then disable Network connection called “WAN Network Driver” (installed with AOL…).
I ended up reinstalling the o/s to correct the problem but, I will keep this in mind in the future.
I had the same problem and found it was my Internet Firewall software (Zonealarm) which was causing the problem. I assume it was preventing the Navision Debugger from acting as a server.
Just yesterday, I also experienced this. No code appears in the debugger. Iam using Navision 3.6 and I havent experience this before. I checked all your suggestions but the problem remains. And re-installing my OS is not an option right now since this will take me a long time. Is there any other solution to solve this. Thanks.
Anybody ever manage to resolve this. Same problem here on a client, debug window comes up blank. It runs from the same DB from a different client, so think we can rule out permission problems. This leaves us with client problems and so far I have ruled out: Local Firewall preventing debugger from connecting to client Spyware Anybody else have any ideas? This is driving me mad… Many thanks Meint
Just to add, I have completely removed the client, reinstalled it and still no joy. Deleted Zup file and tried again, also hopeless… Grrr…
From previous comments and experiences, it looks as if it is not exactly Navision’s fault when the debugger ceases to function. The application and the debugger establish a tcp connection between one another and a failure in Windows networking can probably render this communication unusable. I have never had this happening to me, but from what I’ve read, I’d start looking at reinstalling network drivers and associated software. Whatever you try, good luck!
Well, I have tried just about everything else so that may be the way to go. Does anybody have a document that describes how to troubleshoot the debugger or which ports it is listening and communications protocols it is using? As far as I can see there is nothing special about my setup, the only thing is that I am running a local MSDE server for testing stuff and I have a Checkpoint Secure Remote client for VPN connections to the office. No local firewall or ICS running, DHCP issued address, but using 127.0.0.1 to connect the client to the local DB. Oh and there is the VMware networking stuff, but that is all disabled. Blowing Windows away and re-installing will take ages and would rather not do that, anybody have any more ideas? Thanks Meint P.S. one good thing is that I have finally managed to crack 100 posts, having been stuck in the 90’s for ages
Also, does anybody know if you need to have any specific Windows services running to be able to run the debugger? I tend to turn off stuff I think I do not need in order to squeeze that last drop of performance out of a screaming machine. Thanks Meint
I don’t think so because I also disable most services and their mother but my debugger still works as it should. The following services are running on my Windows XP Professional with Service Pack 2: Automatic Updates Bluetooth Support Service Cryptographic Services DCOM Server Process Launcher DHCP Client DNS Client Event Log Network Connections Plug and Play Print Spooler Remote Access Connection Manager Remote Procedure Call (RPC) Security Accounts Manager Telephony Themes Windows Audio Windows Firewall/Internet Connection Sharing (ICS) Windows Image Acquisition (WIA) Windows Management Instrumentation Wireless Zero Configuration WLTRYSVC Workstation
I recently discovered that a piece of software I had installed was disabling Navisions ability to act as a server for the debugger.
quote:
I recently discovered that a piece of software I had installed was disabling Navisions ability to act as a server for the debugger.
Originally posted by wbenefiel - 2004 Nov 15 : 17:20:22
@wbenefiel: Would you mind sharing the name of the software that caused you the problems? [?]
I have been plagued by this exact problem for the last few weeks, and like most of you I tried everything suggested with no luck. But I’ve just fixed it! I have my debugger back! The solution was to delete the demo version of the Amyuni pdf converter, as well as the runtime version shipped with a local direct credit product. I don’t know why it was interfering with the debugger, I’m just very happy to have it back. Say what you like about the debugger but life sure is tough without it! Dan.
Hello, I had the same problem and solved it by uninstalling the Advanced Gateway Client and the Citrix Presentation Server Client Packager - Version 9.0. Then the debugger worked again. Hope my hint helps anyone going nuts on this as I did. Regards Michael Straszniczky
Hi, Interesting that, got the Citrix stuff installed here as well, so will to uninstall that and see how we go. Thanks for your suggestion Meint
I have seen two causes of this one (as mentioned above is Zone Alarm) the second was Cisco VPN client. I to do uninstall it, then get a screw driver and pair of pliers to remove it from the registry, and delete fiels that it put all over the place before I could debug. Other wise it was rotuing certain packets all over the place. PS the cisco thing killed more than just debugger.
I copied the C:\Program Files\Microsoft Business Solutions-Navision\Client to C:\Program Files*Kopie van* Microsoft Business Solutions-Navision\Client When I use this client the debugger works. (It still won’t show me code when I launch the application from the original directory C:\Program Files\Microsoft Business Solutions-Navision\Client) It’s not beautiful but it works for me (Hopefully also for you) Best regaards Joost
Sorry, forgot the report back. Uninstalled Citrix Advanced Gateway client as suggested and it started working again, bizarre… Meint
Hi, i have this problem too. I’m almost sure that this debugger malfunction is a result of updating windows. When I’m using the debugger on earlier XP’s which have not been updated with MS security updates and etc. the debugger is working perfect, but on my PC and many others, which are regularly updated it is not. If someone has thought about that, please reply.