Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Reporting Services / July 2008

Tip: Looking for answers? Try searching our database.

Report request works, then doesn't work

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Admin - 30 Jun 2008 06:56 GMT
I am running multiple instances of SQL2005 EE on the one Windows 2003
DataCenter edition

I developed a report in the DEV instance and it worked fine.
I changed the deployment server in the Visual Studio project to point to the
TEST instance and deployed the report again

I  have a couple of groups set up tha are used to grant permissions to the
webserver hosting the report service and permisions in the database.  There
is one set for DEV and one set for TEST.

A created a user specific for testing and put the use in the appropriate
groups for TEST.  When I visit the server$test/reports website, I can go
ahead and request the report - I get prompted for the parameters for the
query (it does a 'SELECT * from table where year = @yr")  I get the
following error message in the reportservices log.

---------------------------------------------------
w3wp!processing!e!6/30/2008-13:44:34:: e ERROR: Data source 'AData': An
error has occurred. Details:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'AData'. --->
System.Data.SqlClient.SqlException: Login failed for user 'CORE\bob'.
w3wp!processing!e!6/30/2008-13:44:34:: e ERROR: An exception has occurred in
data source 'AData'. Details:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'AData'. --->
System.Data.SqlClient.SqlException: Login failed for user 'CORE\bob'.
w3wp!processing!e!6/30/2008-13:44:34:: i INFO: Merge abort handler called
for ID=-1. Aborting data sources ...
w3wp!processing!e!6/30/2008-13:44:35:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing. --->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'AData'. --->
System.Data.SqlClient.SqlException: Login failed for user 'CORE\bob'.
  --- End of inner exception stack trace ---
-------------------------------------------------------------
But when I add the user account to the DEV groups and re-run the  report
from the  TEST website - I get the expected pretty pictures in the report.

I have been through the Active Directory Groups, the permissions in SQL over
and over and can't see where the DEV groups have been used to grant
permissions in the TEST environment.

Any ideas where I should be looking for these permissions?

Thanks Heaps

Bob
Admin - 02 Jul 2008 07:24 GMT
I found the problem
The report was using a different dataset other than the shared dataset
I updated the connection string in the alternate dataset and now it runs
without errors

>I am running multiple instances of SQL2005 EE on the one Windows 2003
>DataCenter edition
[quoted text clipped - 49 lines]
>
> Bob
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.