June 2, 2005 at 8:28 pm
Not sure if it's been posted previously, but this looks like it could be a big help in transferring objects from RS server 1 to RS server 2.
Thanks to Mat Stephens' blog for the pointer to the site and tool.
http://www.sqldbatips.com/showarticle.asp?ID=62
Steve.
June 6, 2005 at 8:00 am
This was removed by the editor as SPAM
July 4, 2013 at 6:29 am
It would be nice if there were other mechanisms to get you the answers we need more timely, but this tool is used as is with little instruction. Best hope is for people that have used this be nice enough to provide input.
I've used this tool to migrate reports 2005 to 2012. It was a little frustrating at first because my subscriptions were not transferring. In reviewing the log file generated by this process I really paid attention to the errors. Although you'll not see "your subscriptions didn't generate because", resolving those errors is key. You may still receive errors that the parameter is not supplied and for any .rdl error your subscription for that report more than likely won't generate.
Bottom line: after you select your options on the report tab, to include subscriptions and choose your location and script your objects; open the file and simply change the URL to point to your new server ....
In the folder(s) that contain you actual .rdl and .rss, you'll need to open all .rss file and provide passwords for those that have passwords required for them. In my case we used dynamic connections which required passwords for each .rdl file.
Very important: Open your Data Sources folder and for each .rss file open and provide the passwords for your connections. This will allow your subscriptions to generate. This took me a while to catch.
Good luck
July 4, 2013 at 6:54 am
Christopher Ware (7/4/2013)
It would be nice if there were other mechanisms to get you the answers we need more timely, but this tool is used as is with little instruction. Best hope is for people that have used this be nice enough to provide input.I've used this tool to migrate reports 2005 to 2012. It was a little frustrating at first because my subscriptions were not transferring. In reviewing the log file generated by this process I really paid attention to the errors. Although you'll not see "your subscriptions didn't generate because", resolving those errors is key. You may still receive errors that the parameter is not supplied and for any .rdl error your subscription for that report more than likely won't generate.
Bottom line: after you select your options on the report tab, to include subscriptions and choose your location and script your objects; open the file and simply change the URL to point to your new server ....
In the folder(s) that contain you actual .rdl and .rss, you'll need to open all .rss file and provide passwords for those that have passwords required for them. In my case we used dynamic connections which required passwords for each .rdl file.
Very important: Open your Data Sources folder and for each .rss file open and provide the passwords for your connections. This will allow your subscriptions to generate. This took me a while to catch.
Good luck
Unfortunately, the RSScripter tool is seriously outdated. It only supports SSRS until 2008. 2008R2 and 2012 are not supported and that's most likely why you run in so many errors.
I have looked into alternatives and used MSBUILD for one project. A colleague of mine used VBscripts together with the SSRS web service to deploy everything. (you can find a link to his findings in the same blog post)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply