Check your hard copy of syslogins and your restored syslogins table. Look especially for the following situations and reissue the appropriate commands, as necessary:
If you have added server logins since the last backup of master, reissue the sp_addlogin commands.
If you have dropped server logins, reissue the sp_droplogin commands.
If you have locked server accounts, reissue the sp_locklogin commands.
Check for other differences caused by the use of sp_modifylogin by users or by System Administrators.
Make sure that the suids assigned to users are correct. Mismatched suid values in databases can lead to permission problems, and users may not be able to access tables or run commands.
An effective technique for checking existing suid values is to perform a union on each sysusers table in your user databases. You can include master in this procedure, if users have permission to use master.
For example:
select suid, name from master..sysusers union select suid, name from sales..sysusers union select suid, name from parts..sysusers union select suid, name from accounting..sysusers
If your resulting list shows skipped suid values in the range where you need to redo the logins, you must add placeholders for the skipped values and then drop them with sp_droplogin or lock them with sp_locklogin.
