Problem in window login

hemantOne

Hello Experts,

I have facing a problem in window login.I made a new user in server active directory.
I Synchronized this User In NAV with logins but unable to make login.Please tell me what may be the problem.
what tables are affected with user logins.


Thanks .

kriki

What error do you have?

PS if you use the standard security model, you don't need to synchronize anymore.

hemantOne

I made the user in User set up list .But error still come.
The error is
"User set up user ID does not exist"

kine

This means that there is some modifications which force you to add the user into User Setup table (Administration-Application Setup-Users-User Setup).

hemantOne

Thanks kine,

Actually I modify the username in user setup forcefully and make that user in active directory .After Synchronization the logins,there is a refrence problem of SID .can u tell me the right way to do this..

Thanks in advance...

jannestig

Have you added the user to SQL server logins as well ?

I generally add them in SQL first then add them in NAV

kine

forcefully ??? What does it mean?

You need to add the user between users in standard way, than add new line into user setup, lookup the user from lookup table...

For me it seems that you made some mess through code or directly through SQL and now you are solving the result...

hemantOne

Thanks kine,

you are right .I wanted to change the user name .So i modified it.
I think the proper way is to delete old user and create new user.Is any other way to do this?


Thanks.

kine

If the user is windows user, you need to "rename" it in Active Directory. If it is B User, it is better to let the "old account" there, just add the valid till date, and create new account and add it into NAV. But it depends, is the account still "same person, with different name", or it is really different user?

hemantOne

But it depends, is the account still "same person, with different name", or it is really different user

Thanks kine for your help.

In my case "same user with different name".But finally the issue is resolved .Actually we found that the problem related to NAS login.