March 23, 2004 at 9:06 am
I have successfully installed SQL RS, with all the components excluding Visual Studio and my report datasource db, on the same machine. I have also successfully deployed reports created within VS, to SQL RS, and viewed them through the web app (Report Manager). Although, to get this to work, I used the 'Credentials stored securely in the report server' authentication method, using the 'sa' login credientials. This worked. When I switched this to 'Windows NT Integrated Security', I got the message below.
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Again, I have the data source for this report in question, using NT Integrated Security, thus, Im not sure why the login below is for 'NT AUTHORITY'. This sounds like a system account used to run some of the required services, but Im not sure.
Id appreciate any help on this!
Greg
March 23, 2004 at 10:17 am
Check the security for the Reporting Services website (where the report manager sits). It sounds like it's set for anonymous logon. Try changing that to Integrate Windows Authentication only.
March 24, 2004 at 8:42 am
James,
Thanks for the reply - I checked the IIS security settings for both Reports AND ReportServer (Directory Security/Anonymous and authentication control) , and they were both set to "Integrated Windows Authentication".
From the error message I'm receiving, it seems like the authentication problem is with the db being queried by the report, and not the login to the Reports web app. ('db Name' below is actually the name of the 'data' db being queried by the report, NOT the RS system db).
Cannot create a connection to data source 'db Name'. (rsErrorOpeningConnection) Get Online Help
Also, Im pretty sure that this is true, because, when I go into the data source for the report, within the Reports web app, and 'toggle' the authentication, it works when I hard code sql credentials, eg, "sq and pw", but NOT when i change it to windows authentication. Maybe its a setting on the db and not the web app?
Any thoughts?
Greg
March 25, 2004 at 3:08 pm
We had this problem just logging into one of SQL Servers using NT Authentication. I believe we had to reboot the SQL Server in order to use NT Authentication. It was like the SQL Server was no longer receiving the token or could not communicate with Acitve Direcotry to verify the login.
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
May 5, 2004 at 10:06 am
Greg,
I'm having the exact same problem. Have you found the solution for this issue?
Thanks,
Thao
June 8, 2004 at 9:55 am
Greg,
I am having this same problem when I try to use Windows Authentication. If I switch to "Credentials stored securely on report server" then my report works.
Did you ever figure out how to fix this?
Thanks.
Nancy
March 11, 2005 at 5:39 pm
Hey, I know it has been about a year since you posted this... but I was doing a google search on the problem and came across your post. I installed reporting services recently and am getting the same problem. I have my ASP / IIS server installed on a different machine than my sql server. When I try to access my reports from the box IIS is installed on, it works fine. When I try to access the same reports from another computer on the network, I get your error. Did you ever solve this?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply