December 19, 2016 at 2:37 pm
I am using SQL Server 2008R2. I created a report that uses a shared dataset. I created a new dataset with all the same fields and add 3 new fields. Then I made a copy of the original rdl file. Then changed the dataset to the new dataset. I am able to preview the report in BIDS (where I have been developing the report). When I published the new dataset there were no problems. When I try to publish the new report I get an error message that says "Cannot deploy report XXXXXX to the server because a data set name XXXXX already exists. I have set the property "OverwriteDatasets" to True. Why is it now saying the dataset already exists? When I first published the original report the dataset was published before the report but I did not get any error message.
Thanks for your help.
Fred
December 20, 2016 at 12:37 pm
Try deploying the updated shared dataset separately, and then see if it gives you the same message when you deploy the report. I think the "overwrite dataset" setting might refer to which datasets are attached to the report, rather than the shared dataset itself.
December 20, 2016 at 1:39 pm
Yes, I did deploy the new dataset separately. Afterward I deployed the report. That is when I got the error. I have tried removing the dataset and then deploying the report and it says that the dataset is missing.
When I deploy the dataset and then the report, it errs out saying it is already there.
When I remove the dataset and then deploy the report, it errs out saying it is missing.
How can it be both????
December 20, 2016 at 1:53 pm
Have you tried setting "Overwrite datasets" to false?
December 20, 2016 at 2:17 pm
fred.schmid (12/20/2016)
Yes, I did deploy the new dataset separately. Afterward I deployed the report. That is when I got the error. I have tried removing the dataset and then deploying the report and it says that the dataset is missing.When I deploy the dataset and then the report, it errs out saying it is already there.
When I remove the dataset and then deploy the report, it errs out saying it is missing.
How can it be both????
Another thing to check - I've seen this kind of weirdness before and it has ended up to be permissions. So you may want to double check the permissions on the folder or folders you are using for this.
Sue
December 21, 2016 at 10:51 am
Thank you for your responses!
I can publish the original report to the folder with no problems. It is only the copy that won't allow me to publish it. I can publish other reports to the folder with no problems.
I tried setting the OverwriteDatasets to False and that doesn't fix the error either.
Today, I created a new report and added the new dataset(modified) to it. Then I copied the table from the original report and connected it to the dataset. I was able to publish this report. I am not sure what I did different this time. Is it a fluke that it works sometimes and sometimes it does not? I don't really consider this a solution since I am not sure I did anything different. (Not sure why it works this time.)
Next time I want to try saving the report with a different name and then make modifications to the report and then try publishing it. It will be interesting to see if that works every time. (I saw this solution in another forum).
Does anyone else try to reuse a report so you don't have develop the same report from scratch and not have problems publishing it?
Thanks for your help.
December 21, 2016 at 11:27 am
I have used Save As to make copies of reports so that I didn't have to start from scratch, but haven't (thus far) had any problems publishing the new versions.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply