I'll have to try this out.. I ran into this issue a while ago but have revisited it. Thanks From: [email protected] To: [email protected] Subject: [mssms] RE: reporting issues after upgrade - UPDATE Date: Mon, 22 Feb 2016 20:41:44 +0000
http://configmgrninja.com/configmgr-2012-r2-upgrade-report-errors/ From: [email protected] [[email protected]] on behalf of Qadri, Syed [[email protected]] Sent: Monday, February 22, 2016 2:48 PM To: [email protected] Subject: [mssms] RE: reporting issues after upgrade - UPDATE It is a registered BUG in Microsoft. Here you are disabling RBAC to make your reports work. So it cannot be by design that you will have to make your reporting work at the cost of RBAC feature. Thus MS considered it as a BUG. From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Tuesday, February 23, 2016 1:04 AM To: [email protected] Subject: [mssms] RE: reporting issues after upgrade - UPDATE I don’t know that I’d call it a bug. I would assume that if you configure RBAC reporting, that things work, correct? From: [email protected] [mailto:[email protected]] On Behalf Of Qadri, Syed Sent: Monday, February 22, 2016 11:11 AM To: [email protected] Subject: [mssms] RE: reporting issues after upgrade - UPDATE Seems to be a time thing. Actually I haven’t seen any alternative to the RBAC thing. Microsoft would be in a better position to give this answer. This BUG has been running since the starting of the SCCM 2012 R2. From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Tuesday, February 23, 2016 12:13 AM To: [email protected] Subject: [mssms] RE: reporting issues after upgrade - UPDATE Why does it change back? Is it a time thing, or a reboot thing? What’s the alternative, to actually configure RBAC reporting? From: [email protected] [mailto:[email protected]] On Behalf Of Qadri, Syed Sent: Monday, February 22, 2016 10:33 AM To: [email protected] Subject: [mssms] RE: reporting issues after upgrade - UPDATE It gets changed to default value anyways. I guess you might have to find a way doing the change through WMI to have it permanently fixed to 0. From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Monday, February 22, 2016 11:55 PM To: '[email protected]' Subject: [mssms] RE: reporting issues after upgrade - UPDATE Ok, so the fix from netdavidic.com was done last week. I looked at the registry just now, and that EnableRBACReporting registry key was back to 1, instead of 0. So, the question now would be how did it get changed back? From: Heaton, Joseph@Wildlife Sent: Monday, February 22, 2016 10:10 AM To: '[email protected]' Subject: reporting issues after upgrade I recently upgraded my SCCM environment from 2012 SP1, to 2012 R2 SP1 CU2. I’m now having errors occur with reports. I found and followed this article, which seemed to resolve some issues: http://www.netdavidic.com/2013/11/how-to-fix-sccm-2012-r2-reporting.html But today, I’m still getting errors. I apologize for the large copy/paste here: I’m digging for answers on this as well, and I have my SCCM guru looking into it, but thought I’d throw it out here, to see if any of you have run into this with similar upgrades. Thanks, Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284 Every Californian should conserve water. Find out how at: SaveOurWater.com · Drought.CA.gov This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
