none
SCSM 2016 web portal OpsMgr SDK Service Event ID: 26319 RRS feed

  • Question

  • Hi everyone. I'm having a pretty hard time trying to figure out what is causing the following issue.

    We have a recently installed SCSM ticket system with a web portal. At random times, we have sort of a period of "down time" that gives end users an error when they submit a ticket. The error reads "Failed. The user (domain\username) does not have sufficient permission to perform the operation.". However, the incident is submitted and the user receives a notification as per normal. The username is not specific to the user submitting the ticket, it seems to always display the last user to submit a ticket without that error appearing.

    In the event viewer, we get a couple different errors. The first is the one from the title: OpsMgr SDK Service, Event ID: 26319. The error information is as follows: 

    An exception was thrown while processing ProcessDiscoveryData for session ID uuid:a475af97-81bc-4888-8afe-f6a4132ff350;id=62.
     Exception message: The user ISANS\mdykens does not have sufficient permission to perform the operation.
     Full Exception: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessEnterpriseManagementException: The user ISANS\mdykens does not have sufficient permission to perform the operation.
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreAuthorization.Authorize(DiscoveryDataInstance discoveryDataInstance, IAuthorizationService authService, Boolean useProcessContext, WindowsIdentity identity, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.AuthorizeEntityObjects(DatabaseConnection databaseConnection, Guid discoverySourceId, IContext context, IList`1 packets)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.ProcessIncrementalDiscoveryData(DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.Process()
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)

    The other error we are getting it  a DistributedCOM, event ID 10016, the details read as follows:

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
     and APPID 
    {F72671A9-012C-4725-9D2F-2A4D32D65169}
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    We have recently deployed some new hardware and are planning on moving the SCSM VMs over to the new hardware as we have experienced some slow downs in a few of our services. Could this be caused by slow system response?

    Wednesday, October 9, 2019 12:28 PM

All replies

  • Which Update Rollup of SCSM 2016 is installed on the SCSM Portal Server and on the other SCSM 2016 Servers?


    Andreas Baumgarten

    Wednesday, October 9, 2019 5:34 PM
    Moderator
  • Hi, sorry for the delay.

    After making sure the portal is up to the right rollout (everything is now at rollout 7), the error seemed to have stopped. So all of last week, there were no reports of this error, when it was happening multiple times daily.

    However, it is happening now. The same error is in the event viewer. So it hasn't been happening much since the update, but it is still happening.

    Monday, October 21, 2019 4:00 PM
  • For the last error, this post may help.

    But for the first error, is this happening always for "ISANS\mdykens" or it happens for all users? We used to have this problem, caused by password policies.

    Is it the workflow account or a normal user? It is stating that it cannot authorize the user.


    YSobhdel

    Wednesday, October 30, 2019 3:05 PM