When I run a report in Report Manager I get the following error: An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'ds_productivity'. (rsErrorExecutingCommand) Access to the remote server is denied because the current security context is not trusted. An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'ds_productivity'. (rsErrorExecutingCommand) Access to the remote server is denied because the current security context is not trusted. An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'ds_productivity'. (rsErrorExecutingCommand) Access to the remote server is denied because the current security context is not trusted. "An error has occurred during report processing. (rsProcessingAborted) query execution failed for dataset 'ds_productivity'.(rsErrorExecutiingCommand) Access to the remote server is denied because the current security context is not trusted" As initially written the stored procedure did use a linked server and the report executed.I made a small change to the report not involving the linked server and got the above error.REMOVED all linked server queries from the stored procedure and I still get the error. Suggestions would be greatly appreciated. I have narrowed the issue down. I am using a cursor to update a local temp table and when I do an insert to the temptable is apparently when I get the error. Also please note it works fine in both Development Studio and when I run the procedure in Management Studion

Hey, http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/4338a002-0ea3-41db-a17a-20486766d654 Hope this will help you !!! Sanjeewan

Hi Poolside, http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/9fede32d-476c-4ba8-9e20-56971e9de205 Thanks, Khilit http://www.bigator.com

No remote server.

hi there, Can you please check "Services.msc" -> under which account the SQL Server Reporting Services are running. Also check that account has access to your database on what the dataset is executing to retrieve data ?? We need to check all layers like : When you invoke report from ReportManager -> what is that account (credentials who started this request) -> Reporting Services -> Database etc.. Can you also check if this report is successfully executing from visual studio (BIDS) -> so we can filter out where the access has failed to execute the dataset?? Can you also check the ReportManager -> (your report's) datasource connection string configuration -> what type of connectivity its using ? stored credential in server / windows etc ... ? so i can visualize the scenario better way. Thanks, Khilit http://www.bigator.com

Can you please check "Services.msc" -> under which account the SQL Server Reporting Services are running. Also check that account has access to your database on what the dataset is executing to retrieve data ?? I am not sure what you are asking me to do? We need to check all layers like : When you invoke report from ReportManager -> what is that account (credentials who started this request) -> Reporting Services -> Database etc.. Again I don't quite understand Can you also check if this report is successfully executing from visual studio (BIDS) -> so we can filter out where the access has failed to execute the dataset?? Yes it runs fine from BIDS Can you also check the ReportManager -> (your report's) datasource connection string configuration -> what type of connectivity its using ? stored credential in server / windows etc ... ? so i can visualize the scenario better way. I am thinking this is the crux of the issue. When I change the datasource in Report Manager to prompt for password all runs well including linked server. When I have the report run under a saved login and password but impersonating the windows credentials (same info used as when prompted) I get the error.

Hi Poolside, Can you please try setting up your DataSource configuration in ReportManager as mentioned here: http://www.bigator.com/2012/06/21/ssrs-report-is-asking-for-username-and-password-while-executing/ Because i am thinking that with your credentials if the report is executing fine then this idea will work. Thanks, Khilit http://www.bigator.com

That is not my problem. The password used for executing the report never expires and as long as I don't ask Report Server to impersonate windows security all runs fine.

Hello Poolside, Thank you to post your question on TechNet. I want to check whether you are using the Kerberos authentication on your reporting service. If so, it is possible that the SPN on the server side does not configured properly. Please follow the next instruction to configure your SPN. http://blogs.msdn.com/b/rdoherty/archive/2006/07/26/678841.aspx http://technet.microsoft.com/en-us/library/cc281382.aspx If you have any questions, please tell us freely. Regards, EdwardEdward Zhu TechNet Community Support