'Combination of user ID and password entered is invalid' after ADMT account migration

I migrated a user account to a new domain using ADMT and was hoping the SIDHistory would still allow the user to access Navision with the new domain account. They can’t. I get the error: "The combination of user ID and password entered is invalid. Try again.

Is there any particular issue with using SIDHistory for authentication? The user can access other old-domain resources, so SID filtering is not the issue.

Any help would be greatly appreciated.

What version of Navision are you using?

have you synchronize it in navision?


We’re having a similiar problem.

A user’s windows account has been migrated to a new domain.

The old user within Navision was deleted and the the new one inserted.

The user gets the "‘Combination of user ID and password entered is invalid’ message, but both the Nav Window’s login and related SQL Login settings look to be “normal”.

Other users migrated work fine.

Any ideas of what might be the cause?


Sorry, forgot to add that we’re running v3.60b of Navision on SQL2000.

It appears our problem could be related to the xp_ndo_enumusersids stored procedure.

Running this in Query analyser returns the users SID code and any associated windows groups that they belong to. The results look to be stored to a temp $ndo$groups table.

Running it for the problem user returns ;

Msg 50500, level 1, State 50500 Internal Error : a Win32 function returned error code 122 (0x7a) … even if they are given full SQL rights.

Anyone got any ideas?

Our tech guy solved our issue. [:D]

There appears to be a limit to the number of Windows/AD groups that the xp_ndo_enumusersids stored procedure can cope with - around 447!
Because we are migrating users, to a new domain, there is a cross over period where the number of groups a user has is duplicated…hence it took us above this limit. A bug perhaps?

Either way, the solution was simply to reduce the number of groups that the user belonged to.



Looks strange, of course - why should there be such a limit… But user, belonging to more than 200 (you wrote thet 400+ is temporarily doubled count) groups is a little bit unusual, too - that might be the reason why nobody has had the same problem as you and there weren’t any answers to you.

Anyway - nice that you not only found solution yourself, but shared it here, too !