Login failed for user NT AUTHORITY\NETWORK SERVICE

Hi,

We have just purchased a new server running Windows Server 2003 Standard and I am trying to run an ASP.NET 1.1 application but I keep getting the following error message when the application tries to connect to the SQL Server:

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

After reading numerous posts and responses in the forums I have still been unable to overcome this problem.

I have added the IIS_WPG group as a user in the SQL Server Enterprise Manager which NT AUTHORITY\NETWORK SERVICE is a member of but it still doesn't work.

Some of the other suggestions in the forum included not using a trusted connection and changing the Application Pool Identity in IIS from Network Service to Local System. However both of these options have security implications.

I am using
Windows Server 2003 Standard
- The only roles installed File Server, Application Server (IIS & ASP.NET) and DNS Server
SQL Server 2000
ASP.NET 1.1

Any help would be appreciated,

Thanks,

Peter.Hi,

Your are not alone....

I have similar problem, at least same login fail, problem,
(Login failed for user 'NT AUTHORITY\NETWORK SERVICE').

I´ll guess my second problem below will disappear if I solve this above?
Any help would be appreciated.

I have created an SQL instance DotNetNuke with MSDE(desktop engine)
1) How shall I do to create the tables ?
2) How shall I do to create a userid + password ? ( OSQL )
(work around, for problem one??, maybe)

I do not have Enterprise manager.

Thanks
Johan from Svedala..|||I have solved the problem,

When I installed SQL Server I selected to start and run the SQL Server using a Domain Administrator Account.

Changing this to the System Account solved the problem.

This is achieved by doing the following:

1. Expand a server group.
2. Right-click the server, and then clickProperties.
3. On theSecurity tab, underStartup service account, clickSystem account.

Peter.

Login failed for user MCTSERVER01\ASPNET.

Hi,

Hope someone can help me to solve the error message.

I am using Visual Studio 2005 and MS SQL Server 2005. When I tried to run the aspx, I encountered the error listed below.

Server Error in '/webtime' Application.
------------------------

Login failed for user 'MCTSERVER01\ASPNET'.
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 'MCTSERVER01\ASPNET'.

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 (0x80131904): Login failed for user 'MCTSERVER01\ASPNET'.]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734947
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, ...

Siew Hin

As the error message states, looks like the user does not have enough permissions. Check under the Database -> Security -> Logins and see what permissions the user has.sql

Login failed for user '(null)'. Reason: Not associated with a trus

I am new to SQL Server Reporting Services 2005 and have created a new very
simple report. When I run the report directly on the report server it works
fine. If I try and run the report from my laptop I get the error
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I have set up the data source to use a trusted connection and my id has full
rights on the the database where the data resides. The Report server is
hosted on a SQL Server 2005 database and the data in the report is on a SQL
2000 named instance.
I am probably missing something in the setup, but don't know what. Any help
from anyone would be appreciated.does your SQL Server is on another server than the RS server himself?
(have you 2 servers: 1 with RS + IIS and the second with SQL Server himself)
If yes, then you suffer a Kerberos issue.
you have to setup Kerberos to allow your IIS Server to delegate the user.
Read this article:
http://support.microsoft.com/kb/215383/en-us
"gert" <gert@.discussions.microsoft.com> wrote in message
news:E981B1AB-6D2A-4751-8C0D-140B033CA1FA@.microsoft.com...
>I am new to SQL Server Reporting Services 2005 and have created a new very
> simple report. When I run the report directly on the report server it
> works
> fine. If I try and run the report from my laptop I get the error
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> I have set up the data source to use a trusted connection and my id has
> full
> rights on the the database where the data resides. The Report server is
> hosted on a SQL Server 2005 database and the data in the report is on a
> SQL
> 2000 named instance.
> I am probably missing something in the setup, but don't know what. Any
> help
> from anyone would be appreciated.

Login failed for user '(null)'

Using RS2005 and SS2005. I am able to connect through a browser to
server/reports and run a report. However, another person is not able to run
the report. She gets the error: Cannot create a connection to data source
'dataSource1'. Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
She is an administrator both of the network and of the database where the
data is. I also made her a sysadmin of the database where reporting services
is located but that didn't make any difference.
I originally was getting the same error until I made the server a trusted
computer for delegation. That solved the problem for me but not for her.
Any ideas? Thanks,
--
Dan D.I figured it out. I was taking off the 'anonymous access' from the reports
and reportserver web sites but I needed to remove it from the 'default web
site'. Doing that made everything work.
--
Dan D.
"Dan D." wrote:
> Using RS2005 and SS2005. I am able to connect through a browser to
> server/reports and run a report. However, another person is not able to run
> the report. She gets the error: Cannot create a connection to data source
> 'dataSource1'. Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> She is an administrator both of the network and of the database where the
> data is. I also made her a sysadmin of the database where reporting services
> is located but that didn't make any difference.
> I originally was getting the same error until I made the server a trusted
> computer for delegation. That solved the problem for me but not for her.
> Any ideas? Thanks,
>
> --
> Dan D.sql

Login failed for user

Application works fine when run on local computer, but when accessed from another computer or after moving to hosted server, I get the 'Login failed for user SERVERNAME\iusr_servername' error. The application is attempting to access SQL Server 2000 database with hard coded user name and password. I've read about how to do this and it works fine locally, but I don't see what I am missing. Help!See the steps I listed inthis post to solve your problem.
|||Thanks for your response. This helps a bit, but not completly. After adding the IUSR account and granting access to the database, I was able to connect properly from my test computer to my developement computer that is running the app and the SQL Server after removing all authenticated access in IIS. Unfortunately, I don't have that degree of access on the hosted SQL Server. I thought that the connection string was used to gain access to the SQL Server, and don't understand why the IUSR account needs to have access as well.|||

It is because I bet you in your connection string, you are using trusted connections. On the production box, what you will have to do is either ask your hoster to grant access to that database. The best secure way is to create a whole new windows user account for you and set the IIS application to run under your user. That user is also given grant access to that database.

However, the likelihood of that happening sounds low. Why don't you specify a SQL user name and password (without the trusted connection)?

|||Thank you! I knew that the answer had to be something simple that I was missing. Nothing like being a rooky. Removing the Trusted Connection did the trick.

login failed for user

I have XP Pro installed with SQl Server 7.0. I use Visual
Studio.NET for programming ASP.NET(IIS is also
installed).When I run this, I get an error message

"login failed for user VENKY/ASPNET".

I did some search and many poeple seem to have these
errors but not one page says what is to be clearly done
for XP platform. One page said that I have to create a
domain user ASPNET and see to that this user has access
rights to SQL Server. COuld someone please tell the steps
to do this. Thanks a lot in advance.

Gayathri
.Is your sql server and iis running on the same machine ? What is your anonymous login set to under iis ?|||Originally posted by rnealejr
Is your sql server and iis running on the same machine ? What is your anonymous login set to under iis ?

Yes they are running on the same machine. Sorry what do you mean by anonymous login, where do you go and see that. Anyway yesterday we solved the problem somehow, did further research on the web and somehow solved it.

Thanks,

Gayathri|||To check the anonymous account used in iis - go into internet service manager. Right click on 'default web site'. Click on 'directory security' -> click edit under 'anonymous access ...) -> click edit under 'anonymous access'.

The solution may have been adding that username to sql server or the anonymous access login to sql server.

For future reference - the following is a helpful article from ms:

