Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Users in remote building (On the same VLAN? Not sure of network specifics)
can connect to the sql server in the remote building with no issues. In my
building (HQ), we were able to connect to it until this morning. Last night
the domain controller in the remote building was upgraded to Windows 2003. I
know of no other changes to this environment. I am able to use a remote
management tool (dameware) and log on locally to this sql server and then
connect. If I add a named pipes alias in my client network utility for this
server I can then connect remotely. I'm worried that the problem was caused
by the domain controller upgrade and there are several more of these
scheduled in other buildings. The one that we're having trouble with right
now is very insignificant. Should these results be repeated with subsequent
domain controller upgrades, our entire company could be affected. I can't
seem to get the right information to the domain controller folks to prove
that the cause of this issue was the upgrade nor am I really sure that this
IS the cause. The sql server is listening on port 1433 (tested using
telnet). I can ping it and access the host in every other way from here -
just can't use anything to connect to the sql server.
Thanks for your help!
Michelle
There was a kerberos service on the domain controller that was not started.
Starting this service resolved the issue. I believe that there is a KB
article on this but unfortunately, I was unable to locate it myself.
"michelle" <michelle@.nospam.com> wrote in message
news:eCqv6ohDFHA.628@.TK2MSFTNGP15.phx.gbl...
> Users in remote building (On the same VLAN? Not sure of network specifics)
> can connect to the sql server in the remote building with no issues. In my
> building (HQ), we were able to connect to it until this morning. Last
night
> the domain controller in the remote building was upgraded to Windows 2003.
I
> know of no other changes to this environment. I am able to use a remote
> management tool (dameware) and log on locally to this sql server and then
> connect. If I add a named pipes alias in my client network utility for
this
> server I can then connect remotely. I'm worried that the problem was
caused
> by the domain controller upgrade and there are several more of these
> scheduled in other buildings. The one that we're having trouble with right
> now is very insignificant. Should these results be repeated with
subsequent
> domain controller upgrades, our entire company could be affected. I can't
> seem to get the right information to the domain controller folks to prove
> that the cause of this issue was the upgrade nor am I really sure that
this
> IS the cause. The sql server is listening on port 1433 (tested using
> telnet). I can ping it and access the host in every other way from here -
> just can't use anything to connect to the sql server.
> Thanks for your help!
> Michelle
>

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Users in remote building (On the same VLAN? Not sure of network specifics)
can connect to the sql server in the remote building with no issues. In my
building (HQ), we were able to connect to it until this morning. Last night
the domain controller in the remote building was upgraded to Windows 2003. I
know of no other changes to this environment. I am able to use a remote
management tool (dameware) and log on locally to this sql server and then
connect. If I add a named pipes alias in my client network utility for this
server I can then connect remotely. I'm worried that the problem was caused
by the domain controller upgrade and there are several more of these
scheduled in other buildings. The one that we're having trouble with right
now is very insignificant. Should these results be repeated with subsequent
domain controller upgrades, our entire company could be affected. I can't
seem to get the right information to the domain controller folks to prove
that the cause of this issue was the upgrade nor am I really sure that this
IS the cause. The sql server is listening on port 1433 (tested using
telnet). I can ping it and access the host in every other way from here -
just can't use anything to connect to the sql server.
Thanks for your help!
MichelleThere was a kerberos service on the domain controller that was not started.
Starting this service resolved the issue. I believe that there is a KB
article on this but unfortunately, I was unable to locate it myself.
"michelle" <michelle@.nospam.com> wrote in message
news:eCqv6ohDFHA.628@.TK2MSFTNGP15.phx.gbl...
> Users in remote building (On the same VLAN? Not sure of network specifics)
> can connect to the sql server in the remote building with no issues. In my
> building (HQ), we were able to connect to it until this morning. Last
night
> the domain controller in the remote building was upgraded to Windows 2003.
I
> know of no other changes to this environment. I am able to use a remote
> management tool (dameware) and log on locally to this sql server and then
> connect. If I add a named pipes alias in my client network utility for
this
> server I can then connect remotely. I'm worried that the problem was
caused
> by the domain controller upgrade and there are several more of these
> scheduled in other buildings. The one that we're having trouble with right
> now is very insignificant. Should these results be repeated with
subsequent
> domain controller upgrades, our entire company could be affected. I can't
> seem to get the right information to the domain controller folks to prove
> that the cause of this issue was the upgrade nor am I really sure that
this
> IS the cause. The sql server is listening on port 1433 (tested using
> telnet). I can ping it and access the host in every other way from here -
> just can't use anything to connect to the sql server.
> Thanks for your help!
> Michelle
>

