Hi,
I have a problem with Debugger in Navision Attain 3.60 - it simply doesn't work. I opens a empty window, and all the debugging options are grayed. I tried to remove it and then ran the reinstall, but no change.
If anyone knows how to solve this, pls. let me know.
Thanx.
0
Comments
But are you sure there is something to debug? or maybe there is a error or message in the background?
If it was hard to write, it should be hard to understand."
It really sounds like you know Navision man, but why blow it on sentence like:
btw, you should visit more often... don't just hang around on Navision.net, join the good stuff!
If it was hard to write, it should be hard to understand."
But, maybe that I have installed and uninstalled 3.70 just to take a look at it? It means that after that the 3.60 debugger fails to work.
I have no "WAN Network Driver" connection to remove as Smagi suggested and I do not believe XP Pro is less than W2000 for developer, at all (sorry, Doomhammer).
I have asked local MBS support, waiting them to solve. We'll see what it come from it.
I will keep you informed, so do you, please!
El Jaffe
I've the same problem with a new server (Windows Server 2003). This problem occurs only if we execute the debugger from the the server (not from a client)
The response of the international support :
"I can not reproduce this problem. This is only a guess - the debug.exe and fin.exe communicates using winsockets and if the windows 2003 server is set to not allow this. You might run into these problems. "
I didn't solve my problem.
If you un-installed Navision v. 3.70 an you did not re-install Navision v. 3.60, then it is possible that Navision 3.70 un-installation procedure removed registry entried used for Navision debugger startup. Try to reinstall Navision 3.60 or install back 3.70. This SHOULD solve your problem. I had similar problem with 3.60 and 3.70.
At home I am running Win2000 server on 1GHz machine (Duron) and at my job, I use WinXP Pro on Celeron 2 GHz. And my home computer is a bit faster than my job computer. And I am not alone, who has performance and other problems with WinXP so I think, Win2K is better as WinXP. But it is only my private opinion...
p.s.: sorry for word SH** used in my previous post, simply I do not like WinXP :-)
there is another thread in the forum dealing with the same problem.
I posted my solution on this problem there, just have a look at
http://www.mibuso.com/forum/viewtopic.php?t=4183&highlight=problem+debugger