.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

SQL Server Login - Windows Groups

Posted By:      Posted Date: September 23, 2010    Points: 0   Category :Sql Server
We are trying to standardise access to SQL Server in our oraganisation.

We are installing SQL Server Management Studio locally for all our developers and DBA's.

The DBA login in sql server has been given the 'sysadmin' role. The DBA domain account has been made a member of the following Windows Groups,

- Remote Desktop Users
- Users

Our developers have been given the appropriate database role. Their domain admin account has been made a member of the following Windows Groups,

- Users

Can you advise whether this is a correct setup, if not can you suggest an alternative ?
Do we need to put Developers in the 'Users' group ?


View Complete Post

More Related Resource Links

Login to SQL, using Windows 7, SQL Server Error 18452, "Login failed. The login is from an untrusted

I have a File/Sharing Server which is Server 2008 SP2 and SQL Server 2008 is installed on it. My system which is on the same workgroup, was running Windows 2003 Server, which I have saved Server 2008 login credential on it and used that credential to login to SQL Server on Server 2008 system in Windows Authentication mode using SQL management studio. Recently I installed Windows 7 on that system, and I have also saved that Server 2008 credential in Windows 7 Credential Manager. The problem is here when I want to login in Windows Authentication mode using SQL management studio like past, and I will get below Error: Cannot connect to [SERVER] Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (.Net SqlClient Data Provider) Error Number: 18452 Severity: 14 State: 1 Line Number: 65536 I tried that registry solution (DisableLoopbackCheck=0x01 this thread), but no luck with that. I have checked the outgoing packets when I click on connect, and I found out that SQL management studio tried to send my local windows credential instead of Server 2008 saved credential. I don't want to login in SQL Mode, and also I don't want to convert my server to Domain controller. Is there any other solution with this issue? Regards

Login failed for WINDOWS Administrator login. (Microsoft SQL Server, Error: 18456)

Hi All, I am using SQL server 2008. While adding SQL user i unknowingly deleted the SQL authentication user from SQL server. Now the problem is i can not login with Windows Authentication neither i can login as "sa" user as this user is disabled. Please suggest me how to get in to SQL server management studio. Database is up and running but i can not access the database any more after doing this blunder. Please suggest me how to recover SQL instance, Thank you.

Are nested Windows groups supported as SQL Server 2008 logins?


I am attempting to configure a new SQL Server 2008 instance to use Windows authentication, and am encountering a problem when adding Windows domain groups as logins. Specifically, Windows users who are direct members of a Windows group that has been added as a login behave normally. Users who are members of groups that are, in turn, members of other groups which have been added as logins are unable to connect.

In a simplified example, consider the following:

Group: MYDOMAIN\DataViewers
  Member: MYDOMAIN\Hazel
  Member: MYDOMAIN\Seamus

Group: MYDOMAIN\DataEditors
  Member: MYDOMAIN\Vaughan
  Member: MYDOMAIN\Liesel

Group: MYDOMAIN\AllUsers
  Member: MYDOMAIN\DataViewers <-- This is a group
  Member: MYDOMAIN\DataEditors <-- This is a group

If I add the MYDOMAIN\AllUsers group as a SQL Server login (and map it to some databases), none of the end users (i.e. Hazel, Seamus, Vaughan, Liesel) can connect. If I add the MYDOMAIN\DataViewers or MYDOMAIN\DataEditors groups as logins, though, their members can connect. Similarly, if I add an end user directly to the AllUsers group, they can connect normally.

It appears as if the nested group model I had envisioned is not supported in SQL Server 2008, but I have been unable to find any documents that state this conclusively. Therefore, my q

SQL Server 2005 random login failures for windows forms application


One of our VS .NET 2008 windows forms applications runs from multiple client machines. The application randomly has login failures from random machines and from random places in the code. The login works almost every time but about once every fifteen minutes an error shows up in SQL Server error logs from a random user. We are running a clustered SQL Server 2005 system and the database is in 2005 (90) mode.

The following error appears in the SQL Server error logs:

Login failed for 'App_Login'. [CLIENT: XXX.XXX.X.XXX] Error: 18456, Severity: 14, State: 16.

The following error is what the client sees:

Login is valid, but server access failed. Windows App can't login unless assigned SysAdmin.


I put a similar plea for help in the ADO forum but haven't gotten responses. I have a feeling this is a better place to put this post. If someone thinks it should go elsewhere please let me know.

I've been stuck on this problem for a day and a half. I wrote a windows form application in C# that works flawlessley for myself and the other network admins. As soon as a normal user tries to use it it fails.

Our environment has XP workstations. SQL Server 2005 Enterprise Edition, on Windows 2003 server.

My application makes several connections but I wrote it so that it would test and give give meaningful error mesages every time it tried to connect to SQL server. The very first connection it tries to make fails, which thankfully forces the application to exit before ay other connections are made. This first piece is very simple. It runs a stored procedure that adds the user name and the current time to a table. For normal users, I instantly get the error "Login failed for Domain\User". When I looked at the SQL Server logs, I see [Error :18456, Severity:14, State: 11.] which is telling me that the Login is valid, but server access failed.

We suspected it was a domain rights issue since the network admins can run the aplication successfully, but as it turns out the network admins and developers all have the SQL role "sysadmin". If

Login is valid, but server access failed. Windows App can't login unless assigned SysAdmin.