Login failed for user <null>

Hello,
I have RS (client and server components) installed on a test machine
(Win2k), with the SQL-Server database on a remote machine. I'm able to create
reports, preview them with data, and deploy them with no issues. However,
when I try to execute any of them from the Report Manager, I get: "Login
failed for user '(null)'. Reason: Not associated with a trusted SQL Server
connection".
The connection object is set up in the Report Manager as a shared data
source, with the credentials stored in the report server, the credentials I'm
using have access to the database, and I have the "Use as windows credentials
when connecting to the datasource" check box checked (the database uses
Windows authentication).
Between all of the logins/security settings in use by IIS, the Windows
Services, the database, aspnet, etc. I'm at a loss as to where the issue
might lie. Any thoughts?
Thanks in advance!
BrianI had similar problems as recently as last week.
Are the SQL Server box and the RS box in the same domain ?
My setup is similar to yours but on Win2003 on both sides. and problem
was due to i dint have them in the same domain.
So i created an SQL Account with admin credentials and then
Checked the "use windows and SQL Auth" in the SQL server and configured
RS to use SQL credentials.
this is NOT the most secure solution, but i am able to move forward.
Hope this helps
Bofo|||Yes, both computers are on the same domain. The strange thing is, when I
change the data source properties (from within Report Manager) to 'Windows NT
Integrated Authority' everything runs fine...unfortunately it doesn't seem
that you can create subscriptions to reports unless you're saving the
credentials.
Doesn't seem like it should be this difficult :)
"Win2003InstallIssues" wrote:
> I had similar problems as recently as last week.
> Are the SQL Server box and the RS box in the same domain ?
> My setup is similar to yours but on Win2003 on both sides. and problem
> was due to i dint have them in the same domain.
> So i created an SQL Account with admin credentials and then
> Checked the "use windows and SQL Auth" in the SQL server and configured
> RS to use SQL credentials.
> this is NOT the most secure solution, but i am able to move forward.
> Hope this helps
> Bofo
>|||I think you found it out by trial and error, though just FYI, stored
credentials are required if you want to support subscriptions.
--
Adrian M.
MCP
"bmcelhany" <bmcelhany@.discussions.microsoft.com> wrote in message
news:E2B8822B-8437-4E7C-878A-0D0A8A011EFD@.microsoft.com...
> Yes, both computers are on the same domain. The strange thing is, when I
> change the data source properties (from within Report Manager) to 'Windows
> NT
> Integrated Authority' everything runs fine...unfortunately it doesn't seem
> that you can create subscriptions to reports unless you're saving the
> credentials.
> Doesn't seem like it should be this difficult :)
> "Win2003InstallIssues" wrote:
>> I had similar problems as recently as last week.
>> Are the SQL Server box and the RS box in the same domain ?
>> My setup is similar to yours but on Win2003 on both sides. and problem
>> was due to i dint have them in the same domain.
>> So i created an SQL Account with admin credentials and then
>> Checked the "use windows and SQL Auth" in the SQL server and configured
>> RS to use SQL credentials.
>> this is NOT the most secure solution, but i am able to move forward.
>> Hope this helps
>> Bofo
>>|||If you are connecting to Report Manager using Win Auth, and the data source
connects to the remote DB using Win Auth, you may need to enable Kerberos.
Depending on how your domain is configured, Windows credentials can be
passed across one computer connection before they expire. A user connection
to a report server counts as the first connection. If the user opens a
report that retrieves data from a remote server, that login counts as a
second connection and will fail if you are using Windows Authentication and
Kerberos is not enabled.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_datasources_v1_87e9.asp
--
Adrian M.
MCP
"bmcelhany" <bmcelhany@.discussions.microsoft.com> wrote in message
news:717CD26C-F4E2-426B-80E7-4E2CB99CA11E@.microsoft.com...
> Hello,
> I have RS (client and server components) installed on a test machine
> (Win2k), with the SQL-Server database on a remote machine. I'm able to
> create
> reports, preview them with data, and deploy them with no issues. However,
> when I try to execute any of them from the Report Manager, I get: "Login
> failed for user '(null)'. Reason: Not associated with a trusted SQL Server
> connection".
> The connection object is set up in the Report Manager as a shared data
> source, with the credentials stored in the report server, the credentials
> I'm
> using have access to the database, and I have the "Use as windows
> credentials
> when connecting to the datasource" check box checked (the database uses
> Windows authentication).
> Between all of the logins/security settings in use by IIS, the Windows
> Services, the database, aspnet, etc. I'm at a loss as to where the issue
> might lie. Any thoughts?
> Thanks in advance!
> Brian|||Right, I definitely need to support schedules/subscriptions, so stored
credentials are my only option...unfortunately I can only get the reports to
work using Windows NT Integrated Security. Here are the various data source
settings I've tried:
Assumptions: all RS components are installed on one machine (no SQL Server)
with the database on another machine within the same domain. The SQL Server
uses Windows authentication. Both the 'Reports' and the 'ReportServer'
virtual directories are using anonymous authentication.
1) Windows NT Integrated Security: the reports run perfectly, however I am
unable to schedule any of them.
2) Credentials stored in the report server: I get a "login failed for user
'bmcelhany'. Reason: not associated with a trusted SQL Server connection"
error.
3) Credentials stored in the report server with the "Use as Windows
credentials when connecting to the data source" check box checked: I get a
"login failed for user 'null'. Reason: not associated with a trusted SQL
Server conenction" error.
Any thoughts?
"Adrian M." wrote:
> I think you found it out by trial and error, though just FYI, stored
> credentials are required if you want to support subscriptions.
> --
> Adrian M.
> MCP
> "bmcelhany" <bmcelhany@.discussions.microsoft.com> wrote in message
> news:E2B8822B-8437-4E7C-878A-0D0A8A011EFD@.microsoft.com...
> > Yes, both computers are on the same domain. The strange thing is, when I
> > change the data source properties (from within Report Manager) to 'Windows
> > NT
> > Integrated Authority' everything runs fine...unfortunately it doesn't seem
> > that you can create subscriptions to reports unless you're saving the
> > credentials.
> >
> > Doesn't seem like it should be this difficult :)
> >
> > "Win2003InstallIssues" wrote:
> >
> >> I had similar problems as recently as last week.
> >>
> >> Are the SQL Server box and the RS box in the same domain ?
> >>
> >> My setup is similar to yours but on Win2003 on both sides. and problem
> >> was due to i dint have them in the same domain.
> >>
> >> So i created an SQL Account with admin credentials and then
> >> Checked the "use windows and SQL Auth" in the SQL server and configured
> >> RS to use SQL credentials.
> >>
> >> this is NOT the most secure solution, but i am able to move forward.
> >> Hope this helps
> >> Bofo
> >>
> >>
>
>|||Have you tried the userid-pw login from the Visual Studio IDE? Also - the
obvious question - is mixed mode security enabled on SQL Server?
"bmcelhany" <bmcelhany@.discussions.microsoft.com> wrote in message
news:8D8CB6D4-8FE2-4E03-99AD-BFAFAB4B9B98@.microsoft.com...
> Right, I definitely need to support schedules/subscriptions, so stored
> credentials are my only option...unfortunately I can only get the reports
to
> work using Windows NT Integrated Security. Here are the various data
source
> settings I've tried:
> Assumptions: all RS components are installed on one machine (no SQL
Server)
> with the database on another machine within the same domain. The SQL
Server
> uses Windows authentication. Both the 'Reports' and the 'ReportServer'
> virtual directories are using anonymous authentication.
> 1) Windows NT Integrated Security: the reports run perfectly, however I am
> unable to schedule any of them.
> 2) Credentials stored in the report server: I get a "login failed for user
> 'bmcelhany'. Reason: not associated with a trusted SQL Server connection"
> error.
> 3) Credentials stored in the report server with the "Use as Windows
> credentials when connecting to the data source" check box checked: I get a
> "login failed for user 'null'. Reason: not associated with a trusted SQL
> Server conenction" error.
> Any thoughts?
> "Adrian M." wrote:
> > I think you found it out by trial and error, though just FYI, stored
> > credentials are required if you want to support subscriptions.
> >
> > --
> > Adrian M.
> > MCP
> >
> > "bmcelhany" <bmcelhany@.discussions.microsoft.com> wrote in message
> > news:E2B8822B-8437-4E7C-878A-0D0A8A011EFD@.microsoft.com...
> > > Yes, both computers are on the same domain. The strange thing is, when
I
> > > change the data source properties (from within Report Manager) to
'Windows
> > > NT
> > > Integrated Authority' everything runs fine...unfortunately it doesn't
seem
> > > that you can create subscriptions to reports unless you're saving the
> > > credentials.
> > >
> > > Doesn't seem like it should be this difficult :)
> > >
> > > "Win2003InstallIssues" wrote:
> > >
> > >> I had similar problems as recently as last week.
> > >>
> > >> Are the SQL Server box and the RS box in the same domain ?
> > >>
> > >> My setup is similar to yours but on Win2003 on both sides. and
problem
> > >> was due to i dint have them in the same domain.
> > >>
> > >> So i created an SQL Account with admin credentials and then
> > >> Checked the "use windows and SQL Auth" in the SQL server and
configured
> > >> RS to use SQL credentials.
> > >>
> > >> this is NOT the most secure solution, but i am able to move forward.
> > >> Hope this helps
> > >> Bofo
> > >>
> > >>
> >
> >
> >

Login failed for sql authentication

I've developed an ASP2 application. Locally, everything was fine. However, when I deployed it on a remote server. I got this error:

Login failed for user 'domain\userx'.

My connection string is:

connectionString="Data Source=ServerName;Initial Catalog=Aspect;User Id =domain\userx;Password = abc"

I'm quite sure that connection string is fine. I need to mention that whenever I try to connect to the remote server from my client by the Sql authentication, I get the message that login failed for this user. But when I try to connect by windows authentication, it works and there is no error.

I asked the administrator, and he told me that Sql Server authentication is in mixed mode.

So, I really can't figure out what is the problem

From your connection string I found you're trying to explicitly specify a Windows account, which seems to connect with Windows Authentication rather than SQL Authentication. To learn more about Authentication Mode in SQL, please take a look at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp

You can 2 options when connect to SQL, either to specify a SQL account and password; or use WindowsAuthentication by setIntegrated Security to SSPI (true). So if you want to connect with Windows Authentication, firstly you have to add the Windows Account to the SQL logins and grant proper permission to it. More information about creating SQL Logins can be found at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/moddev/html/dehowcreatingsqlserverusers.asp

then write your connection string as following:

connectionString="Data Source=ServerName;Initial Catalog=Aspect; Integrated Security =SSPI;";

This website provides various connection strings:

http://www.connectionstrings.com

|||

Thanks lori_jay

You're right. that was my mistake

However, when I tried to connect with connection string same as you wrote, I got this error "Login failed for user null'. But. I could connect to my DB by using client tools and with windows authentication.

So, the problem occurs when I try to connect through my web application.

Do you have any suggestion ?

|||

Also I have another question.

If I use windows authentication in my connection string. Does everyone in the domain who succesfully logined, have access ?

Thanks.

|||

bkpazand:

However, when I tried to connect with connection string same as you wrote, I got this error "Login failed for user null'. But. I could connect to my DB by using client tools and with windows authentication.

Then is your application deployed under IIS? It seems that other account has been used to connect to SQL. So please make sure you perform proper impersonation when connect under IIS. You can take a look at this post:

http://forums.asp.net/thread/1294820.aspx

And you can also find much information about impersonation on MSDN.

bkpazand:

If I use windows authentication in my connection string. Does everyone in the domain who succesfully logined, have access ?

No. If you want to allow other users in the same domain to connect the SQL Server, you can add the users or usergroup to the local Administrators group of the SQL machine. That's because SQL has a built-in login 'BULITIN\Administrators', all memebers for local admin will be mapped to this login when connect to SQL with Windows Authentication.

Login failed for give user id

I tried to create a mining model from a remote SQL 2000 database using local user id of remote server. Whenver I try to process the model I am getting login failed error. But the same model runs fine when I configure datasource using windows credentials.I found out the reason, when I set the impersonation mode to service account/degfault its working. But when I set to specific user name and password, its not working. Can somebody suggest me the possible cause.|||I found answer myself. I just created a local user and a role in analysis service database mapping to local user and granted him appropriate rights. Now I can process the data model under "impersonate particular user mode"

login failed error

I am trying to export data from one sql server instance to another on another domain.
however trying to connect to the remote instance never works due to 'login failed' error.
i have access to the remote domain and can verify that the login is correct.
what is the problem?
--
Message posted via http://www.sqlmonster.comCan you be a little more specific as to exactly how you are attempting this?
Are you using DTS, a remote query or what? How are you connecting and what
is the connection string?
--
Andrew J. Kelly SQL MVP
"Mark Evans via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:94ee95ffac054cb6af4c94330d544b85@.SQLMonster.com...
>I am trying to export data from one sql server instance to another on
>another domain.
> however trying to connect to the remote instance never works due to 'login
> failed' error.
> i have access to the remote domain and can verify that the login is
> correct.
> what is the problem?
> --
> Message posted via http://www.sqlmonster.com

login failed error

I am trying to export data from one sql server instance to another on anothe
r domain.
however trying to connect to the remote instance never works due to 'login f
ailed' error.
i have access to the remote domain and can verify that the login is correct.
what is the problem?
Message posted via http://www.droptable.comCan you be a little more specific as to exactly how you are attempting this?
Are you using DTS, a remote query or what? How are you connecting and what
is the connection string?
Andrew J. Kelly SQL MVP
"Mark Evans via droptable.com" <forum@.droptable.com> wrote in message
news:94ee95ffac054cb6af4c94330d544b85@.SQ
droptable.com...
>I am trying to export data from one sql server instance to another on
>another domain.
> however trying to connect to the remote instance never works due to 'login
> failed' error.
> i have access to the remote domain and can verify that the login is
> correct.
> what is the problem?
> --
> Message posted via http://www.droptable.com

login failed error

I am trying to export data from one sql server instance to another on another domain.
however trying to connect to the remote instance never works due to 'login failed' error.
i have access to the remote domain and can verify that the login is correct.
what is the problem?
Message posted via http://www.sqlmonster.com
Can you be a little more specific as to exactly how you are attempting this?
Are you using DTS, a remote query or what? How are you connecting and what
is the connection string?
Andrew J. Kelly SQL MVP
"Mark Evans via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:94ee95ffac054cb6af4c94330d544b85@.SQLMonster.c om...
>I am trying to export data from one sql server instance to another on
>another domain.
> however trying to connect to the remote instance never works due to 'login
> failed' error.
> i have access to the remote domain and can verify that the login is
> correct.
> what is the problem?
> --
> Message posted via http://www.sqlmonster.com