article (http://support.microsoft.com/default.aspx?scid=kb;EN-US;247931)sql

Login Failed - XP Home Edtion accessing SQL Server

Hi All.
I have an application (VB 6) that access a database in a SQL Server.
But, I cant access the database when I try to run the application using
XP Home Edtion, even logging in domain (by "map network drives).
I can access the shares in SQL server normally, but when I run the
application appears the error window attached.
Any idea?
Tks in advance
Dan Pinhiero
Rio de Janeiro - Brasil
You might try the connection string below ('User Id' omitted):
"Provider=SQLOLEDB;Data Source=SERV_MT207\DROGASM1;Initial
Catalog=master;Integrated Security=SSPI;Application
Name=CallCenter;Pooling=True"
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan Pinheiro" <dan_pinheirorj@.hotmail.com> wrote in message
news:uqOKXEWHEHA.3820@.tk2msftngp13.phx.gbl...
> Hi All.
> I have an application (VB 6) that access a database in a SQL Server.
> But, I cant access the database when I try to run the application using
> XP Home Edtion, even logging in domain (by "map network drives).
> I can access the shares in SQL server normally, but when I run the
> application appears the error window attached.
> Any idea?
> Tks in advance
> Dan Pinhiero
> Rio de Janeiro - Brasil
>

|||Dan Guzman escreveu:

> You might try the connection string below ('User Id' omitted):
> "Provider=SQLOLEDB;Data Source=SERV_MT207\DROGASM1;Initial
> Catalog=master;Integrated Security=SSPI;Application
> Name=CallCenter;Pooling=True"
>
Hi Dan, thanks for your help, but the application needs the "user id",
due permissions settings. Is there some way to bypass this problem
changing the role/security settings?
Best Regards
Dan Pinheiro
Rio de Janeiro - Brasil.
|||If you want to connect using standard SQL Security, you can specify both
UserId and Password in the connection string and omit the Integrated
Security keyword. Your server will need to be configured to allow both
Windows and SQL authentication.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan Pinheiro" <dan_pinheirorj@.hotmail.com> wrote in message
news:exOROLXHEHA.3144@.TK2MSFTNGP10.phx.gbl...
> Dan Guzman escreveu:
>
> Hi Dan, thanks for your help, but the application needs the "user id",
> due permissions settings. Is there some way to bypass this problem
> changing the role/security settings?
> Best Regards
> Dan Pinheiro
> Rio de Janeiro - Brasil.
>

Login Failed - XP Home Edtion accessing SQL Server

Hi All.
I have an application (VB 6) that access a database in a SQL Server.
But, I cant access the database when I try to run the application using
XP Home Edtion, even logging in domain (by "map network drives).
I can access the shares in SQL server normally, but when I run the
application appears the error window attached.
Any idea?
Tks in advance
Dan Pinhiero
Rio de Janeiro - BrasilYou might try the connection string below ('User Id' omitted):
"Provider=SQLOLEDB;Data Source=SERV_MT207\DROGASM1;Initial
Catalog=master;Integrated Security=SSPI;Application
Name=CallCenter;Pooling=True"
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan Pinheiro" <dan_pinheirorj@.hotmail.com> wrote in message
news:uqOKXEWHEHA.3820@.tk2msftngp13.phx.gbl...
> Hi All.
> I have an application (VB 6) that access a database in a SQL Server.
> But, I cant access the database when I try to run the application using
> XP Home Edtion, even logging in domain (by "map network drives).
> I can access the shares in SQL server normally, but when I run the
> application appears the error window attached.
> Any idea?
> Tks in advance
> Dan Pinhiero
> Rio de Janeiro - Brasil
>
----
--|||Dan Guzman escreveu:

> You might try the connection string below ('User Id' omitted):
> "Provider=SQLOLEDB;Data Source=SERV_MT207\DROGASM1;Initial
> Catalog=master;Integrated Security=SSPI;Application
> Name=CallCenter;Pooling=True"
>
Hi Dan, thanks for your help, but the application needs the "user id",
due permissions settings. Is there some way to bypass this problem
changing the role/security settings?
Best Regards
Dan Pinheiro
Rio de Janeiro - Brasil.|||If you want to connect using standard SQL Security, you can specify both
UserId and Password in the connection string and omit the Integrated
Security keyword. Your server will need to be configured to allow both
Windows and SQL authentication.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan Pinheiro" <dan_pinheirorj@.hotmail.com> wrote in message
news:exOROLXHEHA.3144@.TK2MSFTNGP10.phx.gbl...
> Dan Guzman escreveu:
>
> Hi Dan, thanks for your help, but the application needs the "user id",
> due permissions settings. Is there some way to bypass this problem
> changing the role/security settings?
> Best Regards
> Dan Pinheiro
> Rio de Janeiro - Brasil.
>

Login Failed - Accessing through XP Home Edition

Hi All.
I have an application (VB 6) that access a database in a SQL Server.
But, I cant access the database when I try to run the application using
XP Home Edtion, even logging in domain (by "map network drives).
I can access the shares in SQL server normally, but when I run the
application appears the error window attached.
Any idea?
Tks in advance
Dan Pinhiero
Rio de Janeiro - Brasil
The null in "login failed for user null" indicates that the domain
controller didn't send a valid, authenticated windows login to SQL Server.
There may be a problem with the DC (out of date, permissions, etc.) or with
something on the network. From the XP workstation you need to see if you
can get to other network resources on the domain without having to enter
credentials and fix it if you can't. You can also see what logonserver (DC)
that workstation is pointed to (run SET from a cmd prompt) and see if you
can point it to a different DC.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Login failed

Hi,

I can connect to the SQL server installed in another machine in our network. But when I run the web form I'm having this error.

Login failed for user ''. The user is not associated with a trusted SQL Server connection.

Pls help me

your sql server to need to setup account for this paticular machine to access.|||

Hi lakmalvbj,

From your description, I understand you can use SQL client tool to connect the remote SQL Server by window authentication, but Web Form fail. If I have misunderstood your concern, please feel free to let me know.

The error message isLogin failed for user ''. The user is not associated with a trusted SQL Server connection.

I find the user name is null. Is it the intact error message?

If the error message is intact. For the user who login fail is null, I believe you were using Impersonation in web.config with simply section:

<identityimpersonate="true" />

When a client view the page with Windows Authentication, the primary token can be passed only once and cannot be used for connecting remove database. So the null user login fail error occured. this is a design feature of NTLM security. And the solution is set username and password in identity section.

<identityimpersonate ="true"username="Domain\UserName"password="pword"/>

Or change the connect string to use SQL authentication.

|||

Hi,

Thanks for all replies.

I solved the problem by creating new user in sql server and giving l user name and password in Connection String. Work fine.

Dim myconnection As SqlConnection = New SqlConnection("workstation id="Ur Work Station";packet size=4096;user id=XXXX;password=XXXX;data source=Server;initial catalog=Database")

This work fine. I tried Benson Yu's suggestions. It also work fine

Login failed

I'm having trouble getting my report to run on the reporting services
server. I can run it fine from my machine, but when I deploy it, I get a
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I've set the datasource to use a shared datasource, with a specific username
and password(which is the username and password for the reporting services
server, going after an external sql server with permissions to the reporting
services user.
Any ideas?
Thanx,
MikeAs long as I know, if you have your reporting services into one server
and your database into another, you CANNOT use trusted connection, you
must use a SQL Server login.
I'm telling this because I have the same problem and I didnt find
anything to solve so far.|||Go to report manager and the properties for your shared datasource. You
might have to set the credentials.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike Voissem" <voissemm@.stjosephs-marhshfield.org> wrote in message
news:u8cQEhqyFHA.2312@.TK2MSFTNGP14.phx.gbl...
> I'm having trouble getting my report to run on the reporting services
> server. I can run it fine from my machine, but when I deploy it, I get a
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> I've set the datasource to use a shared datasource, with a specific
> username
> and password(which is the username and password for the reporting services
> server, going after an external sql server with permissions to the
> reporting
> services user.
> Any ideas?
> Thanx,
> Mike
>|||Thanx Bruce,
That did the trick.
Mike
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:#gJkBBryFHA.2960@.tk2msftngp13.phx.gbl...
> Go to report manager and the properties for your shared datasource. You
> might have to set the credentials.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mike Voissem" <voissemm@.stjosephs-marhshfield.org> wrote in message
> news:u8cQEhqyFHA.2312@.TK2MSFTNGP14.phx.gbl...
> > I'm having trouble getting my report to run on the reporting services
> > server. I can run it fine from my machine, but when I deploy it, I get
a
> > Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > Server connection.
> > I've set the datasource to use a shared datasource, with a specific
> > username
> > and password(which is the username and password for the reporting
services
> > server, going after an external sql server with permissions to the
> > reporting
> > services user.
> > Any ideas?
> > Thanx,
> > Mike
> >
> >
>

Login Access

I want to give a login the ability to see all database objects, insert and
and delete data, run stored procedures, and execute objects within a specifi
c
database. I do not want them to create or delete any database objects or
adjust security. How do I accomplish that by using the database roles?
>I want to give a login the ability to see all database objects, insert and
> and delete data, run stored procedures, and execute objects within a
> specific
> database. I do not want them to create or delete any database objects or
> adjust security. How do I accomplish that by using the database roles?
With a user-defined role. There is no predefined role for executing
procedures. Check the permissions of the fixed db oles in BOL at
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/a08108a3-f1fb-43ac-a264-3f2f
9749db5d.htm.
Dejan Sarka
http://www.solidqualitylearning.com/blogs/

Logging Sql queries

In SQLServer 2000, I am sure there was a way that you configure the
database to log to a file each query that gets run against it.
However, I cannot seen to find where to set this up in Enterprise
Manager."Mystery Man" <PromisedOyster@.hotmail.com> wrote in message
news:87c81238.0405130309.7c0013fb@.posting.google.c om...
> In SQLServer 2000, I am sure there was a way that you configure the
> database to log to a file each query that gets run against it.
> However, I cannot seen to find where to set this up in Enterprise
> Manager.

I don't know any way to do exactly what you want, but there are options:

If you're going through ODBC, you can enable ODBC logging.
You can also enable profiler to capture all the traffic.

Another option is to invest in
http://www.lumigent.com/products/le_sql/le_sql.htm|||Mystery Man (PromisedOyster@.hotmail.com) writes:
> In SQLServer 2000, I am sure there was a way that you configure the
> database to log to a file each query that gets run against it.
> However, I cannot seen to find where to set this up in Enterprise
> Manager.

The Profiler is the tool you should use. Or at least where you should
start looking. If you are seriously into log everything which happens
on the server, you should set up a server-side trace with help of
the sp_trace procedures.

Furthermore, if you cannot accept anything to be unlogged because the
trace file fills up the disk, set the C2-autiding configuration option,
which throttles the server in this situation.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp