cannot connect/login error message

I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection (Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.Get PooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUs erList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Ob ject sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPo stBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEve ntHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCol lection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizW
The ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.

cannot connect/login error message

I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
----
--
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec
tionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePo
stBackEvent(String eventArgument) +57
System.Web.UI.Page. RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.

cannot connect/login error message

I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application
----
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
--
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.

cannot connect to the database using sa or a new login

Hi,
I have problem connecting to any of the databases on the local machine using
the "sa" or any of the logins that I had created and gave database access. I
have SQL Server 2000 Developer Edition installed on XP Professional OS.
I am getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not XXX
ociatied
with a trusted SQL Server connection
I have never seen this error message.
I have the same SQL Server 2000-Developer edition installed on this other XP
Professional system and there is no problem with connecting to any of its
local machine databases.
Please help!
Thank you,
--
MitraThe error indicates you are trying to access the server with
SQL logins but the server is configured for Windows
Authentication only. So try changing the Authentication mode
to SQL Server and Windows.
You can find this by right clicking on the server in
Enterprise Manager, select properties and go to the security
tab.
-Sue
On Wed, 17 Nov 2004 14:48:02 -0800, "mitra"
<mitra@.discussions.microsoft.com> wrote:

>Hi,
>I have problem connecting to any of the databases on the local machine usin
g
>the "sa" or any of the logins that I had created and gave database access.
I
>have SQL Server 2000 Developer Edition installed on XP Professional OS.
>I am getting the following error:
>Java.sql.SQLException: []Login failed for user sa. Reason: Not associ
atied
>with a trusted SQL Server connection
>I have never seen this error message.
>I have the same SQL Server 2000-Developer edition installed on this other X
P
>Professional system and there is no problem with connecting to any of its
>local machine databases.
>Please help!
>Thank you,|||Hi,
You change the authentication process from "Windows only" to "SQL+Windows"
with the following steps :
1- stop MSSQLServer service
2- edit the value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\LoginMode to
assign it the value 2.
3- Restart the service
Note : the value LoginMode can be
1 for Windows authenticaton
2 for Mixed authentication
Rgds,
Chris
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:7A3CF1D3-892B-4054-8B72-FED592BE3FC7@.microsoft.com...
> Hi,
> I have problem connecting to any of the databases on the local machine
using
> the "sa" or any of the logins that I had created and gave database access.
I
> have SQL Server 2000 Developer Edition installed on XP Professional OS.
> I am getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
associatied
> with a trusted SQL Server connection
> I have never seen this error message.
> I have the same SQL Server 2000-Developer edition installed on this other
XP
> Professional system and there is no problem with connecting to any of its
> local machine databases.
> Please help!
> Thank you,
> --
> Mitra

Cannot connect to SQL2005

Hi,

This is the error I am getting - HELP

A connection was successfully established with the server, but an error occured during the login process(provider: TCP Provider - error 0 an existing connection was forcibily closed by the remote host. (Microsoft SQL server error: 10054).

I have checked the error code 10054 - at this link

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303120

it says it applies to SQL2000
Regards
SahilFor a faster response I suggest you post this to the SQL Server Data Access forum.

Dan

Cannot connect to SQL Servrer 2005 remotely using another account than sa

Hi there,
I set up an SQL Server 2005 Enterprise Edition, so it is listening on
the network.
I can login successfully from a remote machine using osql:
osql -H sqlhost -U sa
Password: XXX
1>
However I created another user "test" (SQL Auth.) and also a database
which test should be allowed to access but test cannot login remotely
(test _can_ login locally, for example in the management studio)
osql -H sqlhost -U test -d db_test
Password: XXX
Login failed for user 'test'.
What is strange about it, is that it doesn't even show up in the logs
that it did not work. There is no mention of the user "test" in the
logs when the remote login fails.
Any idea what to check? What am I doing wrong? :-(
Regards,
marcNote that you should use -S server_name\instance_name.
Perhaps you are connecting to a local instance.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Marc" wrote:
> Hi there,
> I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> the network.
> I can login successfully from a remote machine using osql:
> osql -H sqlhost -U sa
> Password: XXX
> 1>
> However I created another user "test" (SQL Auth.) and also a database
> which test should be allowed to access but test cannot login remotely
> (test _can_ login locally, for example in the management studio)
> osql -H sqlhost -U test -d db_test
> Password: XXX
> Login failed for user 'test'.
> What is strange about it, is that it doesn't even show up in the logs
> that it did not work. There is no mention of the user "test" in the
> logs when the remote login fails.
> Any idea what to check? What am I doing wrong? :-(
> Regards,
> marc
>|||When you are using 'osql -H sqlhost -U sa' without -S you are connecting to
the default instance on the local computer. Try it and run this to verify
select @.@.servername
go
Ben Nevarez, MCDBA, OCP
Database Administrator
"Ben Nevarez" wrote:
> Note that you should use -S server_name\instance_name.
> Perhaps you are connecting to a local instance.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Marc" wrote:
> > Hi there,
> > I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> > the network.
> > I can login successfully from a remote machine using osql:
> >
> > osql -H sqlhost -U sa
> > Password: XXX
> > 1>
> >
> > However I created another user "test" (SQL Auth.) and also a database
> > which test should be allowed to access but test cannot login remotely
> > (test _can_ login locally, for example in the management studio)
> >
> > osql -H sqlhost -U test -d db_test
> > Password: XXX
> > Login failed for user 'test'.
> >
> > What is strange about it, is that it doesn't even show up in the logs
> > that it did not work. There is no mention of the user "test" in the
> > logs when the remote login fails.
> >
> > Any idea what to check? What am I doing wrong? :-(
> >
> > Regards,
> > marc
> >
> >|||Yes you are right! Thanks!!

Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)
Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/default...06&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct? If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Hey There,
When I try to connect using the Named Pipes, I have pipes enabled on
both the client and server end, with the server pipe being
"\\.\pipe\sql\query" and trying to keep the client pipe the same as
above. When I try to connect, I get this error:
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not
exist or access denied.
TESTS FAILED!
I have added the user and password that I am logged into now on XP Pro
onto the Windows 2000 Server machine. What do you think I am missing?
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hey There,
I have tried the procedure that was suggested. I have added the user name
and password that I am logged in as on my Windows XP Pro machine to the
Windows 2000 Server machine that has SQL Server 2000 installed on it. I have
also created the same username and password on SQL Server 2000 as a valid
user. I have enabled pipes on the server and client with the server pipe
being the default pipe: "\\.\pipe\sql\query" and I have set the client pipe
to the same value. Now I get this error when I try to do a test connection:
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or
access denied.
TESTS FAILED!
What else could I be missing?
-Jay
(jay@.doityourself.com)
Lou_Arnold@.nospam.com (Lou Arnold) wrote in message news:<40ff4f17.8220370@.nntp.flfrd.phub.net.cable.r ogers.com>...[vbcol=seagreen]
> Kevin,
> Your option 1 below implies that you need Named pipes if you have no
> domain controller and want Windows Authentication mode. Is that
> correct? If so, is this requirement documented somewhere?
> Lou Arnold
> On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
> McDonnell [MSFT]) wrote:
|||Jay...
I can't help you further with your problem, sorry. However at least
you have an error messge. Perhaps Kevin can help.
I am slowly coming to the conclusion that Windows Authentication
doesn't work unless you operate a domain controller. If your situation
permits, you may want to try connecting those two computers into a
network with a domain controller.
My only other suggestion is that you try this same test with the sql
server in mixed or SQL Server mode (the alternatives to Windows
Authentication) and see what happens . I'm not sure how to change the
mode after installation.
Lou.
PS Whatever happens, please let us know. It would be of great value to
me to have the information.
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Lou,
Thanks for the advice. The reason I would really like to use Windows
Authentication is that when I use the SQL Server Authentication, with
some of the machines, it will prompt you to input the password every
single time you select a database table, or click a form button. It
seems that every move that is made requires that SQL needs to have the
password input.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi Patel,
Let's try to get a better error message. Try to make the Named Pipe
connection using a Test ODBC Data Source.
When you create a new ODBC DSN, the wizard will walk you through and
generate a much better error message if it fails.
What we need is the OS Error number.
Example: OS Error 53 == Network name not found
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/defaul...306&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct' If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>

cannot connect to remote SQL server

Hi,

From the SQL Enterprise Manager, i can connect to MS SQL database in server1, but not on Server2. On Server2 its giving Timeout.

When i login into Server2 by Terminal services and open Enterprise Manager, i can connect to the database.

What could be the reason that within the Server2, can connect to the database, but cannot connect from outside the server.

Any ideas?

Thanksany firewalls between the 2 servers ?
both internal ips ?
can you connect server2 to server1 ?|||No there are no firewalls... (i can login through Terminal services)
And i'm connecting from my local PC to either Server through Enterprise manager.

MS SQL Server of Server1 is giving Timeout.
Any network settings in MS SQL server going wrong?|||Originally posted by reliableHost
No there are no firewalls... (i can login through Terminal services)
And i'm connecting from my local PC to either Server through Enterprise manager.

MS SQL Server of Server1 is giving Timeout.
Any network settings in MS SQL server going wrong?

Two options:

1. Add the server using the Client Network Utility under Microsoft SQL Server. Add the servername u want to use, if you have the IP address of the server add it in. Go under alias -> TCP/IP or if the server is local go alias -> Named pipes

2. Also you could try adding the server name and the ipaddress in the hosts file under 'C:\Winnt\system32\drivers\etc\hosts'.
For eg: 1x.xx.x.xx SERVERNAME

just append this to the end of the host file

Hope this helps

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

cannot connect to database: Login failed for user

Hello everyone,

When I try to connect to database I get this error message: Login failed for user 'databaseadmin'.

My connection code is:

Dim MyConnection As New SqlConnection( _
"server=(local); database=news; UID=databaseadmin; PWD=111111;")

I've tried "server=localhost:3066", and "server=." and many many other ways, but it's still not working! I don't know what other things should I try now... I asked the support people of my web host, and their answer is:"Mysql database usename and password is corect one. It seems that there is problem with the script code."

Please would anybody help me with this? Thank you very much!

If you are trying to connect to your web host's database server then the server should be something other than local. Also, you said the support people's answer is "Mysql database ...". You are using SQL Server not MySQL, right?

-Mike

|||Thank you so much for your reply!

Yes it is Microsoft SQL Server I'm using. The web host gave us some choice when adding a new database, and I also added another database which is using MySQL Server, and it didn't work neither...

Sorry I'm new to ASP.net, so I don't know what should I put for "server" if I'm working with the web host's database server? I tried to give it the IP address of my web host, but it didn't work...

Would you please give me some further assistance on the code? Thank you!|||For your information, after I login to phpMyAdmin I get this welcome message:

MySQL 4.1.7 running on localhost:3306 as databaseadmin@.localhost

Don't know whether this helps...
I'll really appreciate if someone could help me with this problem, thank you in advance!!|||Problem solved!

I've added a new MySQL database, and connected to that database using Odbc connection. And it's now working!!

cannot connect to database

i keep getting this error can anyone help me??

Cannot open database requested in login 'Match1'. Login fails. Login failed for user 'DURON\ASPNET'.

i used WINT Integrated security

code as following

Dim MySQL As String = "Insert into UserData ([UserName],[Password]) values (@.user, @.pass)"
Dim myConn As SqlConnection = New SqlConnection("data source=DURON\NETSDK;initial catalog=Match1;integrated security=SSPI;workstation id=DURON;packet size=4096")
Dim Cmd As New SqlCommand(MySQL, myConn)
Cmd.Parameters.Add(New SqlParameter("@.user", tbUser.Text))
Cmd.Parameters.Add(New SqlParameter("@.pass", tbPass1.Text))
myConn.Open()
Cmd.ExecuteNonQuery()You need to make DURON\ASPNET a user in SQL Server. Do you have Enterprise Manager?|||I do. I also have this problem.
settings:
winXP
iis5.1
sql2000 eval
mixed mode