March 11, 2016 at 6:16 am
Honestly, the only time I've ever seen the error is if:
1) The login doesn't exist on the server
2) The login exists on the server but doesn't have database level permissions
3) The login exists on the server, isn't user mapped, but has an orphaned database level login
4) The login is misspelled
I've done it myself many times, mixed around two letters and it looks correct no matter how many times I look at it. In this instance there are two things you can do.
1) Get a peer at the office to look at it and point out the thing you can't see (because "SomeLogin" doesn't help us identify a spelling error and we can't see your server).
2) Use copy-n-paste to make sure absolutely positively that the linked server and the login on the server are spelled exactly the same.
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply