Windows login - length limit?

bhalpin

Very strange ...

NAV 2009 R2 Build 33597

When any user opens a particular page (Sales Order -> Sales Line > Functions -> Reserve. Then click “Available to Reserve”) they get this error:

The server "net.[url=tcp://companyname:7046/DynamicsNAV/Service]tcp://companyname:7046/DynamicsNAV/Service[/url]" is either unavailable or your connection has been lost.

The Event Viewer shows:

Service: MicrosoftDynamicsNAVServer
User: ABCDEFGHIJKLMNO\abcdef
Type: System.ArgumentOutOfRangeException

One guess was that the Windows login string was 'pretty long' - 22 characters. So we created a Windows user with a one-character name. The error did not occur for that user.

So this raises the question: Is there some limit on the length of the Windows login string (Domain\user) ?

The really disturbing part is that this error only started recently - and the page has worked for several months in testing by the same users. (And the NAV build has remained constant.)

Any clues/comments/suggestions would be greatly appreciated.

postsaurav

Hi bhalpin,

To answer your question -

Is there some limit on the length of the Windows login string (Domain\user) ?

No there is no limit for same.

Possible Reason for error -
The local variable used for storing UserID, during the transaction your are trying to do will be assigned a size of say 20 characters. This local variable is exceeding the limit.

Resolution -
Try running the same process with same user ID on classic and start the debugger. It will tell you the location where the USER ID is getting stored in local variable.

Just increase the size to max. length of your domain user id.

Let me know if you still have any issues.

bhalpin

Thanks.

There are two pages in the mix here that were modified - very slightly. The mod is simply to display a calculated value returned from a function added to the Purchase Line table. The function is extremely simple - and doesn't have anything to do with user IDs. It simply filters and then adds up values from the item ledger entry table.

But, the crash started after doing that mod, so anything is possible.

I've made the same mods to the classic forms and sent that off. We'll see if the same crash (or at least an understandable error) occurs in Classic.

B

PS - I've seen string overflow errors under RTC before - they don't cause an end to the universe like this.