tag:blogger.com,1999:blog-3633270974235726205.post3273248572338766889..comments2024-03-09T09:56:35.043-05:00Comments on Swarndeep's TECH BLOGS: Windows NT user or group 'Domain\User' not found. Check the name again. (Microsoft SQL Server, Error: 15401)Swarndeep Singhhttp://www.blogger.com/profile/11550593701026635986noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-3633270974235726205.post-24852522146753907462010-10-29T09:08:10.932-04:002010-10-29T09:08:10.932-04:00Thanks a lot, this did solve my problem.
Frank Ki...Thanks a lot, this did solve my problem.<br /><br />Frank KipfmüllerAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3633270974235726205.post-60025555756005136612010-09-01T13:16:56.013-04:002010-09-01T13:16:56.013-04:00It would be Windowss on which SQL Server is instal...It would be Windowss on which SQL Server is installed needs to be rebooted.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3633270974235726205.post-37582617932338610102010-08-30T18:01:23.973-04:002010-08-30T18:01:23.973-04:00When changing these values is it only the Manageme...When changing these values is it only the Management Studio PC that needs a reboot or the Windows server that the SQL Server resides on?The Branded Marquishttps://www.blogger.com/profile/16474863684107311646noreply@blogger.comtag:blogger.com,1999:blog-3633270974235726205.post-26833208196846885682010-08-05T07:19:06.655-04:002010-08-05T07:19:06.655-04:00Hi, I had this issue only with SQL Server Express ...Hi, I had this issue only with SQL Server Express 2005 running on a 64bit Windows 7 development machine.<br />The changes in the article did not fix my problems but as with the above poster, changing the below setting do disabled did:<br />Domain member: Digitally encrypt or sign secure channel data<br /><br />Thanks for the helpSamnoreply@blogger.comtag:blogger.com,1999:blog-3633270974235726205.post-67570566858935372832010-07-03T23:07:48.644-04:002010-07-03T23:07:48.644-04:00I had the same issue in Windows Server 2008 R2 wit...I had the same issue in Windows Server 2008 R2 with SQL 2000 SP4 (32 bits) and SQL 2005 SP3 (64 bits) with a Windows 2000 domain in Mixed mode. I made these 2 changes also disabling: <br />Domain member: Digitally encrypt or sign secure channel data <br /><br />and the problem was solved. Thank you very muchAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3633270974235726205.post-81534830304805099192010-02-10T09:05:59.849-05:002010-02-10T09:05:59.849-05:00I am sorry to know that, if you have not already d...I am sorry to know that, if you have not already downgraded, could you please provide more information about this error. It could be different issue.Swarndeep Singhhttps://www.blogger.com/profile/11550593701026635986noreply@blogger.comtag:blogger.com,1999:blog-3633270974235726205.post-27293627296399823592010-02-09T07:56:03.552-05:002010-02-09T07:56:03.552-05:00I have tried everything possible and even this art...I have tried everything possible and even this article and my problem has not been solved. I do the exact same steps on another Windows Server 2008 with the same SQL Server edition and on the same domain and it works perfectly. There is something about Windows Server 2008 R2 that is causing this problem, and I just can't seem to find it. I'm downgrading to Server 2008Shadyhttps://www.blogger.com/profile/09541446092944101757noreply@blogger.com