SQLKnowItAll (3/22/2013)
ScottPletcher (3/22/2013)
IF you can very briefly drop the problem login(s) on your clients' machines, and immediately recreate them, you can fix this problem once and for all! Then you would avoid the on-going headaches from this.If you want more details, just let me know.
I don't understand how dropping the logins and recreating them on a separate instance will guarantee the same sid as the login at the provider's machine. Plus, then you leave orphaned database users on the client's machine.
You don't sync the SQL login SIDs on your development, QA and prod machines? Ouch; that must be a royal pita as you restore from one to another.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.