May 9, 2022 at 5:53 pm
We have a SQL job that we run to copy all logins from the Primary node to all (3) Secondary nodes. For this one particular cluster, we can copy the logins to 2 of the secondary nodes, but not to one of them.
I tried adding a new user to Primary and when I ran the job on each secondary node, it gets copied to two of them, but not to one.
What could be the issue with this one particular server that would prevent me from copying a login?
I did check the SID and it is not in use on this server.
Also, the job runs with no errors, it just doesn't copy the login.
Thanks,
May 9, 2022 at 6:04 pm
I posted to the wrong thread... post removed. Apologies.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2022 at 6:26 pm
I think you replied to the wrong post.
May 10, 2022 at 1:22 am
You're correct... and I wondered where the heck that reply went. 😛
I can't delete the post but I can change it to nothing. My apologies for the distraction and apologies for not having an answer to your question.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2022 at 1:51 am
It’s going to be a network issue. The server in question isn’t able to resolve the login credentials from active directory.
If you want to verify, script the login from one of the good instances and execute it on the odd-ball and read the error.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply