scom A file share could not be created

Carl94580345 31 Reputation points
2022-08-24T16:37:59.603+00:00

we have 4 scom servers all running 2019 UR4
2 running on win 2012r2 and working
2 running on win 2022 and throwing the below error when configuring monitoring

A file share could not be created
error could not create group aemuser the group name could not be found
error could not create group aemagent the group name could not be found

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,413 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,113 questions
{count} votes

3 answers

Sort by: Most helpful
  1. SChalakov 10,261 Reputation points MVP
    2022-08-26T10:13:23.307+00:00

    Hi @Carl94580345 ,

    can you please post some more information about the behavior:

    • Where exactly does the error show up? What are you configuring exactly? Can you please post a screenshot of the exact error and its detail?
    • What is the state of those Management Servers (Monitoring -> Operations Manager -> Management Server State)
    • What evenbts are being logged on those Management Servers at the time when the issue happens? Can you please check the event log and post the related events here?

    Thanks and Regads,
    Stoyan

    0 comments No comments

  2. Carl94580345 31 Reputation points
    2022-08-26T15:32:45.113+00:00

    seeing errors like

    An exception was thrown while processing Connect for session ID uuid:3080f1f0-3c42-4ea1-904c-4e01742c060c;id=1011.
    Exception message: The creator of this fault did not specify a Reason.
    Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessEnterpriseManagementException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.UnauthorizedAccessEnterpriseManagementException: The user domian\scom-da does not have sufficient permission to perform the operation.).

    Query returned no results
    Namespace \.\ROOT\CIMV2
    Query SELECT Timestamp_PerfTime,Frequency_PerfTime,TimeStamp_Sys100NS,Name,HandleCount FROM Win32_PerfRawData_PerfProc_Process WHERE IDProcess=2744

    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.NTService.CollectHandleCount
    Instance name: Management Configuration Service
    Instance ID: {58C709BF-0B07-20A4-83B8-CD7763D63F07}
    Management group: XXX

    0 comments No comments

  3. XinGuo-MSFT 14,236 Reputation points
    2022-08-29T08:14:47.88+00:00

    >The user domian\scom-da does not have sufficient permission to perform the operation.

    Please try to add the domian\scom-da to the Operations Manager Administrators group in SCOM.

    0 comments No comments