Problem with debugger

rtomrtom Member Posts: 4
edited 2005-06-01 in Navision Attain
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.

Comments

  • eromeineromein Member Posts: 589
    Maybe you should reinstall all of Navision.

    But are you sure there is something to debug? or maybe there is a error or message in the background?
    "Real programmers don't comment their code.
    If it was hard to write, it should be hard to understand."
  • smagismagi Member Posts: 3
    If your OS Windows XP then disable Network connection called "WAN Network Driver" (installed with AOL...).
  • DoomhammerDoomhammer Member Posts: 211
    you can experience some problems in certain versions of Win98. i.e. on Win98 (first edition) and WinME debugger did not start. If possible, upgrade to Win2000 Professional, this is best system for program developping (not like huge, slow and unstable sh*t named WinXP)
    Martin Bokůvka, AxiomProvis
  • eromeineromein Member Posts: 589
    Doomhammer,

    It really sounds like you know Navision man, but why blow it on sentence like:
    not like huge, slow and unstable sh*t named WinXP

    :wink:

    btw, you should visit more often... don't just hang around on Navision.net, join the good stuff!
    "Real programmers don't comment their code.
    If it was hard to write, it should be hard to understand."
  • eljaffeeljaffe Member Posts: 1
    I have a suspect. First of all initially I am absolutely sure that it did worked, then something happened and I do not know exactly what's that.
    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
  • SHREK31SHREK31 Member Posts: 2
    Hello,

    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. :(
    Skrek
  • DoomhammerDoomhammer Member Posts: 211
    eljaffe wrote:
    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.

    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.
    eljaffe wrote:
    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

    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 :-)
    Martin Bokůvka, AxiomProvis
  • mbsaiimbsaii Member Posts: 2
    Hello,

    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
Sign In or Register to comment.