Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Peace2007
Posting Yak Master
239 Posts |
 Posted - 2009-01-13 : 04:01:13
|
| Hi, I've created a report using SQL2005 reporting services then I deployed it on a server. The reporting service configurations is okay and when I browse to the link of the reports locally it works ok. But when I try to browse to it from another PC, it prompts for UserID/Password or displays following error: The permissions granted to user 'bla bla' are insufficient for performing this operation. (rsAccessDenied)I've searched for it through internet and tried all recommendations, which none of them worked. This is the 2nd time I'm facing this problem. The first time I couldn't resolve it and tried it on another server and it worked fine. Now, I can neither change the server nor reinstall SQLserver on it cause it's the main server on our company and the only one, which is available through internet (IT manager doesn't let me do so) I wonder if there's any solution to this problem Any idea is appreciated |
|
|
Peter Cwik
Starting Member
12 Posts |
Posted - 2009-01-13 : 09:42:07
|
| The issue is pretty simple. The report you have written is accessing data in a database. The report must have rights to access that data, just as a user issuing a select would need rights to do the same. When YOU attempt to run the report from your machine, you are logged on as yourself and your credentials are passed to the SQL Server where YOU have rights to see the data. When you try it from a different machine, I assume that you are not logged on as yourself, but as another user who does not have rights to see the data.So you have two options:1)Give everyone (who needs it) access to the data from the SQL Side.2)Change the Credentials on the report to use stored credentials. To do this view the report then go to properties, then data sources and scroll down to stored credentials and type in a SQL Server username and password. This will be the account that has access to the data.Hope this helps.Pete |
 |
|
|
Peace2007
Posting Yak Master
239 Posts |
Posted - 2009-01-14 : 00:39:23
|
| Thanks a lot pete for your reply I'd given everyone access to the data but the problem still exists. However we have only windows authentication in SQLserver. By the way, I resolved my problem by calling the report through an ASP. NET web application. |
|
|
|
|
|
|
The permissions granted to user are insufficient