Logging query errors: windows

Showing posts with label windows. Show all posts

Friday, March 30, 2012

Login failed for user NT AUTHORITY\NETWORK SERVICE.

I've tried to use Windows authentication to connect to database in MS SQL Server 2000, my connection string like below:
"server=(local);Initial Catalog=myDatabase;Trusted_Connection=yes"
when I run my code, there is an error occur with below message:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'
My SQL Server is configured as Window authentication.
I can't resolve this problem.
Please whow me how to do!
Thank you very much!
You either need to grant the Network Service account access rights toSQL Server, or your application needs to impersonate a specific Windowsuser that has rights to the database.

Login failed for user NT AUTHORITY\NETWORK SERVICE.

I've just installed Windows Server 2003 and can't get past this.
I've changed the <processModel> userName to SYSTEM, I've added ASPNET to the Admin group, other tweaks with reboot but still can get it to work.
I'm not sure what the NT AUTHORITY domain is.

Anyone experience this?
Thanksok, looks like I figured it out. It works anyhow.
In the IIS Manager, I right clicked the Application Pools/DefaultAppPool node and hit properties.
I went to the Identity tab and for Predefined I selected Local System.|||Rex,

you saved me from near insanity....
I had installed tweeked...and gone over everything I could think of without any luck. Your one click solution did it. I guess I was trying to outsmart it all and fell on my face...

thanks a million,
Marc|||Thanks for this message, i can stop pulling my hair out now :-)|||This saved me alot of headaches too. But it also introduced one. You get a message that you are exposing IIS to attack and compromising sercurity.

Can someone explain how it should be done? I would like to be able to configure IIS to run with the minimal security needed to support ASP.NET pages and SQL Server access; but I do not have a clue what privilages and permissions would be needed.

Bill|||We were just chatting about this recently:view post 475172

(You can avoid the specific advice I gave because it wasn't particularly good :-) )

Terri|||The CGN IT article was exactly what I was looking for. Thanks.|||

tmorton:
We were just chatting about this recently: 475172 (You can avoid the specific advice I gave because it wasn't particularly good :-) ) Terri

This link is now dead, makes sinces since its from 2004. Anyone know where I can find the article now?

Thanks

|||

john.lieurance@.flhosp.org:
tmorton:
We were just chatting about this recently: 475172 (You can avoid the specific advice I gave because it wasn't particularly good :-) ) Terri
This link is now dead, makes sinces since its from 2004. Anyone know where I can find the article now?
Thanks

You can use the post ID from that link and surmise the new link:http://forums.asp.net/thread/475172.aspx

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

I have:

(1) SQL 2005 on a member server, Windows Authentication

(2) I'm using Visual Studio.Net 2005 on my Windows XP sp2 work station.

(3) From my machine, within my development application, I have no problem accessing the Data in the SQL server.

(4) I Receive the Login Failed error after I copy my project to the Test Web Server (Same machine that houses SQL) and test from either my machine or from the host server.

More details of the error message are:

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:

Line 33: DA = New SqlDataAdapter(sSql, CONN_STRING)
Line 34: DS = New DataSet
Line 35: DA.Fill(DS)
Line 36:
Line 37: Session("NameInquiry_DS") = DS

Source File: C:\Inetpub\wwwroot\nameinquiry\NameInquiry.aspx.vb Line: 35

The finished product is to be an Intranet site only; accessible by employees within our own private network.

The SQL is a new install with only test data.

What have I missed that is causing the permission problem? The event viewer shows a nonauthenticated user is causing the problem. But, how do I correct this?

Could you please post the connection string here and the part of the web.config file about impersonation (if any and not commented out). This is a configuration problem. Which user do you want to authenticate while connecting to the database ?

http://msdn2.microsoft.com/en-us/library/aa302377.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Hi, Terry

Try to read following article, they probably include solution to your problem:

1) http://support.microsoft.com/kb/316989/

2) https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=348662&SiteID=17

3) http://msdn2.microsoft.com/en-us/library/ab4e6cky(vs.80).aspx

Good Luck!

Ming.

|||

Here is my connection string and the Web.Config.

What is confusing is that I have zero issues running the application within VS ASP.NET. It's only when I run the application outside the development software.

When I check the Event Viewer on the server that houses SQL, the login name is blank. That's why I believe I have a permissions error. I just don't have any idea what permissions to set. It doesn't matter which desktop I use, the connection fails. If I try to access the website from the Server it's housed using the administrator login, I still get the Login failed message.

<connectionStrings>
<add name="myConnection" connectionString="server=MYSERVER;database=MyDataBase;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
<authentication mode="Forms" />
<roleManager enabled="true" />
<compilation debug="true" strict="false" explicit="true"/>
<pages>
<namespaces>
<clear/>
<add namespace="System"/>
<add namespace="System.Collections"/>
<add namespace="System.Collections.Specialized"/>
<add namespace="System.Configuration"/>
<add namespace="System.Text"/>
<add namespace="System.Text.RegularExpressions"/>
<add namespace="System.Web"/>
<add namespace="System.Web.Caching"/>
<add namespace="System.Web.SessionState"/>
<add namespace="System.Web.Security"/>
<add namespace="System.Web.Profile"/>
<add namespace="System.Web.UI"/>
<add namespace="System.Web.UI.WebControls"/>
<add namespace="System.Web.UI.WebControls.WebParts"/>
<add namespace="System.Web.UI.HtmlControls"/>
</namespaces>
</pages>

<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

|||

Ming,

The articles were very informitive but none of the possible solutions resolved my problem.

In an earlier post, I stated that everything worked fine within my VS .NET application. I have since learned that as long as I view data only, it works. If I attempt to do any writes, the application fails. Therefore, I'm more convinced this is an authentication related issue. Now I'm asking the following questions as I try to locate and resolve this issue:

I have determined that NT AUTHORITY\NETWORK SERVICE is the default login when I run my application. Based on what I've read from the many web posts concerning Windows Authenticaion, this is normal. How do I control the default login name? Meaning, can this be changed? If so, How? Should it be changed? Can I set various permissions to the various SQL databases? If so, How?

|||

Are your client and server machine in WORKGROUP instead of domain? If so, can you try grant database login to "<machinename>\guest" see whether it works?

As for your questions that how to control default login name, it is more of ASP.NET configuration issue, such as you can change ASP.NET account( http://www.bluevisionsoftware.com/WebSite/TipsAndTricksDetails.aspx?Name=AspNetAccount)

or post your question in ASP.NET forum.

The workaround here is

1) Change your connection string to force tcp connection(adding prefix "tcp:" in DataSource field ).

2) Use SQL authentication.

Good Luck!

Ming.

|||

Hi,

using Anonymous authentication will make you able to use a single user connecting to the database. This uer has to be setup in the security tab of the website in the IIS configuration screen. If you want to use this combination, you will have to set the tag of the web.config to impersonate=true. This will let you use login procided within the IIS to access SQL Server. If you want to authenticate / impersonate the user which is currently accessing the web page, you will have to (assuming that the web server is on the same server as the SQl Server) disbal the anonymous access option in the IIS configuration dialog.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I think that the 3rd of Ming's posts alludes to the potential problem and provides links to additional relevant info (and your hunch about authentication related issue would also be accurate). The most likely source of the problem, as Ming and Jens have pointed out, is impersonation.

NT AUTHORITY\NETWORK SERVICE is the account that IIS runs under on Windows Server 2003 and without any additional configuration, this is the account that will attempt to access whatever resources the web application needs. Since this is the account that is trying to access the database, it appears that the outbound attempt is not attempting the connection as the connected user. This is where the web.config settings that Jens mentioned come into play and there's a good synopsis of the options available on http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp (this looks identical to the link Jens posted earlier). You probably don't need or want IIS to run under a different account.

If you want each domain user to have a separate connection to the database, you will need to disable Anonymous Access and turn on Integrated Windows authentication (this would be on the Directory Security tab for the web site in IIS Manager). You'd then specify <identity impersonate="true"/> in your web.config. You may also want to change the <authentication> element to be mode="Windows"...check with MSDN and or the ASP.NET forum for additional info/guidance on the specifics there, as I'm well outside my area of expertise on that point.

If you want all DB access to route through a single connection (I'm not entirely sure that's advisable, but your circumstances may dictate this) and/or as a single user (also not advisable...auditability of data written to the database would be compromised, so you wouldn't be able to determine who made a given change), you could continue to use Integrated Windows authentication on your web app but change the web.config to be:

<identity impersonate="false"/>
<authentication mode="Windows"/>

You'd then provide access to the SQL Server table via one of the server roles for the NT AUTHORITY\NETWORK SERVICE account. An example would be to use sp_addrolemember to add this account to public and grant public insert and update permissions on these tables (if it doesn't have them already).

There is a "How To" article on these options available at: http://msdn2.microsoft.com/en-us/library/ht43wsex(VS.80).aspx

Good luck,

Jason

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

I have:

(1) SQL 2005 on a member server, Windows Authentication

(2) I'm using Visual Studio.Net 2005 on my Windows XP sp2 work station.

(3) From my machine, within my development application, I have no problem accessing the Data in the SQL server.

(4) I Receive the Login Failed error after I copy my project to the Test Web Server (Same machine that houses SQL) and test from either my machine or from the host server.

More details of the error message are:

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Source Error:

Line 33: DA = New SqlDataAdapter(sSql, CONN_STRING)
Line 34: DS = New DataSet
Line 35: DA.Fill(DS)
Line 36:
Line 37: Session("NameInquiry_DS") = DS

Source File: C:\Inetpub\wwwroot\nameinquiry\NameInquiry.aspx.vb Line: 35

The finished product is to be an Intranet site only; accessible by employees within our own private network.

The SQL is a new install with only test data.

What have I missed that is causing the permission problem? The event viewer shows a nonauthenticated user is causing the problem. But, how do I correct this?

http://msdn2.microsoft.com/en-us/library/aa302377.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Hi, Terry

Try to read following article, they probably include solution to your problem:

1) http://support.microsoft.com/kb/316989/

2) https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=348662&SiteID=17

3) http://msdn2.microsoft.com/en-us/library/ab4e6cky(vs.80).aspx

Good Luck!

Ming.

|||

Here is my connection string and the Web.Config.

What is confusing is that I have zero issues running the application within VS ASP.NET. It's only when I run the application outside the development software.

|||

Ming,

The articles were very informitive but none of the possible solutions resolved my problem.

|||

Are your client and server machine in WORKGROUP instead of domain? If so, can you try grant database login to "<machinename>\guest" see whether it works?

or post your question in ASP.NET forum.

The workaround here is

1) Change your connection string to force tcp connection(adding prefix "tcp:" in DataSource field ).

2) Use SQL authentication.

Good Luck!

Ming.

|||

Hi,

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

<identity impersonate="false"/>
<authentication mode="Windows"/>

There is a "How To" article on these options available at: http://msdn2.microsoft.com/en-us/library/ht43wsex(VS.80).aspx

Good luck,

Jason

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 'NT AUTHORITY\ANONYMOUS LOGON'

Hello all -

I'm trying to connect to a Sql Server 2005 database from my local development machine, which is running IIS 5.1 (Windows XP Pro). The web application is not using impersonation and has anonymous access enabled. In my system's machine.config file, I've set the processModel section to look like:

This has been working fine for us connecting to SQL Server 2000 databases (running on Windows 2003). When we connect, I access Sql 2000 databases under the context of "OurDomain\MyMachineName$". However, we've recently installed Sql Server 2005 on a new Windows 2003 server & when I connect to that server, I receive the error:

System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

when trying to call the SqlConnection.Open() method. Our connection string is very basic:

Data Source=sql-dev2; Initial Catalog=TestDatabase; Integrated Security=True; Application Name=PrototypeWebservice;

In the Sql Server logins, we've granted the computer account "OurDomain\MyMachineName$" db_owner access to every database (in both Sql Server 2000 & 2005).

I am able to connect to the Sql Server 2005 databases if I change my section in machine.config to <processModel userName="OurDomina\myPersonalAccount" password="myPersonalPwd"/>, or if I move the application to an IIS6 server & set the application pool identity to NETWORK SERVICE, but we'd like to continue accessing our Sql Server 2005 databases (from our development machines running IIS5.1) as we currently access our Sql Server 2000 databases; under the context of "OurDomain\MyMachineName$".

Would anyone have any ideas why this would be happening or how to resolve? Thanks in advance.

Please check this blog: http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx

.....

[1] "Login Failed for user 'NT Authority\ANONYMOUS' LOGON"

In this scenario, client make tcp connection, and it is most likely running under LocalSystem account, and there is no SPN registered for SQL instance, hence, NTLM is used, however, LocalSystem account inherits from System Context instead of a true user-based context, thus, failed as 'ANONYMOUS LOGON'. See http://support.microsoft.com/kb/132679.

The workaround here is

a. ask your domain administrator to manually register SPN if your SQL Server running under a domain user account.

b. use NP connection.

c. change your sql server to run under either localsystem account or networkservice account.

|||

That was the ticket!!! Thank you very much.

For future reference, the problem we ran into was that we had multiple active directory accounts registered with the same SPN. One entry was registered under the computer account sql server was running on & the other was the user account the sql server service was running under. We detected this by looking into the System event log on the domains PDC (the entry was EventID 11, Source KDC. Exact steps we followed were those suggested by other users on the thread: http://www.eventid.net/display.asp?eventid=11&eventno=569&source=KDC&phase=1). After removing the entry for the computer account, kerberos authentication succeeded.

Thanks again!

|||Thanks for the feedback.

Wednesday, March 28, 2012

Login failed for user NT AUTHORITY\ANONYMOUS LOGON

Hello everyone,

I am receiving the above error when using a workstation to connect to my webfiles.

I am using windows authentication (whcih I have selected as my only option on the IIS).
Impersonate is set to true in the webconfig file, with authentication set to Windows.

My connection string is: SQLConnection1 = "initial catalog=SIMS;data source=spacesql;integrated security=SSPI"

It runs no problem when I use the localhost.
It allows me to use other aspx pages that do not connect to the SQL server.
It only gives me this error when I am using a page that tries to connect to the SQL server.

The SQL files reside on a separate server to the IIS and I would like it to remain this way.

Can anyone help me wit this please

Thank you,

RebeccaOk, stupid question.

How is an SQL Server on Computer B supposed to authorize users according to a user account on computer A? Without domain, without using a domain account et al.

Answer: it can not.

An this is your problem.|||Hi,
I suggest you look for information on 'Accessing SQL Server using a Mapped Windows Domain Server'. That may have the solution you are looking for. Try msdn.microsoft.com, and look for this and other authentication and authorization info for web based applications.
Good luck with your project.|||Both computers are on a domain using a domain account et al.
I am not that stupid.

Login failed for user 'NT Authority\Anonymous

I have a Merge Replication configuration in which one Publisher replicates
with 20 subscribers.
Currently, we use Windows Integrated security.
I get the following error when attempting to access tables in a remote
server from the publisher.
In Query Analyzer window, logged into publisher, I type
SELECT * FROM <subscriber1>.<databasename>..<tablename>
And get the following error message:
Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
1) From everything I’ve read, including article 827422, it is necessary to
go to Mixed Security in order to overcome this security issue. Is this true?
2) Will changing the security mode on the Publisher and all 20 subscribers
cause any problems with replication?1) That's a major over-generalization to say that changing it to SQL
Authentication (Mixed Mode) will allow you to over come this. It's working
around the issue entirely. You will still have issues with Windows
authentication, and should deal with those.
When you set up the merge subscribers, are they anonymous? Did you specify
for the merge agent to connect to the subscriber (if push) or publisher (if
pull) under the credentials of the SQL Agent account? What is that account?
Can you log onto each server (pub and sub) as their respective SQL Agent
accounts, then try to open Query Analyzer and point to the other server usin
g
windows authentication? Do you get the same "Anonymous error"? Are they th
e
same account? If not, are they in the same domain? Make sure they both have
the correct rights to each other's machine. If not in the same domain, you
need to look at trust issues. If there is no trust, then you will either
have to set one up, or use mixed mode and SQL accounts.
2) No, unless you consider the time to restart SQL an issue.
Donna Lambert
"elpepe" wrote:

> I have a Merge Replication configuration in which one Publisher replicates
> with 20 subscribers.
> Currently, we use Windows Integrated security.
> I get the following error when attempting to access tables in a remote
> server from the publisher.
> In Query Analyzer window, logged into publisher, I type
> SELECT * FROM <subscriber1>.<databasename>..<tablename>
> And get the following error message:
> Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
> 1) From everything I’ve read, including article 827422, it is necessary
to
> go to Mixed Security in order to overcome this security issue. Is this tru
e?
> 2) Will changing the security mode on the Publisher and all 20 subscribers
> cause any problems with replication?
>
>

Login failed for user COLDFIRE/ASPNET

i have my SQL server in windows integrated security so my connection string doesnt have to have password and uid stuff.
this is my connection string

data source=COLDFIRE;initial catalog=Northwind;integrated security=SSPI;persist security info=True;workstation id=COLDFIRE;packet size=4096

i tried this in windows form project of .net and work fine, i connected easily but when i tried it in asp project i got this error :

whats wrong with it?That's because the ASPNet user account, which was created when you installed ASP.Net, is not set up as a user on the SQL Server.

login failed for user ... Not Associated with a trusted SQL Server

Hello,
I'm trying to connect a mobile computer runing under windows CE to a
database located on a windows XP desktop.
The mobile computer application is written in C# under Visual Studio .NET
2003.
My problem occurs when I execute mConnection.Open();
A SqlException is caught with this message :
Login failed for user '(null)'. Reason : Not associated with a trusted SQL
Server connection.
here is the connection string :
mConnection = new SqlConnection("User ID=sa;data source=" + mSqlServer +
";Integrated Security=SSPI;initial catalog=IDPS;Password=xxxx;persist
security info=false;Trusted_Connection=yes");
What can I do to correct it ?
In your connection string, you are specifying parameters for
both SQL authentication and Windows authentication - it
needs to be one or the other. If you use Windows
authentication, you don't specify a user id and password.
You can find some examples at:
http://www.carlprothman.net/Default...anagedProvider
-Sue
On Tue, 2 Aug 2005 07:56:11 -0700, Christian F CLY
<ChristianFCLY@.discussions.microsoft.com> wrote:

>Hello,
>I'm trying to connect a mobile computer runing under windows CE to a
>database located on a windows XP desktop.
>The mobile computer application is written in C# under Visual Studio .NET
>2003.
>My problem occurs when I execute mConnection.Open();
>A SqlException is caught with this message :
>Login failed for user '(null)'. Reason : Not associated with a trusted SQL
>Server connection.
>here is the connection string :
>mConnection = new SqlConnection("User ID=sa;data source=" + mSqlServer +
>";Integrated Security=SSPI;initial catalog=IDPS;Password=xxxx;persist
>security info=false;Trusted_Connection=yes");
>What can I do to correct it ?

login failed for user ... Not Associated with a trusted SQL Server

Hello,
I'm trying to connect a mobile computer runing under windows CE to a
database located on a Windows XP desktop.
The mobile computer application is written in C# under Visual Studio .NET
2003.
My problem occurs when I execute mConnection.Open();
A SqlException is caught with this message :
Login failed for user '(null)'. Reason : Not associated with a trusted SQL
Server connection.
here is the connection string :
mConnection = new SqlConnection("User ID=sa;data source=" + mSqlServer +
";Integrated Security=SSPI;initial catalog=IDPS;Password=xxxx;persist
security info=false;Trusted_Connection=yes");
What can I do to correct it ?In your connection string, you are specifying parameters for
both SQL authentication and Windows authentication - it
needs to be one or the other. If you use Windows
authentication, you don't specify a user id and password.
You can find some examples at:
http://www.carlprothman.net/Default...ManagedProvider
-Sue
On Tue, 2 Aug 2005 07:56:11 -0700, Christian F CLY
<ChristianFCLY@.discussions.microsoft.com> wrote:

>Hello,
>I'm trying to connect a mobile computer runing under windows CE to a
>database located on a Windows XP desktop.
>The mobile computer application is written in C# under Visual Studio .NET
>2003.
>My problem occurs when I execute mConnection.Open();
>A SqlException is caught with this message :
>Login failed for user '(null)'. Reason : Not associated with a trusted SQL
>Server connection.
>here is the connection string :
>mConnection = new SqlConnection("User ID=sa;data source=" + mSqlServer +
>";Integrated Security=SSPI;initial catalog=IDPS;Password=xxxx;persist
>security info=false;Trusted_Connection=yes");
>What can I do to correct it ?sql

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

I have a windows 2003 server hosting MS SQL Server 2005. Another windows 2003 server hosting my App, and clients from the local intranet and outside (web). How do I surpass this problem, when it all works fine locally on my development machine?

Use Forms authentication!

|||

I am using Forms authentication.

connectionStrings>

addname="memSocConnection"connectionString=" Data Source=WSPASQL01; Initial Catalog=mem_soc;Integrated Security=True"providerName="System.Data.SqlClient" />

addname="MySqlRoleManagerConnection"connectionString="Data Source=WSPASQL01;Initial Catalog=mem_soc_core;Integrated Security=True"providerName="System.Data.SqlClient" />

addname="MySqlMembershipProviderConnection"connectionString="Data Source=WSPASQL01;Initial Catalog=mem_soc_core;Integrated Security=True"providerName="System.Data.SqlClient" />

connectionStrings>

This works fine locally. I am trying to migrate the application onto the servers. As soon as I use the WSPASQL01 server it fails. I have followed the walkthrough from microsoft on using forms authentication and still no progress. I have assigned roles to the login 'aspnet'.

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

Hi,

I have 2 windows 2003 server, i instllaed sql server 2005 enterprise edition on the first one (Mixed Mode), and i am trying to install sql server reporting 2000 on the second one,

I installed the sql 2000 connectivity only on the second one , and i installed the sql server sp4 also, while installing reporting services i used the sql login account (sa,pwd)

i got the following error :

Cannot connect to sql server instance ...

NB1: Allow Remote connection is enabled on sql server 2005.

NB2: I tried to connect from server 2 to server 1 from odbc and it worked properly with (sa,pwd) i have only a problem from reporting server.

Please any help?

Tarek Ghazali

SQL Server MVP

Are the machines in the same domain? What is the network configuration? What does "sql 2000 connectivity" mean?

Have you checked the errorlog? Is there any additional information on the failure there?

Try running a Profiler trace on the SQL Server machine to see if you can find any additional information on the login attempt.

Thanks
Laurentiu

|||

Here's a thread that may be related to the issue you are seeing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=422598&SiteID=1

Thanks
Laurentiu

|||

Hi Laurentiu,

Thx for your reply,

I have 2 servers on the same domain and under vmware virtual

server (the new release beta 2) ,about sql 2000 connectivity you can install sql server 2000 as (database server or client or connectivity).

I don't have any log error.

Thanks,

Tarek Ghazali

SQL Server MVP

|||

Login failures are normally logged. Are you sure you checked the log on the right server - the one you were trying to connect to? Also, have you got any insights from running a Profiler trace?

Thanks
Laurentiu

|||

Hi Laurentiu,

I created a user on the domain , and i logged on windows by this user on the second server, i added this user to have access login on the first server and it worked fine.

Regards,

Tarek Ghazali

SQL Server MVP

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

Hi,

I have 2 windows 2003 server, i instllaed sql server 2005 enterprise edition on the first one (Mixed Mode), and i am trying to install sql server reporting 2000 on the second one,

I installed the sql 2000 connectivity only on the second one , and i installed the sql server sp4 also, while installing reporting services i used the sql login account (sa,pwd)

i got the following error :

Cannot connect to sql server instance ...

NB1: Allow Remote connection is enabled on sql server 2005.

NB2: I tried to connect from server 2 to server 1 from odbc and it worked properly with (sa,pwd) i have only a problem from reporting server.

Please any help?

Tarek Ghazali

SQL Server MVP

Are the machines in the same domain? What is the network configuration? What does "sql 2000 connectivity" mean?

Have you checked the errorlog? Is there any additional information on the failure there?

Try running a Profiler trace on the SQL Server machine to see if you can find any additional information on the login attempt.

Thanks
Laurentiu

|||

Here's a thread that may be related to the issue you are seeing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=422598&SiteID=1

Thanks
Laurentiu

|||

Hi Laurentiu,

Thx for your reply,

I have 2 servers on the same domain and under vmware virtual

server (the new release beta 2) ,about sql 2000 connectivity you can install sql server 2000 as (database server or client or connectivity).

I don't have any log error.

Thanks,

Tarek Ghazali

SQL Server MVP

|||

Login failures are normally logged. Are you sure you checked the log on the right server - the one you were trying to connect to? Also, have you got any insights from running a Profiler trace?

Thanks
Laurentiu

|||

Hi Laurentiu,

I created a user on the domain , and i logged on windows by this user on the second server, i added this user to have access login on the first server and it worked fine.

Regards,

Tarek Ghazali

SQL Server MVP

sql

Monday, March 26, 2012

Login failed for user '(null)'...

There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
selected a database on PC2 using Windows authentication and executed the
following query:
select * from PC1.Database1.dbo.Table1
I got this error:
Server: Msg 18452, Level 14, State 1, Line 2
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
Both servers are set to mixed mode authentication and both are linked
using sp_addlinkedserver. Does anybody have a solution to this issue?
--
Best regards,
Vladimir.Vova
When you created linked server what is the login do you specify?
"Vladimir Svrkota" <see@.reply.to> wrote in message
news:1o1fojctigtr3.dlg@.vladimir.svrkota...
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
> --
> Best regards,
> Vladimir.|||Vladimir Svrkota wrote:
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
>
Hi
You most likely need to specify a login that can access the remote
server. If you don't specify anything, the server will try to connect
using your NT login which requires that the both servers is set to
delegation.
Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||"Steen Schlüter Persson (DK)" wrote:
> Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
Thanks. I'll take a look.
--
Best regards,
Vladimir.

Login failed for user '(null)'...

There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
selected a database on PC2 using Windows authentication and executed the
following query:
select * from PC1.Database1.dbo.Table1
I got this error:
Server: Msg 18452, Level 14, State 1, Line 2
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
Both servers are set to mixed mode authentication and both are linked
using sp_addlinkedserver. Does anybody have a solution to this issue?
Best regards,
Vladimir.Vova
When you created linked server what is the login do you specify?
"Vladimir Svrkota" <see@.reply.to> wrote in message
news:1o1fojctigtr3.dlg@.vladimir.svrkota...
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
> --
> Best regards,
> Vladimir.|||Vladimir Svrkota wrote:
> There are two computers, PC1 and PC2. On PC1 I started QueryAnalyzer and
> selected a database on PC2 using Windows authentication and executed the
> following query:
> select * from PC1.Database1.dbo.Table1
> I got this error:
> Server: Msg 18452, Level 14, State 1, Line 2
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Both servers are set to mixed mode authentication and both are linked
> using sp_addlinkedserver. Does anybody have a solution to this issue?
>
Hi
You most likely need to specify a login that can access the remote
server. If you don't specify anything, the server will try to connect
using your NT login which requires that the both servers is set to
delegation.
Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||"Steen Schlter Persson (DK)" wrote:

> Try to look up sp_addlinkedsrvlogin in BOL - that will give you more info.
Thanks. I'll take a look.
Best regards,
Vladimir.sql

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect

After an office move (accompanied by IP Address changes), I can no longer
use Windows authentication to connect to one of my SQL Server machines.
Nothing else seems to have changed. This is an example of what I am facing.
For simplicity, I conducted this with Query Analyzer, attempting to connect
via SQL Server authentication and Windows authentication:
SERVER1 --> SERVER2 : Both succeed
SERVER1 --> SERVER3 : Both succeed
SERVER2 --> SERVER1 : Both succeed
SERVER2 --> SERVER3 : Both succeed
SERVER3 --> SERVER1 : Both succeed
SERVER3 --> SERVER2 : SQL Server Authentication succeeds, but Windows
authentication returns: Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.
Server Specs
============
SERVER1 : SQL2K Enterprise Edition, SP3 (8.00.760) on Windows 2000 Server
SERVER2 : SQL2K Developer Edition, SP3a (8.00.818) on Windows 2000 Server
SERVER3 : SQL2K Developer Edition, SP3a (8.00.818) on Windows Server 2003
Named pipes and TCP/IP are enabled on all three (client and network).
SERVER1 sits in our DMZ; its IP Address did not change. SERVERs 2 & 3 got
new addresses and new DNS entries. None is on a domain.
I have seen similar questions posed here, but have yet to see a suggestion
that resolves my problem. Any ideas?
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.
If server2 and serv3 are not on a domain what account are you using to log
on with windows authentication? Are you using pass-thru authentication? If
the user being returned is NULL (as in your case) it means the problem is
outside of sql permissions, this means sql cannot even see what account is
trying to log on to it. One example of how this can happen is this:
Server2 is on Workgroup2 - there is a local account User2 - there is NO
local account User3 on this machine
Server3 is on Workgroup3 - there is a local account User3 - there is NO
local account User2 on this machine
So now if I log on to Server3 as user User3, and then use windows
authentication to connect to server2 this would fail since on the Server2
no account User3 exists, what you would usually see is a login entry in the
SECURITY log on server2 for an account: ANONYMOUS (which by default does
not have permissions into SQL Server).
To troubleshoot this issue I would recommend
1. If you are using PASS-THROUGH authentication (per my example above),
create an account User3 on your Server2 box which has the same name and
password as the user3 account on Server3
2. Enable security account auditing on your Server2 box to see what account
is seen on the Server2 box when you try your windows authentication
connection - I suspect you may see ANONYMOUS or something similar
3. Check these articles as well:
- BOL topic: Security Account Delegation
- You may not be able to connect to a SQL Server that is running on a - ID:
840219
http://support.microsoft.com/?id=840219
- How to troubleshoot connectivity issues in SQL Server 2000 - ID: 827422
http://support.microsoft.com/?id=827422
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Fany Vargas [MSFT] wrote:
> If server2 and serv3 are not on a domain what account are you
> using to log on with windows authentication?
I am using local accounts on both servers, in which the account name &
password are identical. Recall that SERV2 --> SERV3 is successful with
Windows Authentication, but SERV3 --> SERV2 is not.

> Are you using pass-thru authentication?
I'm not sure what you mean by this. If I select "Windows Authentication"
when connecting (whether in a SQL Server tool or with something like a UDL
file setup), the one direction fails while the other succeeds...

> 1. If you are using PASS-THROUGH authentication (per my example
> above), create an account User3 on your Server2 box which has the
> same name and password as the user3 account on Server3
Aready there...

> 2. Enable security account auditing on your Server2 box to see what
> account is seen on the Server2 box when you try your windows
> authentication connection - I suspect you may see ANONYMOUS or
> something similar
I had actually already tried this. It logs nothing whatsoever, which I
assume means the whole process is aborted before a connection is even
attempted.

> ...You may not be able to connect to a SQL Server that is running...
> http://support.microsoft.com/?id=840219
I was so sure this was going to solve my problem, as it describes it
precisely. Unfortunately, the resolution therein does not help me connect.
In hindsight, I suppose I should not have expected it to help, as my problem
arose after the physical (and network) move. In other words, since Local
Security Policy was not a hurdle before the problem began, why should it be
the cause of the problem?
Is it possible I am merely correlating the network changes with this?
Perhaps a recent Windows Update plays a part...

> - How to troubleshoot connectivity issues in SQL Server 2000 - ID:
> 827422 http://support.microsoft.com/?id=827422
This was actually my starting point. I have no idea where to go from here.
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.
|||1. I can see you are indeed using Pass-through authentication (this means
you are using a local account with same name and pwd to authenticate) .
You should be seeing an entry in the security log. Can you ensure that the
security policy to enable auditing has been set? If there is a group policy
defined (there should not be if its in a workgroup) then this would
override your local security policy. Also, you can you enable security
auditing on the sql server itself (see BOL topic: SQL Server Properties
(Security Tab))
2. Are you able to connect from some OTHER client? Or do trusted
connections to SRV2 fail from ALL clients?
from your description it seems that trusted connections work from all other
clients except SRV3
3. What is the startup account of the SQL Service account is it the local
administrator account? If not, try setting it to local admin and test your
connection.
4. On SRV3 try creating an LMHOST entry for SRV2, are you now able to
connect with trusted auth?
5. Can you create a new account TESTACCOUNT on both SRV2 and SRV3 (with
same password) and see if you can use pass through authentication with
these new accounts (the issue may be account specific)
6. When connecting to SRV2 specify the IP address rather than the network
name - does it now work?
7. Check if the account has "impersonate client after authentication" right
on SRV2 - try for both sql service account and the account trying to log on
8. This error usually refers to security issues. Essentially SQL server is
unable to get information about the NT account that you are trying to use
to connect to it. The fact that you are not seeing an entry in the security
log hints to this as well. You may also want to try running a netmon trace
to see if we ever establish a connection to sql.
9. Does the account have "Access this computer from the network" rights? If
not try adding this right and retry your connection
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||First I'd like to thank you for all of your help - my problem is solved. My
comments (and a question) are inline:
Fany Vargas [MSFT] wrote:
> 1. I can see you are indeed using Pass-through authentication (this
> means you are using a local account with same name and pwd to
> authenticate) . You should be seeing an entry in the security log.
> Can you ensure that the security policy to enable auditing has been
> set? If there is a group policy defined (there should not be if its
> in a workgroup) then this would override your local security policy.
> Also, you can you enable security auditing on the sql server itself
> (see BOL topic: SQL Server Properties (Security Tab))
The security log mirrors my specific error message - once per connection
attempt. None of the policy settings in KB:840219 helped, though this was
not really a surprise, given that only one direction was failing (of the 6
possible between 3 servers), not to mention the fact that this connectivity
problem is new, and I am unaware of recent changes to the policies on either
machine.

> 2. Are you able to connect from some OTHER client? Or do trusted
> connections to SRV2 fail from ALL clients?
> from your description it seems that trusted connections work from all
> other clients except SRV3
Not only that, but trusted connections TO all other servers were fine from
that machine...

> 3. What is the startup account of the SQL Service account is it the
> local administrator account? If not, try setting it to local admin
> and test your connection.
Local System. Changing it had no effect.

> 4. On SRV3 try creating an LMHOST entry for SRV2, are you now able to
> connect with trusted auth?
No.

> 5. Can you create a new account TESTACCOUNT on both SRV2 and SRV3
> (with same password) and see if you can use pass through
> authentication with these new accounts (the issue may be account
> specific)
Different accounts did not matter.

> 6. When connecting to SRV2 specify the IP address rather than the
> network name - does it now work?
> 7. Check if the account has "impersonate client after authentication"
> right on SRV2 - try for both sql service account and the account
> trying to log on
> 8. This error usually refers to security issues. Essentially SQL
> server is unable to get information about the NT account that you are
> trying to use to connect to it. The fact that you are not seeing an
> entry in the security log hints to this as well. You may also want
> to try running a netmon trace to see if we ever establish a
> connection to sql.
> 9. Does the account have "Access this computer from the network"
> rights? If not try adding this right and retry your connection
Suffice it to say that I tried all of the above, without solution. Then I
came back the next day and demonstrated the problem to one of our network
guys, and as I walked him through all of the steps I took to show the
different error messages, I got it to work by setting up an alias to use
Named Pipes.
Now, this was one of the first steps I took, as it was the natural place to
start, and I revisited it several times through this ordeal. But it never
led to resolution until Friday. I also noticed on Friday that I could again
map network drives by name rather than IP Address -- I had been getting the
"duplicate name exists on the network" error**
In the end, I am left wondering if this was just some WINS artifact or
something. Is this possible? And even if it were, why would Windows
Authentication fail over IP, but succeed over named pipes?
**Recall that the IP Address changed on both machines. But this drive
mapping error was not preventing Windows Authentication from other machines.
Furthermore, success at drive mapping by IP Address was not paired with
success at SQL Server connection by IP Address.
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.
|||If named pipes worked and TCP did not (assuming that SQL was indeed
listening on TCP) then it may be an Kerberos - SPN issue. You may have a
duplicate or invalid SPN. To see the list of SPN's you can use the SETSPN
utility
(http://www.microsoft.com/downloads/d...31fd-ab77-46a3
-9cfe-ff01d29e5c46&displaylang=en). However, SPN's should only apply in a
domain environment not a workgroup environment. Let us know if you get any
results when running setspn -L ...
See these references:
* BOL Topic: Security Account Delegation
* PRB: Setspn Fails if Domain Name Differs from NetBIOS Name Where SQL -
ID: 277658 - http://support.microsoft.com/?id=277658
* INF: SQL Server 2000 Kerberos support including SQL Server virtual - ID:
319723 (available at http://support.microsoft.com)
* You receive a "Cannot generate SSPI context" error message when you use -
ID: 824402 (available at http://support.microsoft.com)
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Dave Anderson wrote:
> After an office move...
> SERVER1 --> SERVER2 : Both succeed
> SERVER1 --> SERVER3 : Both succeed
> SERVER2 --> SERVER1 : Both succeed
> SERVER2 --> SERVER3 : Both succeed
> SERVER3 --> SERVER1 : Both succeed
> SERVER3 --> SERVER2 : SQL Server Authentication succeeds, but Windows
> authentication returns: Login failed for user '(null)'. Reason: Not
> associated with a trusted SQL Server connection...
One final footnote: I believe I now know the cause of this problem. When we
moved offices, we also consolidated offices. That is to say that groups from
several facilities are now housed at the same place, with a single LAN. And
one of the groups from a different facility brought along a machine with the
same MACHINE NAME as SERVER2 (though ours had the DNS entry).
This appears to be the cause of the "duplicate name" problem with mapping
drives, and is most likely the cause of our SQL Server authentication
nightmares.
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect

Hello:
I've just upgraded Windows 2000 server to Windows server 2003, and after
this I cannot get to the SQL server Enterprise manager, I'm getting error
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
I've found many articles about it, but they are all about problems with ASP
or ASP.Net. I don't have a problem with ASP.Net, my Intranet application is
running OK.
I still can get in using SQL server connection if I change the registration
properties, but if I use Trusted connections I get this error. And I need to
use trusted connections.
I would appreciate any help very much.
Thank you,
--
Peter Afonin"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> I've just upgraded Windows 2000 server to Windows server 2003, and after
> this I cannot get to the SQL server Enterprise manager, I'm getting error
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I've found many articles about it, but they are all about problems with
ASP
> or ASP.Net. I don't have a problem with ASP.Net, my Intranet application
is
> running OK.
> I still can get in using SQL server connection if I change the
registration
> properties, but if I use Trusted connections I get this error. And I need
to
> use trusted connections.
If you enable auditing on both the server and SQL Server, do you see any
failed login attempts? If so, which account is being used?
Steve|||"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> I've just upgraded Windows 2000 server to Windows server 2003, and after
> this I cannot get to the SQL server Enterprise manager, I'm getting error
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I've found many articles about it, but they are all about problems with
ASP
> or ASP.Net. I don't have a problem with ASP.Net, my Intranet application
is
> running OK.
> I still can get in using SQL server connection if I change the
registration
> properties, but if I use Trusted connections I get this error. And I need
to
> use trusted connections.
Moments after I posted the last message, I found this link which may be of
value to you:
How to troubleshoot connectivity issues in SQL Server 2000
http://www.support.microsoft.com/?id=827422
Steve|||Peter,
CAUSE
This error occurs because the SQL Server is configured to use "Windows only"
authentication.
RESOLUTION
On the SQL Server Security tab, configure SQL Server to use "SQL Server and
Windows" authentication.
Russell Fields
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Hello:
> I've just upgraded Windows 2000 server to Windows server 2003, and after
> this I cannot get to the SQL server Enterprise manager, I'm getting error
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I've found many articles about it, but they are all about problems with
ASP
> or ASP.Net. I don't have a problem with ASP.Net, my Intranet application
is
> running OK.
> I still can get in using SQL server connection if I change the
registration
> properties, but if I use Trusted connections I get this error. And I need
to
> use trusted connections.
> I would appreciate any help very much.
> Thank you,
> --
> Peter Afonin
>|||Thank you, but it's configured this way.
Peter
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:O4mPpDUMEHA.624@.TK2MSFTNGP11.phx.gbl...
> Peter,
> CAUSE
> This error occurs because the SQL Server is configured to use "Windows
only"
> authentication.
> RESOLUTION
> On the SQL Server Security tab, configure SQL Server to use "SQL Server
and
> Windows" authentication.
> Russell Fields
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > Hello:
> >
> > I've just upgraded Windows 2000 server to Windows server 2003, and after
> > this I cannot get to the SQL server Enterprise manager, I'm getting
error
> > "Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > Server connection"
> >
> > I've found many articles about it, but they are all about problems with
> ASP
> > or ASP.Net. I don't have a problem with ASP.Net, my Intranet application
> is
> > running OK.
> >
> > I still can get in using SQL server connection if I change the
> registration
> > properties, but if I use Trusted connections I get this error. And I
need
> to
> > use trusted connections.
> >
> > I would appreciate any help very much.
> >
> > Thank you,
> >
> > --
> > Peter Afonin
> >
> >
>|||Thank you, Steve.
I'm working on it, buy now I even cannot get in with my administrative (sa)
account. I don't know what's wrong.
Peter
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > I've just upgraded Windows 2000 server to Windows server 2003, and after
> > this I cannot get to the SQL server Enterprise manager, I'm getting
error
> > "Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > Server connection"
> >
> > I've found many articles about it, but they are all about problems with
> ASP
> > or ASP.Net. I don't have a problem with ASP.Net, my Intranet application
> is
> > running OK.
> >
> > I still can get in using SQL server connection if I change the
> registration
> > properties, but if I use Trusted connections I get this error. And I
need
> to
> > use trusted connections.
> Moments after I posted the last message, I found this link which may be of
> value to you:
> How to troubleshoot connectivity issues in SQL Server 2000
> http://www.support.microsoft.com/?id=827422
> Steve
>|||By chance, did you change the security mode and not restart MSSQLServer
service?
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Thank you, Steve.
> I'm working on it, buy now I even cannot get in with my administrative
(sa)
> account. I don't know what's wrong.
> Peter
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> >
> > > I've just upgraded Windows 2000 server to Windows server 2003, and
after
> > > this I cannot get to the SQL server Enterprise manager, I'm getting
> error
> > > "Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL
> > > Server connection"
> > >
> > > I've found many articles about it, but they are all about problems
with
> > ASP
> > > or ASP.Net. I don't have a problem with ASP.Net, my Intranet
application
> > is
> > > running OK.
> > >
> > > I still can get in using SQL server connection if I change the
> > registration
> > > properties, but if I use Trusted connections I get this error. And I
> need
> > to
> > > use trusted connections.
> >
> > Moments after I posted the last message, I found this link which may be
of
> > value to you:
> >
> > How to troubleshoot connectivity issues in SQL Server 2000
> > http://www.support.microsoft.com/?id=827422
> >
> > Steve
> >
> >
>|||Peter,
Do you get the same error when logging in as 'sa'? If so, that is telling
you that the server is not accepting standard SQL logins, no matter what the
settings seems to be.
Do you have a domain account with sysadmin rights that you can login with?
If so, try that one.
During the upgrade of your server, did you lose any local Windows accounts?
Domain accounts? Look at article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307002
Russell Fields
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Thank you, Steve.
> I'm working on it, buy now I even cannot get in with my administrative
(sa)
> account. I don't know what's wrong.
> Peter
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> >
> > > I've just upgraded Windows 2000 server to Windows server 2003, and
after
> > > this I cannot get to the SQL server Enterprise manager, I'm getting
> error
> > > "Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL
> > > Server connection"
> > >
> > > I've found many articles about it, but they are all about problems
with
> > ASP
> > > or ASP.Net. I don't have a problem with ASP.Net, my Intranet
application
> > is
> > > running OK.
> > >
> > > I still can get in using SQL server connection if I change the
> > registration
> > > properties, but if I use Trusted connections I get this error. And I
> need
> > to
> > > use trusted connections.
> >
> > Moments after I posted the last message, I found this link which may be
of
> > value to you:
> >
> > How to troubleshoot connectivity issues in SQL Server 2000
> > http://www.support.microsoft.com/?id=827422
> >
> > Steve
> >
> >
>|||OK. The (null) probably suggests the comment in my other post. (Unless
'sa' is returning a similar message.)
IF in the unlikely event that your registry is messed up:
http://support.microsoft.com/default.aspx?scid=kb;en-us;285097
Russell Fields
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uNK2oUUMEHA.3216@.TK2MSFTNGP12.phx.gbl...
> Thank you, but it's configured this way.
> Peter
> "Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
> news:O4mPpDUMEHA.624@.TK2MSFTNGP11.phx.gbl...
> > Peter,
> >
> > CAUSE
> > This error occurs because the SQL Server is configured to use "Windows
> only"
> > authentication.
> > RESOLUTION
> > On the SQL Server Security tab, configure SQL Server to use "SQL Server
> and
> > Windows" authentication.
> >
> > Russell Fields
> > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > > Hello:
> > >
> > > I've just upgraded Windows 2000 server to Windows server 2003, and
after
> > > this I cannot get to the SQL server Enterprise manager, I'm getting
> error
> > > "Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL
> > > Server connection"
> > >
> > > I've found many articles about it, but they are all about problems
with
> > ASP
> > > or ASP.Net. I don't have a problem with ASP.Net, my Intranet
application
> > is
> > > running OK.
> > >
> > > I still can get in using SQL server connection if I change the
> > registration
> > > properties, but if I use Trusted connections I get this error. And I
> need
> > to
> > > use trusted connections.
> > >
> > > I would appreciate any help very much.
> > >
> > > Thank you,
> > >
> > > --
> > > Peter Afonin
> > >
> > >
> >
> >
>|||I did restart it, thanks.
Peter
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:e1RnoaUMEHA.1556@.TK2MSFTNGP10.phx.gbl...
> By chance, did you change the security mode and not restart MSSQLServer
> service?
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > Thank you, Steve.
> >
> > I'm working on it, buy now I even cannot get in with my administrative
> (sa)
> > account. I don't know what's wrong.
> >
> > Peter
> >
> > "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> > news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > >
> > > > I've just upgraded Windows 2000 server to Windows server 2003, and
> after
> > > > this I cannot get to the SQL server Enterprise manager, I'm getting
> > error
> > > > "Login failed for user '(null)'. Reason: Not associated with a
trusted
> > SQL
> > > > Server connection"
> > > >
> > > > I've found many articles about it, but they are all about problems
> with
> > > ASP
> > > > or ASP.Net. I don't have a problem with ASP.Net, my Intranet
> application
> > > is
> > > > running OK.
> > > >
> > > > I still can get in using SQL server connection if I change the
> > > registration
> > > > properties, but if I use Trusted connections I get this error. And I
> > need
> > > to
> > > > use trusted connections.
> > >
> > > Moments after I posted the last message, I found this link which may
be
> of
> > > value to you:
> > >
> > > How to troubleshoot connectivity issues in SQL Server 2000
> > > http://www.support.microsoft.com/?id=827422
> > >
> > > Steve
> > >
> > >
> >
> >
>|||No, it's accepting standard logins, it's just not accepting sa. I didn't
loose any Windows accounts.
All articles I saw say that it has something to do with impersonation, but I
even cannot change these settings - all my controls in Local security policy
are greyed out.
And SQL server doesn't take any domain accounts.
Thanks,
Peter
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:%23pXmGcUMEHA.3944@.tk2msftngp13.phx.gbl...
> Peter,
> Do you get the same error when logging in as 'sa'? If so, that is telling
> you that the server is not accepting standard SQL logins, no matter what
the
> settings seems to be.
> Do you have a domain account with sysadmin rights that you can login with?
> If so, try that one.
> During the upgrade of your server, did you lose any local Windows
accounts?
> Domain accounts? Look at article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;307002
> Russell Fields
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > Thank you, Steve.
> >
> > I'm working on it, buy now I even cannot get in with my administrative
> (sa)
> > account. I don't know what's wrong.
> >
> > Peter
> >
> > "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> > news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > >
> > > > I've just upgraded Windows 2000 server to Windows server 2003, and
> after
> > > > this I cannot get to the SQL server Enterprise manager, I'm getting
> > error
> > > > "Login failed for user '(null)'. Reason: Not associated with a
trusted
> > SQL
> > > > Server connection"
> > > >
> > > > I've found many articles about it, but they are all about problems
> with
> > > ASP
> > > > or ASP.Net. I don't have a problem with ASP.Net, my Intranet
> application
> > > is
> > > > running OK.
> > > >
> > > > I still can get in using SQL server connection if I change the
> > > registration
> > > > properties, but if I use Trusted connections I get this error. And I
> > need
> > > to
> > > > use trusted connections.
> > >
> > > Moments after I posted the last message, I found this link which may
be
> of
> > > value to you:
> > >
> > > How to troubleshoot connectivity issues in SQL Server 2000
> > > http://www.support.microsoft.com/?id=827422
> > >
> > > Steve
> > >
> > >
> >
> >
>|||Was there a change in servername ? Run "select @.@.servername " within QA .
Does this coincide with the actual servername ? If not, look at
sp_dropserver and sp_addserver
I have seen that message when my system is too busy ...and cannot accept any
more connections. Look at you SQL error log and see if theres anything worth
a note there.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:O9MIXfUMEHA.556@.TK2MSFTNGP10.phx.gbl...
> OK. The (null) probably suggests the comment in my other post. (Unless
> 'sa' is returning a similar message.)
> IF in the unlikely event that your registry is messed up:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;285097
> Russell Fields
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:uNK2oUUMEHA.3216@.TK2MSFTNGP12.phx.gbl...
> > Thank you, but it's configured this way.
> >
> > Peter
> >
> > "Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
> > news:O4mPpDUMEHA.624@.TK2MSFTNGP11.phx.gbl...
> > > Peter,
> > >
> > > CAUSE
> > > This error occurs because the SQL Server is configured to use "Windows
> > only"
> > > authentication.
> > > RESOLUTION
> > > On the SQL Server Security tab, configure SQL Server to use "SQL
Server
> > and
> > > Windows" authentication.
> > >
> > > Russell Fields
> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > > > Hello:
> > > >
> > > > I've just upgraded Windows 2000 server to Windows server 2003, and
> after
> > > > this I cannot get to the SQL server Enterprise manager, I'm getting
> > error
> > > > "Login failed for user '(null)'. Reason: Not associated with a
trusted
> > SQL
> > > > Server connection"
> > > >
> > > > I've found many articles about it, but they are all about problems
> with
> > > ASP
> > > > or ASP.Net. I don't have a problem with ASP.Net, my Intranet
> application
> > > is
> > > > running OK.
> > > >
> > > > I still can get in using SQL server connection if I change the
> > > registration
> > > > properties, but if I use Trusted connections I get this error. And I
> > need
> > > to
> > > > use trusted connections.
> > > >
> > > > I would appreciate any help very much.
> > > >
> > > > Thank you,
> > > >
> > > > --
> > > > Peter Afonin
> > > >
> > > >
> > >
> > >
> >
> >
>|||Hi Peter,
I actually just fix the same problem with out enviroment.
My questions are that:
1. Do you have novell client installed on your computer
2. Is your computer in any domains or just create new
domain
If so, bypass novell and just login windows domain or AD
firstly to see any changes. This is what I did to fix the
null login problem.
If you do not have novell. make sure you have a domain
login (Or just re create new login)and try again.
Good luck
Mike
>--Original Message--
>Was there a change in servername ? Run "select
@.@.servername " within QA .
>Does this coincide with the actual servername ? If not,
look at
>sp_dropserver and sp_addserver
>I have seen that message when my system is too
busy ...and cannot accept any
>more connections. Look at you SQL error log and see if
theres anything worth
>a note there.
>"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote
in message
>news:O9MIXfUMEHA.556@.TK2MSFTNGP10.phx.gbl...
>> OK. The (null) probably suggests the comment in my
other post. (Unless
>> 'sa' is returning a similar message.)
>> IF in the unlikely event that your registry is messed
up:
>> http://support.microsoft.com/default.aspx?scid=kb;en-
us;285097
>> Russell Fields
>> "Peter Afonin" <pva@.speakeasy.net> wrote in message
>> news:uNK2oUUMEHA.3216@.TK2MSFTNGP12.phx.gbl...
>> > Thank you, but it's configured this way.
>> >
>> > Peter
>> >
>> > "Russell Fields" <RussellFields@.NoMailPlease.Com>
wrote in message
>> > news:O4mPpDUMEHA.624@.TK2MSFTNGP11.phx.gbl...
>> > > Peter,
>> > >
>> > > CAUSE
>> > > This error occurs because the SQL Server is
configured to use "Windows
>> > only"
>> > > authentication.
>> > > RESOLUTION
>> > > On the SQL Server Security tab, configure SQL
Server to use "SQL
>Server
>> > and
>> > > Windows" authentication.
>> > >
>> > > Russell Fields
>> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
>> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
>> > > > Hello:
>> > > >
>> > > > I've just upgraded Windows 2000 server to
Windows server 2003, and
>> after
>> > > > this I cannot get to the SQL server Enterprise
manager, I'm getting
>> > error
>> > > > "Login failed for user '(null)'. Reason: Not
associated with a
>trusted
>> > SQL
>> > > > Server connection"
>> > > >
>> > > > I've found many articles about it, but they are
all about problems
>> with
>> > > ASP
>> > > > or ASP.Net. I don't have a problem with ASP.Net,
my Intranet
>> application
>> > > is
>> > > > running OK.
>> > > >
>> > > > I still can get in using SQL server connection
if I change the
>> > > registration
>> > > > properties, but if I use Trusted connections I
get this error. And I
>> > need
>> > > to
>> > > > use trusted connections.
>> > > >
>> > > > I would appreciate any help very much.
>> > > >
>> > > > Thank you,
>> > > >
>> > > > --
>> > > > Peter Afonin
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>
>.
>|||Thank you everyone for your help.
I finally had to open ticket with Microsoft. The problem was just like with
ASP - I had to add some accounts to "Impersonate users after authentication"
setting in the Local Security policy. It was mentioned in some articles, but
in Windows server 2003 the controls in my Local Security policy were
disbled, so I couldn't add anything. It took Microsoft some time to figure
out how to enable it.
So it's OK now.
Thanks again,
Peter
"Mike Y" <anonymous@.discussions.microsoft.com> wrote in message
news:7efa01c43182$f9fc5670$a001280a@.phx.gbl...
> Hi Peter,
> I actually just fix the same problem with out enviroment.
> My questions are that:
> 1. Do you have novell client installed on your computer
> 2. Is your computer in any domains or just create new
> domain
> If so, bypass novell and just login windows domain or AD
> firstly to see any changes. This is what I did to fix the
> null login problem.
> If you do not have novell. make sure you have a domain
> login (Or just re create new login)and try again.
> Good luck
> Mike
>
> >--Original Message--
> >Was there a change in servername ? Run "select
> @.@.servername " within QA .
> >Does this coincide with the actual servername ? If not,
> look at
> >sp_dropserver and sp_addserver
> >I have seen that message when my system is too
> busy ...and cannot accept any
> >more connections. Look at you SQL error log and see if
> theres anything worth
> >a note there.
> >
> >"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote
> in message
> >news:O9MIXfUMEHA.556@.TK2MSFTNGP10.phx.gbl...
> >> OK. The (null) probably suggests the comment in my
> other post. (Unless
> >> 'sa' is returning a similar message.)
> >>
> >> IF in the unlikely event that your registry is messed
> up:
> >> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;285097
> >>
> >> Russell Fields
> >> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> >> news:uNK2oUUMEHA.3216@.TK2MSFTNGP12.phx.gbl...
> >> > Thank you, but it's configured this way.
> >> >
> >> > Peter
> >> >
> >> > "Russell Fields" <RussellFields@.NoMailPlease.Com>
> wrote in message
> >> > news:O4mPpDUMEHA.624@.TK2MSFTNGP11.phx.gbl...
> >> > > Peter,
> >> > >
> >> > > CAUSE
> >> > > This error occurs because the SQL Server is
> configured to use "Windows
> >> > only"
> >> > > authentication.
> >> > > RESOLUTION
> >> > > On the SQL Server Security tab, configure SQL
> Server to use "SQL
> >Server
> >> > and
> >> > > Windows" authentication.
> >> > >
> >> > > Russell Fields
> >> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> >> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> >> > > > Hello:
> >> > > >
> >> > > > I've just upgraded Windows 2000 server to
> Windows server 2003, and
> >> after
> >> > > > this I cannot get to the SQL server Enterprise
> manager, I'm getting
> >> > error
> >> > > > "Login failed for user '(null)'. Reason: Not
> associated with a
> >trusted
> >> > SQL
> >> > > > Server connection"
> >> > > >
> >> > > > I've found many articles about it, but they are
> all about problems
> >> with
> >> > > ASP
> >> > > > or ASP.Net. I don't have a problem with ASP.Net,
> my Intranet
> >> application
> >> > > is
> >> > > > running OK.
> >> > > >
> >> > > > I still can get in using SQL server connection
> if I change the
> >> > > registration
> >> > > > properties, but if I use Trusted connections I
> get this error. And I
> >> > need
> >> > > to
> >> > > > use trusted connections.
> >> > > >
> >> > > > I would appreciate any help very much.
> >> > > >
> >> > > > Thank you,
> >> > > >
> >> > > > --
> >> > > > Peter Afonin
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >|||"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Hello:
> I've just upgraded Windows 2000 server to Windows server 2003, and after
> this I cannot get to the SQL server Enterprise manager, I'm getting error
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
null points to an anonymous user that tries to login. In a (default) Win2000
is anonymous login easily possible. In Win2003 not.
Another thing to look at, is your client configuration (see SQL menu). It
might be that you use the wrong protocol such as TCP/IP while it needs named
pipes.|||Thanks for posting the solution!
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:eFGjcYYMEHA.2628@.TK2MSFTNGP12.phx.gbl...
> Thank you everyone for your help.
> I finally had to open ticket with Microsoft. The problem was just like
with
> ASP - I had to add some accounts to "Impersonate users after
authentication"
> setting in the Local Security policy. It was mentioned in some articles,
but
> in Windows server 2003 the controls in my Local Security policy were
> disbled, so I couldn't add anything. It took Microsoft some time to figure
> out how to enable it.
> So it's OK now.
> Thanks again,
> Peter
> "Mike Y" <anonymous@.discussions.microsoft.com> wrote in message
> news:7efa01c43182$f9fc5670$a001280a@.phx.gbl...
> > Hi Peter,
> >
> > I actually just fix the same problem with out enviroment.
> > My questions are that:
> > 1. Do you have novell client installed on your computer
> > 2. Is your computer in any domains or just create new
> > domain
> > If so, bypass novell and just login windows domain or AD
> > firstly to see any changes. This is what I did to fix the
> > null login problem.
> > If you do not have novell. make sure you have a domain
> > login (Or just re create new login)and try again.
> > Good luck
> >
> > Mike
> >
> >
> > >--Original Message--
> > >Was there a change in servername ? Run "select
> > @.@.servername " within QA .
> > >Does this coincide with the actual servername ? If not,
> > look at
> > >sp_dropserver and sp_addserver
> > >I have seen that message when my system is too
> > busy ...and cannot accept any
> > >more connections. Look at you SQL error log and see if
> > theres anything worth
> > >a note there.
> > >
> > >"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote
> > in message
> > >news:O9MIXfUMEHA.556@.TK2MSFTNGP10.phx.gbl...
> > >> OK. The (null) probably suggests the comment in my
> > other post. (Unless
> > >> 'sa' is returning a similar message.)
> > >>
> > >> IF in the unlikely event that your registry is messed
> > up:
> > >> http://support.microsoft.com/default.aspx?scid=kb;en-
> > us;285097
> > >>
> > >> Russell Fields
> > >> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > >> news:uNK2oUUMEHA.3216@.TK2MSFTNGP12.phx.gbl...
> > >> > Thank you, but it's configured this way.
> > >> >
> > >> > Peter
> > >> >
> > >> > "Russell Fields" <RussellFields@.NoMailPlease.Com>
> > wrote in message
> > >> > news:O4mPpDUMEHA.624@.TK2MSFTNGP11.phx.gbl...
> > >> > > Peter,
> > >> > >
> > >> > > CAUSE
> > >> > > This error occurs because the SQL Server is
> > configured to use "Windows
> > >> > only"
> > >> > > authentication.
> > >> > > RESOLUTION
> > >> > > On the SQL Server Security tab, configure SQL
> > Server to use "SQL
> > >Server
> > >> > and
> > >> > > Windows" authentication.
> > >> > >
> > >> > > Russell Fields
> > >> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > >> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > >> > > > Hello:
> > >> > > >
> > >> > > > I've just upgraded Windows 2000 server to
> > Windows server 2003, and
> > >> after
> > >> > > > this I cannot get to the SQL server Enterprise
> > manager, I'm getting
> > >> > error
> > >> > > > "Login failed for user '(null)'. Reason: Not
> > associated with a
> > >trusted
> > >> > SQL
> > >> > > > Server connection"
> > >> > > >
> > >> > > > I've found many articles about it, but they are
> > all about problems
> > >> with
> > >> > > ASP
> > >> > > > or ASP.Net. I don't have a problem with ASP.Net,
> > my Intranet
> > >> application
> > >> > > is
> > >> > > > running OK.
> > >> > > >
> > >> > > > I still can get in using SQL server connection
> > if I change the
> > >> > > registration
> > >> > > > properties, but if I use Trusted connections I
> > get this error. And I
> > >> > need
> > >> > > to
> > >> > > > use trusted connections.
> > >> > > >
> > >> > > > I would appreciate any help very much.
> > >> > > >
> > >> > > > Thank you,
> > >> > > >
> > >> > > > --
> > >> > > > Peter Afonin
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> > >.
> > >
>|||Thank you.
You're correct, removing TCP/IP protocol solved the problem as well.
However, we needed TCP/IP for replication. Impersonation solved all
problems, and we could add TCP/IP back.
Peter
"Egbert Nierop (MVP for IIS)" <egbert_nierop@.nospam.invalid> wrote in
message news:ep7NeCaMEHA.340@.TK2MSFTNGP11.phx.gbl...
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > Hello:
> >
> > I've just upgraded Windows 2000 server to Windows server 2003, and after
> > this I cannot get to the SQL server Enterprise manager, I'm getting
error
> > "Login failed for user '(null)'. Reason: Not associated with a trusted
SQL
> > Server connection"
> null points to an anonymous user that tries to login. In a (default)
Win2000
> is anonymous login easily possible. In Win2003 not.
> Another thing to look at, is your client configuration (see SQL menu). It
> might be that you use the wrong protocol such as TCP/IP while it needs
named
> pipes.
>

Friday, March 30, 2012

Login failed for user NT AUTHORITY\NETWORK SERVICE.

Login failed for user NT AUTHORITY\NETWORK SERVICE.

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

Login failed for user NT AUTHORITY\NETWORK SERVICE

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Wednesday, March 28, 2012

Login failed for user NT AUTHORITY\ANONYMOUS LOGON

Login failed for user 'NT Authority\Anonymous

Login failed for user COLDFIRE/ASPNET

login failed for user ... Not Associated with a trusted SQL Server

login failed for user ... Not Associated with a trusted SQL Server

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

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

Monday, March 26, 2012

Login failed for user '(null)'...

Login failed for user '(null)'...

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect

Logging query errors

Blog Archive

About Me