March 11, 2008 at 1:30 pm
I ran that script and came up with this
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 131
Terminating this procedure. The Login name 'AMEMpusr' is absent or invalid.
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 131
Terminating this procedure. The Login name 'AMEMpusr' is absent or invalid.
But that's not the user am testing. All the logins are transfered but when tried to login with on of them, kicks an error as login failed.
March 11, 2008 at 1:33 pm
Mike Levan (3/11/2008)
I ran that script and came up with thisMsg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 131
Terminating this procedure. The Login name 'AMEMpusr' is absent or invalid.
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 131
Terminating this procedure. The Login name 'AMEMpusr' is absent or invalid.
But that's not the user am testing. All the logins are transfered but when tried to login with on of them, kicks an error as login failed.
Well, that user doesn't appear to have a login on the new server then. Still though, the script would have fixed any orphaned users. The problem you now have is more than likely a password issue.
March 11, 2008 at 1:38 pm
If its a password issue then how cud i resolve it for all the logins in the server, but still i wonder when the same logins are working well in the source server, why doesnt it work in new server.
March 11, 2008 at 1:46 pm
Is it an NT or SQL login?
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply