Answered by:
SQL connection with security for reports - data not returned properly

Question
-
Hi,
We're having some issues with reports securtiy.
For example, a manager role is seeing data that he shouldn't.
I'm wondering if didn't set up the connection string corrrectly.
This is what i have currently.
THanks for taking the time to have a look.
Name: The item name is not valid. Item names cannot contain the following reserved characters ;? &=+$,\*<>|"/, and cannot consist exclusively of dots or spaces.
The length of the item name is not valid. Item names must be between 1 and 260 characters long. A required field is missing its value. Type or enter a value for the field. Description: The description is too long. It may not exceed 512 characters. Connection type: The data processing extension used for this report is not available. It has either been uninstalled, or it is not configured correctly. Connection string: Connection type: The data processing extension used for this report is not available. It has either been uninstalled, or it is not configured correctly. Connection string: Connect using: Display the following text to prompt user for a user name and password: User name: Password: The password is not valid. Please retype the password. Tuesday, September 18, 2007 2:15 PM
Answers
-
Hi Mike,
You need to select "Windows Integrated Security" instead of "Credentials stored securely in the report server". Windows integrated security will use the credentials of currently login user and will show the correct data accordingly.
Tuesday, September 18, 2007 5:19 PMModerator
All replies
-
Hi Mike,
You need to select "Windows Integrated Security" instead of "Credentials stored securely in the report server". Windows integrated security will use the credentials of currently login user and will show the correct data accordingly.
Tuesday, September 18, 2007 5:19 PMModerator -
Thanks Umar.
David Jennings replied with the same answer and i'll give you the same response i sent him.
I initially thought that was how the connection should be done but one of the other developers changed it.
The problem though now when it is set to integrated security, it gives a SQL connection error.
I'm away from the office and don't know the exact error message they are getting.
Maybe the users are not set up with report permissions?
Thanks again.
Tuesday, September 18, 2007 5:26 PM -
Hi, Check out if connection string is right?
Tuesday, September 18, 2007 5:46 PMModerator -
Yeah. Connection works.
Right now i'm thinking if they've set up the user configuration correctly.
The reason why i'm thinking about this is that some users can view certain reports.
So...we'll have to figure out what those people did in setting it up.
Thanks.
Tuesday, September 18, 2007 6:28 PM