User unable to edit a subscription after migration of SSRS from 2008 R2 to 2017Verification that my SSRS...
Does fast page mode apply to ROM?
Enable Advanced Currency Management using CLI
Quenching swords in dragon blood; why?
Book where aliens are selecting humans for food consumption
How to deal with an incendiary email that was recalled
Adding a new switch to a C9300 stack
Jumping Numbers
Every character has a name - does this lead to too many named characters?
Does Improved Divine Strike trigger when a paladin makes an unarmed strike?
Why is "points exist" not an axiom in geometry?
What to do when being responsible for data protection in your lab, yet advice is ignored?
Disable the ">" operator in Rstudio linux terminal
Parsing a string of key-value pairs as a dictionary
Process to change collation on a database
How to explain planetary rings pulsating?
Why Normality assumption in linear regression
Cryptic with missing capitals
Showing size of pie chart in legend of QGIS?
Why do members of Congress in committee hearings ask witnesses the same question multiple times?
Typing Amharic inside a math equation?
How to apply float precision (type specifier) in a conditional f-string?
What was the earliest start time of a Catholic mass before 1957?
What does Cypher mean when he says Neo is "gonna pop"?
Difference between thick vs thin front suspension?
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
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
asked 2 mins ago
SandraSandra
113
add a comment |
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
asked 2 mins ago
SandraSandra
113
add a comment |
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
asked 2 mins ago
SandraSandra
113
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
ssrs ssrs-2017
asked 2 mins ago
SandraSandra
113
asked 2 mins ago
SandraSandra
113
asked 2 mins ago
SandraSandra
113
asked 2 mins ago
SandraSandra
113
asked 2 mins ago
SandraSandra
113
113
add a comment |
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
