October 5, 2011 at 1:14 am
Can someone resolve this issue for me pleasee
October 5, 2011 at 11:46 am
Usually this means I have to go back to the dataset and do my calculation there and just put the field on the report.
October 5, 2011 at 11:52 am
abbysql (10/5/2011)
Are there any differences between the source queries (probably stored procs...I hope) on the two servers?
October 7, 2011 at 3:55 pm
Data Source is basically the same. The Stored Procedures used to be always on SERVER B, and from SERVER A it used to access the Stored Procedures on SERVER B. Now its more direct. Since all the Reports are being moved to SERVER B it self.
Still confused. I downloaded from Server A and tried to upload and these out of scope errors popped up.
Could it be that the XML File was not formatted properly when I downloaded the report, is there any clean way to get the original XML file for the SSRS Report.
October 7, 2011 at 4:09 pm
abbysql (10/7/2011)
Data Source is basically the same. The Stored Procedures used to be always on SERVER B, and from SERVER A it used to access the Stored Procedures on SERVER B. Now its more direct. Since all the Reports are being moved to SERVER B it self.Still confused. I downloaded from Server A and tried to upload and these out of scope errors popped up.
Could it be that the XML File was not formatted properly when I downloaded the report, is there any clean way to get the original XML file for the SSRS Report.
Hmm...interesting. I don't think the formatting of the XML is wack...downloading it from the server should be as good as any. Can you try and open the reports in Visual Studio (or BIDS), and deploy from there?
October 7, 2011 at 5:28 pm
Yes, I tried that too, its giving me the same errors and not able to deploy the reports due to that errors. .......
Indeed it is interesting. I am also willing to do a webex with some one who wants to have a look at it. ....
October 8, 2011 at 5:49 am
abbysql (10/7/2011)
Yes, I tried that too, its giving me the same errors and not able to deploy the reports due to that errors. .......Indeed it is interesting. I am also willing to do a webex with some one who wants to have a look at it. ....
I could do a webex with you, but only in about a week's time...don't know if that is too late for you.
Before we get there though, please have a look at the following:
1. Are the SSRS versions (including service packs) on both servers the same?
2. The text fields giving the errors seem not be part of a tablix. If so, ensure that the expressions explicitly refer to the datasource. You may have to recreate the expressions.
3. Check your datasources again. Make sure that the names are identical (case is important in the expressions). Also check field names.
4. Replace the expressions of the error fields with some other hard-coded value, and see if you are still unable to deploy the report. Just trying to make sure there are no other errors...
Hope this helps.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply