October 2, 2008 at 2:04 pm
I have a problem similar to this
http://www.sqlservercentral.com/Forums/Topic283472-150-1.aspx
I've developed a report with a shared dataset from a stored SQL 2005 procedure with a single parameter. It runs just fine for me in my BIDS development environment. If I deploy it to my report server my users get an rsErrorExecutingCommand error. They can see images in other reports stored directly on the report server but they cant query the my databases via a SSRS dataset.
I've read deeply on the error and made sure my users are in the db_dataReader role in the database as well as granted execute permissions for them to run the SP.
How can I get them to run the report? Do I need to grant permission for my SSRS service account in the database?
Many thanks ahead of time
jhh
October 2, 2008 at 7:01 pm
Have you attempted the fix that is suggested in the thread you reference? I think you can get around it by storing the credentials in the ReportServer database.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
October 2, 2008 at 8:10 pm
Thanks Jack, I think I have.
My users are in the db_dataReader role.
I certainly wont put them in the sysAdmin role.
I'll try putting the credentials directly in the report server db tomorrow.
I may not be able to however because that db resides on the default instance of the server.
I have access to only a named instance under the default instance.
jhh
October 14, 2008 at 9:35 am
I have similar issues. Keep getting the following error when I run the report in report manager. I have changed to use a SQL login with db_datareader and sysadmin rights but still getting the error. Can you advise on how to put the credentials directly in the report server? Thanks!
Logon failed.
Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)
October 14, 2008 at 9:42 am
My problem seems to have has solved itself.
Actually I termporarily placed my users in the dbo role and proved to myself that they could run the report off the reports server.
Then I changed them back to their normal role with db_read permissions and viola! all seems to be working fine
give the temporary switch a try
jhh
October 14, 2008 at 9:59 am
My issues maybe more complicated than yours as I cannot even open the reports myself. I have full admin rights to the db. When I look in the security log on the web server where the reporting services is installed, there's a failed login error -
The user has not been granted the requested logon type at this machine.
What logon type does this user needs? What rights does your execution account has on the web server? Thanks!
October 14, 2008 at 11:36 am
Fixed my issue. I have to use a User account for the execution account and use SQL Login for all my reports connections.
January 8, 2014 at 2:14 pm
When using the Test Connection function using a service account's credentials, SSRS does not act as a service, rather as a batch. This is why the authentication is failing and you are getting the error "Log on failed. Ensure the user name and password are correct". To fix this, edit the Local Security Policy of the SSRS box and add that service account to "log on as a batch job"
Cheers
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply