Login failed for user '(null)'

Hi.

Im trying to make a couple of reports online for other people. My current setup is:

Machine A: SQL05 server.
Machine B: ReportingServer05 and IIS 5.0 (XP machine).
Machine C: Client trying to connect to Machine B and view a report. (Windows 2003)

On Machine B everything is working just fine, i can view my reports without any problems.
But if i try viewing a report on Machine C, I get the following error:

An error has occurred during report processing. (rsProcessingAborted) Get Online Help

Cannot create a connection to data source 'IntegrationDB'.

(rsErrorOpeningConnection) Get Online Help

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

Server connection.
But machine C kan browse http://machine-b/ReportServer and se the list of reports hosted, its when trying to generate the reports there is a problem. Im logged in on machine C with the same user as on Machine B.

My Shared Data Source in this VS05 project is setup to be using Integrated Security, so the "user '(null)'" part looks like Machine C dosnt supply the username, but why?

What is it that im missing in my configuration?
And any addional information needed?

Best Regards.
Lasse Stig Thomsen

---

You are running into a double-hop issue. Make sure Kerberos is enabled and configured correctly (the "real" solution").

Another thing you might try (not really a fix, but avoiding the problem) is to hard-code the credentials in your data source versus using Windows Integration.

|||Hi thanks for the answer. It worked like a charm with both solutions.

thanks gain.

Login failed for user '(null)'

Hi.

Im trying to make a couple of reports online for other people. My current setup is:

Machine A: SQL05 server.
Machine B: ReportingServer05 and IIS 5.0 (XP machine).
Machine C: Client trying to connect to Machine B and view a report. (Windows 2003)

On Machine B everything is working just fine, i can view my reports without any problems.
But if i try viewing a report on Machine C, I get the following error:

An error has occurred during report processing. (rsProcessingAborted) Get Online Help Cannot create a connection to data source 'IntegrationDB'. (rsErrorOpeningConnection) Get Online Help Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
But machine C kan browse http://machine-b/ReportServer and se the list of reports hosted, its when trying to generate the reports there is a problem. Im logged in on machine C with the same user as on Machine B.

My Shared Data Source in this VS05 project is setup to be using Integrated Security, so the "user '(null)'" part looks like Machine C dosnt supply the username, but why?

What is it that im missing in my configuration?
And any addional information needed?

Best Regards.
Lasse Stig Thomsen

---

You are running into a double-hop issue. Make sure Kerberos is enabled and configured correctly (the "real" solution").

Another thing you might try (not really a fix, but avoiding the problem) is to hard-code the credentials in your data source versus using Windows Integration.

|||Hi thanks for the answer. It worked like a charm with both solutions.

thanks gain.

Login Authentication for Standard Accounts

We have a couple of vendor applications that create standard accounts.
These accounts have the same format as our domain accounts. For
example, my Windows account would be <domain>\<user_name>. The SQL
standard account would be <user_name>.
What we would like to do is change the login process to validate
against active directory either prior to or instead of checking the
SQL password. Everything else could remain the same.
This would be on SQL 2000 or SQL 2005. Any suggestions or other
insight would be appreciated.RogerT (roger.tompkins@.gmail.com) writes:
> We have a couple of vendor applications that create standard accounts.
> These accounts have the same format as our domain accounts. For
> example, my Windows account would be <domain>\<user_name>. The SQL
> standard account would be <user_name>.
> What we would like to do is change the login process to validate
> against active directory either prior to or instead of checking the
> SQL password. Everything else could remain the same.
> This would be on SQL 2000 or SQL 2005. Any suggestions or other
> insight would be appreciated.
I'm not really sure what you mean here. SQL Server provides to
means of authentication: SQL authentication and Windows authentication.
It sounds from your description that the vendor accounts are for
SQL authentication. But you cannot change a login from being an SQL
login, to be a Windows login. These two types of logins are competely
unconnected.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx