NAV 2013 Debugger Problem

I guess its true, if you look at code in page 9506-Seesion List

CanDebugSelectedSession := NOT DEBUGGER.ISATTACHED AND NOT ISEMPTY;

CanDebugSelectedSession is attached to Enabled property of Debug Selected Session action.

There is no setup kind of thing to enable it..

Lets wait for Microsoft Answer..

Excepti0nal wrote:

Im pretty sure I have read that they only allow one debug session in documentation.

That's true. One NST, one debugger session. If you need concurrent debugging, you have to install additional Services for the database.

Cheers
Carsten

We had experienced the same inconvenience too when we needed to modify some data for a customer but not able to do so because solely changing to partner license in development environment wouldn't work anymore. We gotta write a script and give the permission in the object to do it.

Well, we can live with that since correcting data isn't something customers do too frequently. However, what is really a pain is on user access control. Creating users and assigning permission sets gotta be done in RTC now, and for small customer who only bought a starter pack license of 3 concurrent users and using it to the max, we are not able to administer the user access such as creating user, changing permission or check/kill sessions without asking one of the users to log out so that we can log in. In NAV 2009 and before, we were able to do it in Classic by changing to our partner licence when the customer's license is full.

In addition, to launch the Session window in RTC seem to take up one more user license -- as experienced recently, the small customer with only 3 user license needed us to make some permission change. We asked one of the users to log out so that we could get in. Then they claimed that in fact two users had logged out, which means there should still be one more available session but then the system kept prompting the license was full. Then we wanted to check out the sessions and possibly kill off the one that probably got stuck; but after clicking on the Session menu link, the system prompted that there was no more availale user license, which seems to suggest that launching the Session window is not utilising the same user session that we are already in but requiring one more user license.

Anyway, this can get quite frustrating and take longer than before to perform user access administration.

Mark Brummel wrote:

I'm not sure, but maybe you can only have one debugsession per service tier.

Let me get this to Microsoft and find an answer.

Have you tried more than one service tier?

:idea: Any answer from Microsoft?