User unable to edit a subscription after migration of SSRS from 2008 R2 to 2017Verification that my SSRS...

What does Cypher mean when he says Neo is "gonna pop"?

Solving Fredholm Equation of the second kind

Broken patches on a road

A minimum of two personnel "are" or "is"?

Why did this image turn out darker?

What kind of hardware implements Fourier transform?

What is better: yes / no radio, or simple checkbox?

Can an insurance company drop you after receiving a bill and refusing to pay?

Word or phrase for showing great skill at something without formal training in it

Why zero tolerance on nudity in space?

Help Me simplify: C*(A+B) + ~A*B

Can a person refuse a presidential pardon?

How does Arcane Armament interact with the Artillerist Artificer's Wand Prototype feature?

How to prevent users from executing commands through browser URL

Adding a new switch to a C9300 stack

What is a jet (unit) shown in Windows 10 calculator?

Why does a metal block make a shrill sound but not a wooden block upon hammering?

How to apply float precision (type specifier) in a conditional f-string?

Program that converts a number to a letter of the alphabet

What to do when being responsible for data protection in your lab, yet advice is ignored?

How can animals be objects of ethics without being subjects as well?

Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?

Can a dragon be stuck looking like a human?

How to deal with an incendiary email that was recalled



User unable to edit a subscription after migration of SSRS from 2008 R2 to 2017


Verification that my SSRS subscription was emailed to a valid addressHow should I deploy these SSRS reports?SSRS Reports Manager Security ConfigurationUser can create in SSRS, but can't manage objectsSSRS Domain MigrationCrazy SSRS IssueSSRS (2008 R2 to 2014) Migration Issues Running ReportsWhat are the user privileges required to for an ssrs report owner to 'send email'SSRS 2008R2 to 2016 report manager - has permissions model changed?Migration from SSRS 2012 to SSRS 2017













0















I performed a migration of our SSRS 2008 R2 instance to a brand new SSRS 2017 instance. This was accomplished via Microsoft's documented instructions "Migrate a Reporting Service Installation (Native Mode)": Backup/Restore of the DBs, setup of the RSExecRole in the system DBs with permissions, import the encryption keys for the old server. Everything is working well and we're slowly turning on reports in the new environment and turning off in the old after testing.



Everything seems to be working except for this one thing: We give our DOMAINDomain Users group access via Site settings. It's a System User. And, for a particular folder of reports, we have a user who is explicitly added to that folder by domain account name with permissions more than sufficient to edit subscriptions. And, this still works fine. However, when a user who did not have this explicit access/permissions on the old server was added to the folder on the new server in the same fashion, he is not able to edit an existing subscription. The error is "The permissions granted to user 'DOMAINUSER' are insufficient for performing this operation" This is despite the user not only being a member of all the same roles as the existing user but being added to the System Administrators role in Site settings. (!)



The error occurs when the user clicks the "Edit" link for the subscription. The subscription page begins to open but the error dialog appears and the page is greyed out. The user can create a subscription (or at least get the page to open). It doesn't matter whether the subscription is data driven or standard. It doesn't matter if the subscription existed before the migration or was created after.



Given that the user now has all the permissions possible in SSRS, I'm not sure where to look next. It's baffling to me that the function works in general, it just doesn't work for someone who was given permissions after the migration.



Both the old and new server are running under the same service account.