I'm not sure if this belongs here or in a SQL Server forum.  It's an ADO.NET application though so I'm posting it here first.

Here is our environment.  XP workstations.  SQL Server 2005 Enterprise Edition, on Windows 2003 server.

We are putting together our first C# windows-based SQL application.  We want to install it on 50 to 100 workstations.  The first piece is very simple.  It starts by running a stored procedure which adds the user name and the current time to a table.   

If I put a test user into the SQL Server role [sysadmin] it works flawlessly.  If the user is not assigned that role I get the error "Login failed for Domain\User".  When I looked at the SQL Server logs, I see [Error :18456, Severity:14, State: 11.] which is telling me that the Login is valid, but server access failed.  Obviously, I don't want to give all our users sysadmin rights.


Essentially, we're trying to figure the minimum security settings that will allow our windows users to read, write, and delete from tables in a database, and execute stored procedures.  We thought we understood the security settings but we're missing something.  I don't know how to start with "sysadmin" and remove priveleges one at a time.

Here are a few things w

Not able to login to Sql Server 2005 DataBase Engine on Windows 7


Hi All,

 I installed Sql Server 2005 Enterprise Edition on My Laptop (also on desktop) which is running on Windows 7.I have updated it with SQL Server 2005 SP3. I am still unable to access the Database Engine.

·     I installed the required IIS component before SQL server installation.

·     During installation it didn't asked me about components t

Re-login to SQL Server 2008 in Windows authentication mode after resetting my Windows login password



I recently reset my Windows login password but from then onwards SQL Server 2008 is not allowing me to login in Windows authentication mode.

Can someone please help on where I can go and set my new Windows Login password in SQL Server 2008 and continue to login in Windows authentication mode?

Thank you,

Anish Ravindran

MS SQL Server 2008 sa account locked out and Windows Authentication login is greyed out



The sa account got locked out and even though mixed mode authentication is enabled. When I select "Windows Authentication" the Username and Password fields are greyed out. The username field contains my current windows logon and the password field is blank. I am logged in with a windows administrator account though I hadnt explicitly added this account to the SQL server sysadmin role.

I have also tried "Run as Administrator" with the SQL server management studio but the problem persists

Please note that SQL server was installed with another windows administrator account. Could this be the reason ? Will it work if I login with the account with which SQL server was installed ?

Word Automation Issue in Windows Server 2008 Hosting



The problem I am posting here is that I was facing nearly 2 weeks around. Any body comes with this stuff please help.

Word Automation in sample ASP.NET(C#) application.

I am using Microsoft.Office.Inetrop.Word Assembly for automation. Here I am reading a XXX.dot template file and fill the contents with dynamic data.

When i am executing my code in localhost:someportnumber the automation is working fine and I could get expected result and when I am hosting in my inetmgr(Windows XP is my OS) it is also working fine.

But the problem is that when I am hosting in my production server(Windows Server 2008 Standard Edition) I am not able to perform automation and results in the following error.

Data: System.Collections.ListDictionaryInternal
Message: Word has encountered a problem.
Source: Microsoft Word

The code gets failed in the following line:

ApplicationClass wordApp = new Microsoft.Office.Interop.Word.ApplicationClass();

Document wordDoc = wordApp.Documents.Add(ref oTemplate, ref oFalse, ref oMissing, ref oMissing); // Error in this line

I cannot able to proceed further. Can anybody please help me in solving this issue?

Thank you.

With Regards,


No ASPNET User in Windows Server 2008?


I have been looking everywhere online regarding this, but have not found a clear answer.


I have an ASP.Net app running on Windows Server 2008, it's basically a reporting app using Crystal Reports. I have encountered a roadblock in regards to rendering some pages. When I run the app in Visual Studio(on the same 2008 machine) everything works perfectly. Yet when I publish it and run it live the reports will not display correctly, I get a message saying Failed to render page.


I looked this error up in the Crystal Reports website and the fixes they have there refer to giving the windows "aspnet" user full access rights to certain folders on the machine. I would be happy to do this, however there is no aspnet user in Windows Server 2008.


I installed the server and set its role to be Web Server. I also checked all the options regarding ASP.Net and IIS 6 compatibility. Yet there is no ASPNET username anywhere.


Did I set the server up wrong? or do I have to do something within ASP.Net to  create this user and then give it rights? 

Not working on Windows Server 2008




I had the CSS friendly adapters working great on our old server (windows server 2003 - 32bit) and now we have moved to a 64 bit environment and now I can not get the CSS friendly adapters to work.

We are using SharePoint 2007.

Is there another work thru for 64bit environment.

I notice windows server 2008 has a directory  C:\Windows\Microsoft.NET\Framework64 would I be using the browser file in this directory???

Please help!

{ End Bracket }: Customize Windows Home Server


Chris Gray discusses custom applications he's developed for Windows Home Server and explores applications for energy savings.

Chris Gray

MSDN Magazine July 2008

Desktop Security: Create Custom Login Experiences With Credential Providers For Windows Vista


Why is a change to the Windows logon plug-in interface so exciting? Because with credential providers you can customize the logon experience for your users.

Dan Griffin

MSDN Magazine January 2007

Built For Speed: Develop Turbocharged Apps For Windows Compute Cluster Server


This article explores the services provided by Compute Cluster Server 2003 and the tools provided by Visual Studio 2005 that will help you develop High-Perfomance Computing applications.

Rich Ciapala

MSDN Magazine April 2006

Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs


There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend