October 25, 2011 at 2:03 pm
I am running 2008 R2
I have an entire set of reports that I have to load into RS. These were developed and sent to our company by a third party. They connect to a shared data source. I uploaded the reports into folders that separated them by function. The problem is that they don't see the data source that the reports are written to use. I created a shared data source and pointed the report to it. The connection tested successfully but when I ran the report I continued to receive the following error:
"The report server cannot process the report or shared dataset. The shared data source 'dsMyObject' for the report server or SharePoint is not valid. Browse to the server or site and select a shared data source. (rsInvalidDataReference)"
When I used the exact same credentials in an embedded data source the report runs and after I get it to run I can change it back to the shared data source I created and it runs just fine.
My problem is that this process is too inefficient I have to many reports, and many more servers to roll this too, to have to manually switch the data source back and forth in order for it to work.
I noticed that when I look through the list of data sources I see the ones that I created with the name of the DS on the first line and the location on the next (http://[Server]/reports/%5BData Source Folder]) while the DS created by the vender have the name of the DS on both lines. This leads me to believe that there is a way to load the DS into SSRS with the same name the vendor used in such a way to allow the reports to automatically use them. I can’t find anything that tells me how to do this so I am asking this question here. How do I get prewritten reports to see a shared data source on the server I deploy the reports to?
Thanks in advance,
October 25, 2011 at 2:18 pm
Unfortunately, I must tell that I have had the exact same issue. What I did is the same as described here, I browsed to the report, and configured it manually to use the shared data source. Voila, it worked. And I did not have to do it the next time I published an updated version of the report. Why this happens? Honestly, I don't have the slightest idea.
October 25, 2011 at 2:31 pm
Having to change each one would really be a hassle but even more so when I have to configure and run it with an embedded data source before I can point it to the appropriate shared data source; as I described in the original post. Can some one at least give me a way to avoid that even if they can’t save me from modifying each report?
It’s obvious that the shared is configured correctly since it eventually works perfectly but it doesn’t work at first.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply