We've just deployed SCOM 2012 RTM, and I'm in the process of adding the Reporting Service. When I add a group to the "Operations Manager Report Security Administrators" or "Operations Manager Report Operators" and hit apply, I get this error: Operations Manager Parameter UserRoleDisplayName cannot be null. Additional information Microsoft.EnterpriseManagement.Common.NullConstraintException: Parameter UserRoleDisplayName cannot be null. at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message) at Microsoft.EnterpriseManagement.Common.Internal.SecurityConfigurationServiceProxy.UpsertUserRolesV2(ICollection`1 urUpdateResults, ICollection`1 urScopeUpdateResults, ICollection`1 urViewScopeUpdateResults, ICollection`1 urTaskScopeUpdateResults, ICollection`1 urConsoleTaskScopeUpdateResults, ICollection`1 urTemplateScopeUpdateResults, ICollection`1 urDashboardReferenceScopeUpdateResults, ICollection`1 urUserUpdateResults) at Microsoft.EnterpriseManagement.SecurityConfigurationManagement.UpdateUserRoles(ICollection`1 userRoles) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args) Anyone have an idea what can cause this? Are there some database security permissions missing?

Hi Below thread is related to SCOM 2007 R2 but has good information to start with http://social.technet.microsoft.com/Forums/en-US/operationsmanagerreporting/thread/c77ebd87-b496-45e8-8ba4-6d1264d895f7 ~Cheers, Rohit Kochher

where did you get the 2012 RTM download?

We downloaded it on MSDN. It's under the collection called System Center 2012 RTM or something.

Hi Below thread is related to SCOM 2007 R2 but has good information to start with http://social.technet.microsoft.com/Forums/en-US/operationsmanagerreporting/thread/c77ebd87-b496-45e8-8ba4-6d1264d895f7 ~Cheers, Rohit Kochher The thing is that I've not encountered any of the problems discussed in this thread. The UserRoleDisplayName is filled correctly, the IsSystem value is 1 on all roles under dbo.UserRole. The only thing that I've picked up is the IsScopeFixed of 0 for the Operations Manager Report Operator. All other user roles have 1 in this field. I suspect that this is not the reason for this error, because I also have this problem on the Report Security Administrators. The only evidence of problems I've necountered is some language differences and modified data. When I run the command "Get-SCOMUserRole | Format-List Name, ID, DisplayName" on the Management server with this results: PS C:\> Get-SCOMUserRole | Format-List Name, ID, DisplayName, Description Name : Operations Manager Report Security Administrators Id : 50585907-7858-4488-ab9c-13e0eaac08be DisplayName : Operations Manager Report Security Administrators Description : The Operations Manager Report Security Administrators user role is designed to enable the integration of SQL Server Reporting Services security with Operations Manager user roles. This gives Operations Manager Administrators the ability to control access to reports. This role's scope cannot be changed. Name : Operations Manager Report Operators Id : 2537b367-6d74-4110-b0b5-1f51c1b1b09e DisplayName : Operations Manager Report Operators Description : The Operations Manager Report Operators user role is created during setup and has a global scope. Name : OperationsManagerAdministrators Id : 597f9d98-356f-4186-8712-4f020f2d98b4 DisplayName : Administratorer Description : Brukerrollen for Operations Manager-administratorene er opprettet under konfigureringen og kan ikke slett es. Denne rollen m inneholde n eller flere globale grupper. Name : OperationsManagerAdvancedOperators Id : 489e12f0-6ada-4647-91db-65ab9ff0b40e DisplayName : Avanserte operatrer Description : Brukerrollen for avanserte Operations Manager-operatrer er opprettet under konfigureringen, har globalt omrde og kan ikke slettes. Name : OperationsManagerAuthors Id : 35b4a078-1f02-4988-9599-6824792722ce DisplayName : Forfattere Description : Brukerrollen for Operations Manager-forfattere er opprettet under konfigureringen, har globalt omrde og kan ikke slettes. Name : OperationsManagerApmOperator Id : 357c69fa-b873-4964-be5d-69f4f53b926a DisplayName : Operations Manager Application Monitoring Operator Description : The Operations Manager Application Monitoring Operator user role is created at setup time, is globally sc oped and cannot be deleted. Name : OperationsManagerOperators Id : 3bf09528-6cfa-4e09-bf87-ecade3373814 DisplayName : Operations Manager Operators Description : The Operations Manager Operators user role is created at setup time, is globally scoped and cannot be del eted. Name : OperationsManagerReadOnlyOperators Id : 9f86f9a1-e2d4-4116-893a-f450f800f55d DisplayName : Leseoperatrer Description : Brukerrollen for Operations Manager-leseoperatrer er opprettet under konfigureringen, har globalt omrde og kan ikke slettes. The two first roles, which I have problems with, have Description and Display name in English. The other roles have data written in Norwegian. I can not remember that I have chosen Norwegian ANYWHERE, and the Collation language on the databases is all the Default Latin one. Can this be the reason? That the desplay name for the Report roles have not bein set as Norwegian as well? Where could I check this? The other possible problem I spot is when executing "Select * from userrole" on the OperationsManager database. The result shows that I last modified it with my admin user. The other roles does not show that I have modified them, but I KNOW I have. At least the Operations Manager Admins role. UserRoleID, UserRoleName, ProfileID, IsSystem, IsScopeFixed, LastModified, LastModifiedBy, IsHidden 50585907-7858-4488-AB9C-13E0EAAC08BE Operations Manager Report Security Administrators 94723848-CD34-421B-AD80-02B64664B555 1 1 2012-04-27 18:37:20.230 Domain\Adm_MyUser 0 2537B367-6D74-4110-B0B5-1F51C1B1B09E Operations Manager Report Operators 0B3F51FD-6F81-47C5-8E6F-87085DBD4CEC 1 0 2012-04-27 18:37:21.310 Domain\Adm_MyUser 0 597F9D98-356F-4186-8712-4F020F2D98B4 OperationsManagerAdministrators 25D0CD39-407F-4717-ADB9-8B824BC773E9 1 1 2012-04-27 18:25:05.303 NULL 0 489E12F0-6ADA-4647-91DB-65AB9FF0B40E OperationsManagerAdvancedOperators B0D29ED8-2B8E-4228-9545-E6EF48757AB6 1 1 2012-04-27 18:25:05.843 NULL 0 35B4A078-1F02-4988-9599-6824792722CE OperationsManagerAuthors 3E927DA5-3BA5-4CBE-94B3-D23FC0FC7575 1 1 2012-04-27 18:25:05.957 NULL 0 357C69FA-B873-4964-BE5D-69F4F53B926A OperationsManagerApmOperator 47ACA0F7-4E03-49C6-A18A-F8C0B017BE42 1 1 2012-04-27 18:25:05.913 NULL 0 3BF09528-6CFA-4E09-BF87-ECADE3373814 OperationsManagerOperators 222DFDD1-F100-4763-A253-418A58AE6E42 1 1 2012-04-27 18:25:05.997 NULL 0 9F86F9A1-E2D4-4116-893A-F450F800F55D OperationsManagerReadOnlyOperators F15E9A46-8052-4867-9724-B69D0BC3B79E 1 1 2012-04-27 18:25:06.027 NULL 0

I have the exact same problem - cannot add members to the Report Operators role using SCOM2012 RTM with the UpdateRollup1 applied. The language issues in powershell looks similar to something I encountered in SCSM2012 (which essentially shares the same foundation as SCOM2012). It was related to that SCSM didn't get the language info from system language but the location (or if it was the formats?) setting..?! When I changed that I got the powershell feedback returned in english again. Getting it in Swedish kind of sucked.. ;)

Similar to the issue resolved here where their resolution was to call PSS...this doesn't help us to know how to fix the issue :( I have two SCOM 2012 RTM environments and they both have exactly the same issue, where I cannot add any users or groups to the Report Operator role? I can browse the users/groups but when I click OK I get the error as per the link. I notice that there is no description against this group or the Report Security Administrator group, which seems a bit odd as there is a description in SCOM 2007 R2 for these groups, and even in SCOM 2012 when looking at the relevant SQL table, I can actually see the descriptions...just not in the Console? FYI - both environments run Server 2008 R2 SP1 x64, SQL 2008 SP3. Forest/Domain Function Levels = 2008 R2. Thanks in advance

I finally went for the easy workaround.. Create an own Report Operators role and add the members there.. Worked fine :P

I finally went for the easy workaround.. Create an own Report Operators role and add the members there.. Worked fine :P

I'm doing a new SCOM 2012 implementation for a customer and I have just encountered this error. Searched for the error and this was the first thread result that came up. So what I'm saying is - exact same problem over here. I like JonRunheim's idea, but still...this needs to be fixed. Post up any positive (or negative) things you try. My datareader & datawriter action accounts (specified during the install) seem to be added ok to the Report Security Administrator Role - I just can't add any additional members or groups.http://www.dreamension.net

got it on vlsc, thanks

I finally went for the easy workaround.. Create an own Report Operators role and add the members there.. Worked fine :P Yog Li - this is a workaround, however surely this is not the answer?! The role cannot be added to so the problem is still unresolved. Please unmark this as the answer so that people may still actually endeavour to find the real fix! Thanks

I agree with Kiwifulla. A band-aid fix is not the answer. The true cause of the issue has still not been resolved. http://www.dreamension.net

Still nobody with a clue? This is rather serious in my case. I can't really get any further without some help. I've tried to use the workaround of creating new Security User Roles. But I can not add new Reporting roles. I only have the option between Operator, Read-Only Operator, Author and Advanced Operator. What's going on here?!?

We finally got som answers from Microsoft, and the solution worked perfectly! Here's the mail we got from them, and the suggested solution: This is not the first case reporting this issue that Ive came across in Europe customers. Looks like this is related to Regional settings implemented on OperationsManager DB when install, due to server being in Regional Settings other than English USA. So creating entries on DB with those settings on: Operations Manager Report Operators and Operations Manager Report Security Administrators are special roles and if the System Locale is something other than ENU, then their display Name will never get populated and they will throw the exception. Using SQL query: select * from Localizedtext where LTValue like '%Operations Manager Report Operators%' select * from Localizedtext where LTValue like '%Operations Manager Report Security Administrators%' Will help you to check if you are impacted by this. If setting are other than ENU then you have the issue So what you need to do is update DB to ENU using the following query: update LocalizedText set LanguageCode = 'ENU' where LTStringId = '2537B367-6D74-4110-B0B5-1F51C1B1B09E' update LocalizedText set LanguageCode = 'ENU' where LTStringId = '50585907-7858-4488-AB9C-13E0EAAC08BE' After that and waiting a couple of minutes to the configuration is available, you should be able to edit the groups for Reports. Tell me please how this worked out for you. Ive already asked our developer team to verify this in depth and, if possible, to change behavior on future installs of Operations Manager.

We finally got som answers from Microsoft, and the solution worked perfectly! Here's the mail we got from them, and the suggested solution: This is not the first case reporting this issue that Ive came across in Europe customers. Looks like this is related to Regional settings implemented on OperationsManager DB when install, due to server being in Regional Settings other than English USA. So creating entries on DB with those settings on: Operations Manager Report Operators and Operations Manager Report Security Administrators are special roles and if the System Locale is something other than ENU, then their display Name will never get populated and they will throw the exception. Using SQL query: select * from Localizedtext where LTValue like '%Operation Manager Report Operators%' select * from Localizedtext where LTValue like '%Operations Manager Report Security Administrators%' Will help you to check if you are impacted by this. If setting are other than ENU then you have the issue So what you need to do is update DB to ENU using the following query: update LocalizedText set LanguageCode = 'ENU' where LTStringId = '2537B367-6D74-4110-B0B5-1F51C1B1B09E' update LocalizedText set LanguageCode = 'ENU' where LTStringId = '50585907-7858-4488-AB9C-13E0EAAC08BE' After that and waiting a couple of minutes to the configuration is available, you should be able to edit the groups for Reports. Tell me please how this worked out for you. Ive already asked our developer team to verify this in depth and, if possible, to change behavior on future installs of Operations Manager.

Thanks very much for the solution Mr.Haugen - ours was set to ENZ. FYI - the query for the first section should be Operations (not Operation as this did not return anything). I wonder if anything else will crop up with SQL being installed with ENZ rather than ENU... Thanks again - all fixed :)