Wrox Programmer Forums
|
BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7
This is the forum to discuss the Wrox book Professional SQL ServerReporting Services by Paul Turley, Todd Bryant, James Counihan, George McKee, Dave DuVarney; ISBN: 9780764568787
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 22nd, 2006, 07:22 AM
Registered User
 
Join Date: Jul 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default rsErrorOpeningConnection

Hi,
I really really need some help with the problem below. I am having problems trying to run reports from a VB.Net application. The problem is as follows:

SQL Server 2005, SQL Server Reporting Services and the VB .NET application called ‘risk-op’ are on a server.

A user tries to access the application from a remote computer. The application is displayed and the user is able to do everything. However when the user tries to click ‘Go’ for one of the reports the following error is displayed:


An error has occurred during processing (rsProcessingAborted)
Cannot create a connection to data source ‘risk-op’ (rsErrorOpeningConnection)

This error occurs because the user is not a user on the SQL server database. However if I add the user to the database the user is able to then view the report.

The reason for this is because reporting services is configured to use windows authentication as shown below. As a result when the user presses ‘Go’ to view a report, reporting services tries to connect to the database using windows authentication and if that user is not setup as a user on the database the user is then not able to view the report.

I need to get around this problem. I don’t want to have to manually add users to the database every time (that maintenance for a couple of hundred people would be a disaster!)

I believe that a way around this would be to use ‘Credentials stored securely in the report server’ in SQL Server Reporting Services. Is this the way to do it and if so, where do I add these credentials to the report server?

I came across an article that said “Credentials are stored in reversible encryption in the report server database. You can specify one set of stored credentials for each data source used in a report. The credentials you provide retrieve the same data for every user who runs the report.”

How do I add these credentials and is this the answer to my problem?

Do I have to change something in the RSreportserver.config file?
Any help would be much appreciated, thanks!
Ian













Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.