Windows error 15401

Friday, September 20, PM. The login does not exist Verify that the Windows login still exists in the domain. Your network administrator may have removed the Windows login for specific reasons, and you may not be able to grant that login access to the SQL Server. If the login is in a different domain than the SQL Server, verify that the correct trusts exist between the domains. Verify that the domain controller of the login is accessible by using the ping command from the computer that is running SQL Server.

Check both the IP address and the name of the domain controller. Thanks Candy Zhou. Monday, September 23, AM. This will open the Policy Editor. You will see all security policies on right hand side window. Make changes into the following two policies. Domain member: Digitally encrypt secure channel data when possible — Disable this policy Domain member: Digitally sign secure channel data when possible — Disable this policy After making these changes, close the policy editor and reboot the box.

I came across this error, and found that in AD when a new account is created yes I waited 15 minutes for replication there may be times when the name resolves, but you still get this error. So while I was researching the error perhaps another 10 minutes into the search , I tried again and it worked…. So if this case sounds similar to anyone, work with your AD Administrator and check if your replication has gone full circle or give it just a little more time.

He holds a Masters of Science degree and numerous database certifications. Pinal is an experienced and dedicated professional with a deep commitment to flawless customer service. Nupur Dave is a social media enthusiast and an independent consultant. She primarily focuses on the database domain, helping clients build short and long term multi-channel campaigns to drive leads for their sales pipeline.

Is your SQL Server running slow and you want to speed it up without sharing server credentials? In my Comprehensive Database Performance Health Check , we can work together remotely and resolve your biggest performance troublemakers in less than 4 hours. Once you learn my business secrets, you will fix the majority of problems in the future. June 7, Pinal Dave. Leave new Nebu. Hi, I have one suggestion, now that it works for me. Hi Pinal, I got this err when I tried to manually change the Window group name after the physical server got renamed.

Hi Alice, I encountered the same as yours. Best Regards, Charlie. Pinal Dave. Hello Mike, SQL Server introduced encryption methods to encript or decrypt specific data, but incorporating that feature needs changes in data store and fetch procedurs.

Regards, Pinal Dave. Any ideas? Hi PT, This may be a bit late, but hopefully for the benefit of someone who is still experiencing the same problem. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Use BUILTINGroup to grant access to predefined Windows NT groups back to the top Name resolution If you have problems resolving the name of a computer that is involved in adding the login or group, you might receive error Hope this helps.

Andy Ong. Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback?