ID de evento del servicio OpsMgr SDK 26219 - SCOM 2022

ID de evento del servicio OpsMgr SDK 26219 - SCOM 2022

Cada 5 minutos, el siguiente registro se genera dos veces en los registros de Operations Manager en Management Server. Definitivamente está relacionado con los servicios de informes. Desinstalé los servicios de informes por completo y eliminé la base de datos en SQL. Vuelva a instalar todo y configure nuevas bases de datos para los servicios de informes. Todavía genera este registro de eventos.

An exception was thrown while processing GetUserRolesForOperationAndUser for session ID uuid:658fd6bc-f3e1-4201-b906-69dd3950a759;id=647.
 Exception message: Value does not fall within the expected range.
 Full Exception: System.ArgumentException: Value does not fall within the expected range.
   at Microsoft.EnterpriseManagement.Interop.Security.Auth.IAzApplication2.InitializeClientContextFromStringSid(String SidString, Int32 lOptions, Object varReserved)
   at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AzManHelper.GetScopedRoleAssignmentsForUser(Int32 operationNumericId, String userName)
   at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AuthManager.GetUserRolesForOperationAndUser(Guid operationId, String userName)
   at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AuthorizationService.GetUserRolesForOperationAndUser(Guid operationId, String userName)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.SecurityConfigurationService.GetUserRolesForOperationAndUser(Guid operationId, String userName)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessBackCompatProxy.GetUserRolesForOperationAndUser(Guid operationId, String userName)

La vista de eventos también mostrará los ID de evento 26328 y 26329 para la cuenta del lector de datos y la cuenta de acción. El ID de sesión parece apuntar a la cuenta del lector de datos. A la cuenta de lector de datos se le asigna la función de operadores de informes de Operations Manager y los administradores de seguridad de informes de Operations Manager.

Actualmente en la consola no hay ninguna alerta. Pero antes de la reinstalación, también recibía una alerta de que no podía conectarme a \ssrs.

No estoy seguro de qué desencadena exactamente la alerta. No es el evento. Se agradece cualquier ayuda para solucionar este problema. No he encontrado nada concreto buscando en línea.

SSRS: la instancia no se puede conectar al Administrador de informes SSRS

Instance cannot connect to SSRS Report Manager.
PortalStatusCode: 200
Portal Error Message: 
Http Status Code: 
REST Status Code: 500
REST Service Error Message:

SSRS: la instancia no puede conectarse al servicio web SSRS

Instance cannot connect to the SSRS web service.
PortalStatusCode: 500
Portal Error Message: An error occurred when invoking the authorization extension. (rsAuthorizationExtensionError)
Value does not fall within the expected range.
Http Status Code: 
REST Status Code: 0
REST Service Error Message:

Registros adicionales de los servicios de informes:

library!ReportServer_0-1!24d4!06/17/2022-17:16:04:: i INFO: Call to GetItemTypeAction(/). User: NT AUTHORITY\SYSTEM.
library!ReportServer_0-1!24d4!06/17/2022-17:16:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: , Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: An error occurred when invoking the authorization extension. ---> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Value does not fall within the expected range.
Server stack trace: 
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.EnterpriseManagement.Common.ISecuritySpaceDataAccess.GetUserRolesForOperationAndUser(Guid operationId, String userName)
   at Microsoft.EnterpriseManagement.Reporting.Security.ManagementGroupConnection.GetReportingUser(String userName)
   at Microsoft.EnterpriseManagement.Reporting.Security.GroupAuthorization.CheckAccess(String userName, Byte\[\] secDesc, RequiredOperation requiredOperation) at Microsoft.ReportingServices.Library.Security.<>c\_\_DisplayClass21.<CheckAccess>b\_\_1e()
   at Microsoft.ReportingServices.Diagnostics.ExtensionBoundary.Invoke(Method m) - 
   -- End of inner exception stack trace ---;

Respuesta1

Finalmente me di cuenta de esto después de pasar días pensando en el tema. Activar el registro HTTP del servidor de informes me permitió ver lo que estaba sucediendo.

06/17/2022 22:36:05 127.0.0.1 NT AUTHORITY\SYSTEM 127.0.0.1 20480 localhost GET /ReportServer  500 189 938 1.1 - - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1432 94 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1454 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1454 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1454 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1468 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1467 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1467 47 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1467 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1463 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1465 47 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> <DataReaderAccount> <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  200 1486 31 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 367 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 
06/17/2022 22:36:05 <ManagementServer> - <ReportServer> 47873 <Site> POST /ReportServer/ReportService2005.asmx  401 421 0 1.1 Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000) - - - 

Parece que el paquete de administración de SQL Server Reporting Services estaba usando la cuenta de acción del sistema local. Una vez que me di cuenta de esto, pude realizar los cambios apropiados para que usara la cuenta del Lector de datos para determinar si SSRS estaba disponible o no. Desearía que se mencionara lo siguiente como necesario configurar en eldocumentación. Si se menciona en alguna parte, no lo vi.

  • Ir aAdministración-->Ejecutar como configuración-->Perfiles
  • Buscar perfil de ejecución de supervisión de Microsoft SQL Server
  • Agregar una cuenta de ejecución
    • Nombre de cuenta: Cuenta de implementación de informes de almacén de datos
    • Una clase, grupo u objeto seleccionado: Objeto
      • Busque: MSSQL Reporting Services: Instancia (modo nativo)
      • Filtrado por:
      • Agregue el artículo disponible apropiado
      • haga clic en Aceptar y guardar

Tan pronto como hice esto, todas las alertas y eventos desaparecieron de la consola.

información relacionada