August 29, 2017 at 7:53 am
We upgraded SSRS from 2008 to 2014 a while back, and are making our first attempt to add/modify subscriptions, and it is failing miserably.
If there is a drop down parameter selection on the subscription page any attempt to access this data causes JavaScript errors in C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportManager\js\ReportingServies.js We found two "rewrites" of this through searches, neither of which work. The error causes the entire subscription page to hang, and we cannot manage subscriptions.
We had been behind on updates, but brought the server to SQL Server 2014 SP2 CU6 with no change in behavior (or in the size/create date of the above named file). Has Microsoft addressed this issue (searches there have been useless), and if so, how do I obtain the fix?
August 31, 2017 at 3:09 pm
bboelke 52928 - Tuesday, August 29, 2017 7:53 AMWe upgraded SSRS from 2008 to 2014 a while back, and are making our first attempt to add/modify subscriptions, and it is failing miserably.
If there is a drop down parameter selection on the subscription page any attempt to access this data causes JavaScript errors in C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportManager\js\ReportingServies.js We found two "rewrites" of this through searches, neither of which work. The error causes the entire subscription page to hang, and we cannot manage subscriptions.
We had been behind on updates, but brought the server to SQL Server 2014 SP2 CU6 with no change in behavior (or in the size/create date of the above named file). Has Microsoft addressed this issue (searches there have been useless), and if so, how do I obtain the fix?
Could you please post the error message and what you have tried so far? It would really help if you could add the browser you are using and any other errors you see in the Reporting Services log as well.
Sue
September 1, 2017 at 5:59 am
It turns out it was a data issue and bad code in the ASPX/JavaScript. There was a query driven parameter, and the displayed value (Name field, not part of the key value) had two values the same. This apparently breaks the subscription functionality. It's a bug, but one we can work around (the report page itself had no issue with it).
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply