Hello, I created a report with a shared data source for accessing a database in the local machine. I could run the report locally without any problem. The build and deploy for the report was also successful. But when I accessing the report in the report manager, I get the rsErrorOpeningConnection problem. I want to add here that I am using the same domain account to access the local sql server and report manager and I can view other reports in the report manager successfully. So I accessed the data source in report manager and instead of using windows integrated secuirty for the data source I have given my same domain name and password (which I think should be same if I use windows integrated secuirty as I am using the same account) and I checked to use this credentials to access the data source and now it worked. But I am confused why it didn't work the first time as I am using the same account, please let me know if you know the reason. Thanks.

Sounds like you ran into a double-hop limitation in NTLM, where 1. you're access from your machine to the report server machine is the first hop. 2. the report server machine to your database machine is the second hop. NTLM does not allow credentials to be passed beyond the first hop, which is why your report works before you deploy it (no hop) and after you store credentials (two independent first hops). To get around this, you'll need to setup windows integrated authentication with Kerberos. Detailed help on this can be found at http://download.microsoft.com/download/B/E/1/BE1AABB3-6ED8-4C3C-AF91-448AB733B1AF/SSRSKerberos.docx. (Note: setting up Kerberos is non-trivial and requires domain administrator privileges, so depending on your situation you might just want to stick with your workaround.)Cephas Lin This posting is provided "AS IS" with no warranties.