Home All Groups Group Topic Archive Search About

Help: Login failed for User ???

Author
4 Apr 2006 1:38 PM
Michael
Please Help me. I've got a .Net 2003 program that attaches to a SQL Server
machine and I'm getting the above error when a user tries to log in. The SQL
server is setup to use Windows Auth. and I have added the new user to the
database and have given the user access to the database for the app. But
everytime I try and login using this users ID, I always get the error:
Login failed for user Christian.Gaut
If I login using my userid and password, the program works fine, but if I
login (into windows) as the user and try it again, same thing happens. I
tried putting the userid and password(windows) in the connect string, but
that is not helping either. Now, in the user properties of the database, it
won't allow me to change the password for the user (I guess cause I'm using
Windows Auth). So should I leave the password blank in the connect string?
Any help would be great, thanks again for taking the time to stop by.
Michael

Author
4 Apr 2006 2:30 PM
Michael
Hi Everyone,
After looking back at the message, I thought that the connection string
might be a good thing to add to the list. The connect string is as follows:
"User=Christian.Gaut Password=??? packet size=4096;integrated
security=SSPI;data source=BACKUPSVR\BKUPEXEC;persist security
info=False;initial catalog=NF_Inventory"

Now I've only put the userid and password here for testing only. I can leave
that in, and login into my machine(using my ID) and it will work. Any ideas.
Thanks
Michael


Show quote
"Michael" wrote:

> Please Help me. I've got a .Net 2003 program that attaches to a SQL Server
> machine and I'm getting the above error when a user tries to log in. The SQL
> server is setup to use Windows Auth. and I have added the new user to the
> database and have given the user access to the database for the app. But
> everytime I try and login using this users ID, I always get the error:
> Login failed for user Christian.Gaut
> If I login using my userid and password, the program works fine, but if I
> login (into windows) as the user and try it again, same thing happens. I
> tried putting the userid and password(windows) in the connect string, but
> that is not helping either. Now, in the user properties of the database, it
> won't allow me to change the password for the user (I guess cause I'm using
> Windows Auth). So should I leave the password blank in the connect string?
> Any help would be great, thanks again for taking the time to stop by.
> Michael
>
>
Author
4 Apr 2006 3:35 PM
Jim Hughes
www.connectionstrings.com is your friend.

Since you are using Windows Auth, your connectionstring should look like
this:

"Integrated  Security=SSPI;Data Source=BACKUPSVR\BKUPEXEC;Initial
Catalog=NF_Inventory"

or

"Server=BACKUPSVR\BKUPEXEC;Database=NF_Inventory;Trusted_Connection=True"

Show quote
"Michael" <Mich***@discussions.microsoft.com> wrote in message
news:5F42A0FD-E734-4746-BA87-EC33DC4DD8A0@microsoft.com...
> Hi Everyone,
> After looking back at the message, I thought that the connection string
> might be a good thing to add to the list. The connect string is as
> follows:
> "User=Christian.Gaut Password=??? packet size=4096;integrated
> security=SSPI;data source=BACKUPSVR\BKUPEXEC;persist security
> info=False;initial catalog=NF_Inventory"
>
> Now I've only put the userid and password here for testing only. I can
> leave
> that in, and login into my machine(using my ID) and it will work. Any
> ideas.
> Thanks
> Michael
>
>
> "Michael" wrote:
>
>> Please Help me. I've got a .Net 2003 program that attaches to a SQL
>> Server
>> machine and I'm getting the above error when a user tries to log in. The
>> SQL
>> server is setup to use Windows Auth. and I have added the new user to the
>> database and have given the user access to the database for the app. But
>> everytime I try and login using this users ID, I always get the error:
>> Login failed for user Christian.Gaut
>> If I login using my userid and password, the program works fine, but if I
>> login (into windows) as the user and try it again, same thing happens. I
>> tried putting the userid and password(windows) in the connect string, but
>> that is not helping either. Now, in the user properties of the database,
>> it
>> won't allow me to change the password for the user (I guess cause I'm
>> using
>> Windows Auth). So should I leave the password blank in the connect
>> string?
>> Any help would be great, thanks again for taking the time to stop by.
>> Michael
>>
>>
Author
4 Apr 2006 4:14 PM
Michael
Hi Jim,
I tried using the new version of the connect string and have the same
problem. I'll include more detail here:
Here is some additional info that might help. I have the follwoing setup in
Enterprise Manager.
Server -> Security -> Logins -> General Tab
The name is listed as 'NARCO??????\christian.gaut
The properties for this user are set as:
Windows Authentication
Domain = NARCO??????  (but grayed out)
Security Access = Grant
and the default database is set.
Server Role Tab:
Nothing set here.
Database Access:
Only the database that needs accessing is checked for permission.

Now if I look in the follwoing
Database -> Users   (Users for this database)
The name is christian.gaut and the Login Name value includes the domain and
has Permit access to db.
The properties are set as followed:
Permit in Database Role:
Public, db_owner, db_datareader, db_datawriter are checked.
and for the permissions I set every possible option (Select, insert, update
and delete) for all the tables and SP's.

We are running on a domain. If I'm using Windows Auth, is the Userid and
Password in the connection string even used?

Ok here is what I have so far:
I login Windows(using my UserId and password), Run application, I can get
into the database with any problems.

I Login Windows(Using the Users ID and Password). In otherwords my
client(co-worker, ect). App starts, but as soon as it tries to access the
database I get the following error:
Login failed for user 'NARCO??????\Christian\Gaut'.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Data.SqlClient.SqlException: Login failed for user
'NARCOFREEDOM\christian.gautier'.
   at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction)
   at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection,
ConnectionState& originalState)
   at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
   at NF_Inventory.frmProductStatus.frmProductStatus_Load(Object sender,
EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
removed for readability
**************************

I also wanted to know if any Windows security setting could cause SQL Server
access problems. For example, the user that I'm trying to get access for,
will not have admin rights to his machine, as will most users here. Could one
of these settings be causing problems with SQL Server since I'm using Windows
Auth security in SQL Server. Thanks again.
Michael
P.S. I'm researching now to try and find the answer to my problem, and the
above question came from one of my readings.



Show quote
"Jim Hughes" wrote:

> www.connectionstrings.com is your friend.
>
> Since you are using Windows Auth, your connectionstring should look like
> this:
>
> "Integrated  Security=SSPI;Data Source=BACKUPSVR\BKUPEXEC;Initial
> Catalog=NF_Inventory"
>
> or
>
> "Server=BACKUPSVR\BKUPEXEC;Database=NF_Inventory;Trusted_Connection=True"
>
> "Michael" <Mich***@discussions.microsoft.com> wrote in message
> news:5F42A0FD-E734-4746-BA87-EC33DC4DD8A0@microsoft.com...
> > Hi Everyone,
> > After looking back at the message, I thought that the connection string
> > might be a good thing to add to the list. The connect string is as
> > follows:
> > "User=Christian.Gaut Password=??? packet size=4096;integrated
> > security=SSPI;data source=BACKUPSVR\BKUPEXEC;persist security
> > info=False;initial catalog=NF_Inventory"
> >
> > Now I've only put the userid and password here for testing only. I can
> > leave
> > that in, and login into my machine(using my ID) and it will work. Any
> > ideas.
> > Thanks
> > Michael
> >
> >
> > "Michael" wrote:
> >
> >> Please Help me. I've got a .Net 2003 program that attaches to a SQL
> >> Server
> >> machine and I'm getting the above error when a user tries to log in. The
> >> SQL
> >> server is setup to use Windows Auth. and I have added the new user to the
> >> database and have given the user access to the database for the app. But
> >> everytime I try and login using this users ID, I always get the error:
> >> Login failed for user Christian.Gaut
> >> If I login using my userid and password, the program works fine, but if I
> >> login (into windows) as the user and try it again, same thing happens. I
> >> tried putting the userid and password(windows) in the connect string, but
> >> that is not helping either. Now, in the user properties of the database,
> >> it
> >> won't allow me to change the password for the user (I guess cause I'm
> >> using
> >> Windows Auth). So should I leave the password blank in the connect
> >> string?
> >> Any help would be great, thanks again for taking the time to stop by.
> >> Michael
> >>
> >>
>
>
>
Author
4 Apr 2006 4:34 PM
Jim Hughes
The users desktop permssions are not relevant to their ability to access the
SQL Server. They will not need to be admins on their desktop or the server.

UserID and Passwd are not used in the connection string when
trusted/integrated security is used and should not be present.

You can test database access by creating an empty file with as UDL extension
and then opening it and setting the parameters and using the Test Connection
button.

The SQL Server will need to be a member server of the domain as will the
users workstations.

Internal DNS will need to be properly configured with appropriate records to
access the domain controllers.

Firewall settings on the SQL Server will need to be set to allow access for
Named Pipes.

The SQL Server Network Configuration network utility will need to be set to
allow Network connections via Named Pipes and perhaps TCP/IP.


Show quote
"Michael" <Mich***@discussions.microsoft.com> wrote in message
news:856C5ED8-F4EE-4F45-934D-18752E11A7EE@microsoft.com...
> Hi Jim,
> I tried using the new version of the connect string and have the same
> problem. I'll include more detail here:
> Here is some additional info that might help. I have the follwoing setup
> in
> Enterprise Manager.
> Server -> Security -> Logins -> General Tab
> The name is listed as 'NARCO??????\christian.gaut
> The properties for this user are set as:
> Windows Authentication
> Domain = NARCO??????  (but grayed out)
> Security Access = Grant
> and the default database is set.
> Server Role Tab:
> Nothing set here.
> Database Access:
> Only the database that needs accessing is checked for permission.
>
> Now if I look in the follwoing
> Database -> Users   (Users for this database)
> The name is christian.gaut and the Login Name value includes the domain
> and
> has Permit access to db.
> The properties are set as followed:
> Permit in Database Role:
> Public, db_owner, db_datareader, db_datawriter are checked.
> and for the permissions I set every possible option (Select, insert,
> update
> and delete) for all the tables and SP's.
>
> We are running on a domain. If I'm using Windows Auth, is the Userid and
> Password in the connection string even used?
>
> Ok here is what I have so far:
> I login Windows(using my UserId and password), Run application, I can get
> into the database with any problems.
>
> I Login Windows(Using the Users ID and Password). In otherwords my
> client(co-worker, ect). App starts, but as soon as it tries to access the
> database I get the following error:
> Login failed for user 'NARCO??????\Christian\Gaut'.
> See the end of this message for details on invoking
> just-in-time (JIT) debugging instead of this dialog box.
>
> ************** Exception Text **************
> System.Data.SqlClient.SqlException: Login failed for user
> 'NARCOFREEDOM\christian.gautier'.
>   at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
> isInTransaction)
>   at
> System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString
> options, Boolean& isInTransaction)
>   at System.Data.SqlClient.SqlConnection.Open()
>   at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection,
> ConnectionState& originalState)
>   at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32
> startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
> CommandBehavior behavior)
>   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32
> startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
> CommandBehavior behavior)
>   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
>   at NF_Inventory.frmProductStatus.frmProductStatus_Load(Object sender,
> EventArgs e)
>   at System.Windows.Forms.Form.OnLoad(EventArgs e)
>   at System.Windows.Forms.Form.OnCreateControl()
>   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
>   at System.Windows.Forms.Control.CreateControl()
>   at System.Windows.Forms.Control.WmShowWindow(Message& m)
>   at System.Windows.Forms.Control.WndProc(Message& m)
>   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
>   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
>   at System.Windows.Forms.Form.WmShowWindow(Message& m)
>   at System.Windows.Forms.Form.WndProc(Message& m)
>   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
>   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
>   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>
>
> ************** Loaded Assemblies **************
> removed for readability
> **************************
>
> I also wanted to know if any Windows security setting could cause SQL
> Server
> access problems. For example, the user that I'm trying to get access for,
> will not have admin rights to his machine, as will most users here. Could
> one
> of these settings be causing problems with SQL Server since I'm using
> Windows
> Auth security in SQL Server. Thanks again.
> Michael
> P.S. I'm researching now to try and find the answer to my problem, and the
> above question came from one of my readings.
>
>
>
> "Jim Hughes" wrote:
>
>> www.connectionstrings.com is your friend.
>>
>> Since you are using Windows Auth, your connectionstring should look like
>> this:
>>
>> "Integrated  Security=SSPI;Data Source=BACKUPSVR\BKUPEXEC;Initial
>> Catalog=NF_Inventory"
>>
>> or
>>
>> "Server=BACKUPSVR\BKUPEXEC;Database=NF_Inventory;Trusted_Connection=True"
>>
>> "Michael" <Mich***@discussions.microsoft.com> wrote in message
>> news:5F42A0FD-E734-4746-BA87-EC33DC4DD8A0@microsoft.com...
>> > Hi Everyone,
>> > After looking back at the message, I thought that the connection string
>> > might be a good thing to add to the list. The connect string is as
>> > follows:
>> > "User=Christian.Gaut Password=??? packet size=4096;integrated
>> > security=SSPI;data source=BACKUPSVR\BKUPEXEC;persist security
>> > info=False;initial catalog=NF_Inventory"
>> >
>> > Now I've only put the userid and password here for testing only. I can
>> > leave
>> > that in, and login into my machine(using my ID) and it will work. Any
>> > ideas.
>> > Thanks
>> > Michael
>> >
>> >
>> > "Michael" wrote:
>> >
>> >> Please Help me. I've got a .Net 2003 program that attaches to a SQL
>> >> Server
>> >> machine and I'm getting the above error when a user tries to log in.
>> >> The
>> >> SQL
>> >> server is setup to use Windows Auth. and I have added the new user to
>> >> the
>> >> database and have given the user access to the database for the app.
>> >> But
>> >> everytime I try and login using this users ID, I always get the error:
>> >> Login failed for user Christian.Gaut
>> >> If I login using my userid and password, the program works fine, but
>> >> if I
>> >> login (into windows) as the user and try it again, same thing happens.
>> >> I
>> >> tried putting the userid and password(windows) in the connect string,
>> >> but
>> >> that is not helping either. Now, in the user properties of the
>> >> database,
>> >> it
>> >> won't allow me to change the password for the user (I guess cause I'm
>> >> using
>> >> Windows Auth). So should I leave the password blank in the connect
>> >> string?
>> >> Any help would be great, thanks again for taking the time to stop by.
>> >> Michael
>> >>
>> >>
>>
>>
>>
Author
5 Apr 2006 1:27 PM
Michael
I just wanted to let you all know that I found the problem. It was a connect
string, but it was hidden in a few SQLConnection objects that where used on
several screens. It now works as expected. Thanks again for all the help.
Michael


Show quote
"Michael" wrote:

> Please Help me. I've got a .Net 2003 program that attaches to a SQL Server
> machine and I'm getting the above error when a user tries to log in. The SQL
> server is setup to use Windows Auth. and I have added the new user to the
> database and have given the user access to the database for the app. But
> everytime I try and login using this users ID, I always get the error:
> Login failed for user Christian.Gaut
> If I login using my userid and password, the program works fine, but if I
> login (into windows) as the user and try it again, same thing happens. I
> tried putting the userid and password(windows) in the connect string, but
> that is not helping either. Now, in the user properties of the database, it
> won't allow me to change the password for the user (I guess cause I'm using
> Windows Auth). So should I leave the password blank in the connect string?
> Any help would be great, thanks again for taking the time to stop by.
> Michael
>
>
Author
5 Apr 2006 3:27 PM
Jim Hughes
Glad to hear it!

Show quote
"Michael" <Mich***@discussions.microsoft.com> wrote in message
news:33FF6156-E393-4CE8-978B-2F63A5E28124@microsoft.com...
>I just wanted to let you all know that I found the problem. It was a
>connect
> string, but it was hidden in a few SQLConnection objects that where used
> on
> several screens. It now works as expected. Thanks again for all the help.
> Michael
>
>
> "Michael" wrote:
>
>> Please Help me. I've got a .Net 2003 program that attaches to a SQL
>> Server
>> machine and I'm getting the above error when a user tries to log in. The
>> SQL
>> server is setup to use Windows Auth. and I have added the new user to the
>> database and have given the user access to the database for the app. But
>> everytime I try and login using this users ID, I always get the error:
>> Login failed for user Christian.Gaut
>> If I login using my userid and password, the program works fine, but if I
>> login (into windows) as the user and try it again, same thing happens. I
>> tried putting the userid and password(windows) in the connect string, but
>> that is not helping either. Now, in the user properties of the database,
>> it
>> won't allow me to change the password for the user (I guess cause I'm
>> using
>> Windows Auth). So should I leave the password blank in the connect
>> string?
>> Any help would be great, thanks again for taking the time to stop by.
>> Michael
>>
>>

AddThis Social Bookmark Button