share



























    0















    I performed a migration of our SSRS 2008 R2 instance to a brand new SSRS 2017 instance. This was accomplished via Microsoft's documented instructions "Migrate a Reporting Service Installation (Native Mode)": Backup/Restore of the DBs, setup of the RSExecRole in the system DBs with permissions, import the encryption keys for the old server. Everything is working well and we're slowly turning on reports in the new environment and turning off in the old after testing.



    Everything seems to be working except for this one thing: We give our DOMAINDomain Users group access via Site settings. It's a System User. And, for a particular folder of reports, we have a user who is explicitly added to that folder by domain account name with permissions more than sufficient to edit subscriptions. And, this still works fine. However, when a user who did not have this explicit access/permissions on the old server was added to the folder on the new server in the same fashion, he is not able to edit an existing subscription. The error is "The permissions granted to user 'DOMAINUSER' are insufficient for performing this operation" This is despite the user not only being a member of all the same roles as the existing user but being added to the System Administrators role in Site settings. (!)



    The error occurs when the user clicks the "Edit" link for the subscription. The subscription page begins to open but the error dialog appears and the page is greyed out. The user can create a subscription (or at least get the page to open). It doesn't matter whether the subscription is data driven or standard. It doesn't matter if the subscription existed before the migration or was created after.



    Given that the user now has all the permissions possible in SSRS, I'm not sure where to look next. It's baffling to me that the function works in general, it just doesn't work for someone who was given permissions after the migration.



    Both the old and new server are running under the same service account.









    share

























      0












      0








      0








      I performed a migration of our SSRS 2008 R2 instance to a brand new SSRS 2017 instance. This was accomplished via Microsoft's documented instructions "Migrate a Reporting Service Installation (Native Mode)": Backup/Restore of the DBs, setup of the RSExecRole in the system DBs with permissions, import the encryption keys for the old server. Everything is working well and we're slowly turning on reports in the new environment and turning off in the old after testing.



      Everything seems to be working except for this one thing: We give our DOMAINDomain Users group access via Site settings. It's a System User. And, for a particular folder of reports, we have a user who is explicitly added to that folder by domain account name with permissions more than sufficient to edit subscriptions. And, this still works fine. However, when a user who did not have this explicit access/permissions on the old server was added to the folder on the new server in the same fashion, he is not able to edit an existing subscription. The error is "The permissions granted to user 'DOMAINUSER' are insufficient for performing this operation" This is despite the user not only being a member of all the same roles as the existing user but being added to the System Administrators role in Site settings. (!)



      The error occurs when the user clicks the "Edit" link for the subscription. The subscription page begins to open but the error dialog appears and the page is greyed out. The user can create a subscription (or at least get the page to open). It doesn't matter whether the subscription is data driven or standard. It doesn't matter if the subscription existed before the migration or was created after.



      Given that the user now has all the permissions possible in SSRS, I'm not sure where to look next. It's baffling to me that the function works in general, it just doesn't work for someone who was given permissions after the migration.



      Both the old and new server are running under the same service account.









      share














      I performed a migration of our SSRS 2008 R2 instance to a brand new SSRS 2017 instance. This was accomplished via Microsoft's documented instructions "Migrate a Reporting Service Installation (Native Mode)": Backup/Restore of the DBs, setup of the RSExecRole in the system DBs with permissions, import the encryption keys for the old server. Everything is working well and we're slowly turning on reports in the new environment and turning off in the old after testing.



      Everything seems to be working except for this one thing: We give our DOMAINDomain Users group access via Site settings. It's a System User. And, for a particular folder of reports, we have a user who is explicitly added to that folder by domain account name with permissions more than sufficient to edit subscriptions. And, this still works fine. However, when a user who did not have this explicit access/permissions on the old server was added to the folder on the new server in the same fashion, he is not able to edit an existing subscription. The error is "The permissions granted to user 'DOMAINUSER' are insufficient for performing this operation" This is despite the user not only being a member of all the same roles as the existing user but being added to the System Administrators role in Site settings. (!)



      The error occurs when the user clicks the "Edit" link for the subscription. The subscription page begins to open but the error dialog appears and the page is greyed out. The user can create a subscription (or at least get the page to open). It doesn't matter whether the subscription is data driven or standard. It doesn't matter if the subscription existed before the migration or was created after.



      Given that the user now has all the permissions possible in SSRS, I'm not sure where to look next. It's baffling to me that the function works in general, it just doesn't work for someone who was given permissions after the migration.



      Both the old and new server are running under the same service account.







      ssrs ssrs-2017





      share












      share










      share



      share










      asked 5 mins ago









      SandraSandra

      113




      113






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231105%2fuser-unable-to-edit-a-subscription-after-migration-of-ssrs-from-2008-r2-to-2017%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231105%2fuser-unable-to-edit-a-subscription-after-migration-of-ssrs-from-2008-r2-to-2017%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Parapolítica Índice Antecedentes El escándalo Proceso judicial Consecuencias Véase...

          How to remove border from elements in the last row?Targeting flex items on the last rowHow to vertically wrap...

          Tecnologías entrañables Índice Antecedentes Desarrollo Tecnologías Entrañables en la...