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 |
|
steve123
Starting Member
8 Posts |
 Posted - 2007-09-18 : 12:51:51
|
| I’m having problems with security for reporting services when using Windows Integrated Security as the connection type for the data source. Here is the setup: The reporting service is on a virtual machine called cws-devtest. The database usedby the reporting service is on a server called sql2005, and that database is Enterprise Edition.There is a cube from which the report retrieves data on a server called sql2005-dev, that is sql server 2005 Developer Edition.I have created roles on sql2005-dev, and have assigned users and groups to those rolesto achieve the security that I want. I have tested those roles using the cube browser, and using Excel 2007and that looks very good.I created a simple ssrs report to test security in that area, and am having trouble simply viewing any data, logged in as myself, using Windows Integrated Security.Here is the error from the browser:• An error has occurred during report processing. o Cannot create a connection to data source 'trade_dw_cube'. #61607; The connection either timed out or was lost. #61607; Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. #61607; An existing connection was forcibly closed by the remote host.If I use “Credentials stored securely in the report server” in the browser for the data source,and enter my Windows username and password, and check the “Use as Windows credentials when connecting to the data source”checkbox, I can view the report, but that does not use the roles that I had already created. I prefer to use Windows Integrated Security.Has anyone been able to use Windows Integrated Security with SSRS? |
|
|
elracorey
Starting Member
30 Posts |
Posted - 2008-06-26 : 03:25:25
|
| Hi,I have an issue with the "Credentials stored securely in the report server" functionality.If I add a secure SQL user I then get an error saying my report connection cannot be opened.The solution was to delete the SQL user and re-create. Is this a known bug/issue? Regards.Just because something doesn't do what you planned it to do doesn't mean it's useless. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-06-27 : 23:14:26
|
| Did you check Microsoft news group for the issue? |
|
|
|
|
|
|
|
|
Reporting Services Security