Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSRS : Cannot create a connection to data source .(rsErrorOpeningConnection) Expand / Collapse
Author
Message
Posted Thursday, February 4, 2010 4:42 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 5, 2013 8:47 AM
Points: 2, Visits: 74
Hi,

I'm Belgian, so I'm sorry if my English is not very good.

I'm working with a windows server 2003,SQL SERVER 2005 and Reporting Services.
The SQL Server is on my local computer and the Reporting Services Server is on another computer.
When I test my reports on the local computer there is no error.
But when I'm deploying them on the new Reporting Services Server (on another computer) .

I receive this error message :
"An error has occurred during report processing. (rsProcessingAborted).
Cannot create a connection to data source .(rsErrorOpeningConnection)
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. "

The error occur when I use the "windows authentication" with my connection string.
If I use the "SQL Server authentication" withe User Name and Password.I don't have the error message.

I've found some people talking about a "double HOP" problem.
But I'm not an expert in Security or in Network Connection problems.

Is that someone already had the same error?

Thanks,

Richard
Post #859514
Posted Thursday, February 4, 2010 4:56 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, February 19, 2013 2:02 AM
Points: 846, Visits: 303
Richard,

I'm Belgian too but as you know that is still no guarantee for easy communication

If you use Google, you'll find lots of information on the double hop issue, e.g. in this article.

Basically, what it means for you is that the SQL Server database cannot give you access based on the the domain\username it receives, the reason being that for security reasons IIS is not allowed to pass them on.

You either have to change your configuration (or talk to your system engineer) or stick with SQL Server authentication. This is in general considered less secure but nonetheless often used (to overcome problems like yours).

Or try this article.


Regards,

Willem
http://wschampheleer.wordpress.com
Post #859518
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse