A cada 5 minutos, o seguinte log é gerado duas vezes nos logs do Operations Manager no Management Server. Definitivamente está relacionado aos serviços de relatórios. Desinstalei totalmente os serviços de relatório e excluí o banco de dados SQL. Reinstale tudo e configure novos bancos de dados para os serviços de relatório. Ainda gera esse log 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)
A visualização do evento também mostrará os IDs de evento 26328 e 26329 para a conta do Leitor de Dados e da Conta de Ação. O ID da sessão parece apontar para a conta do Data Reader. A conta Leitor de Dados recebe a função de Operadores de Relatório do Operations Manager e Administradores de Segurança de Relatório do Operations Manager.
Atualmente no console, não há alerta. Mas antes da reinstalação, eu também receberia um alerta de que não foi possível conectar-se ao \ssrs
Não tenho certeza do que exatamente aciona o alerta. Não é o evento. Qualquer ajuda para resolver isso é apreciada. Não encontrei nada concreto pesquisando online.
SSRS: a instância não pode se conectar ao SSRS Report Manager
Instance cannot connect to SSRS Report Manager.
PortalStatusCode: 200
Portal Error Message:
Http Status Code:
REST Status Code: 500
REST Service Error Message:
SSRS: a instância não pode se conectar ao serviço 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:
Logs adicionais dos serviços de relatórios:
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 ---;
Responder1
Finalmente descobri isso depois de passar dias pensando no assunto. Ativar o log HTTP do servidor de relatórios me permitiu ver o que estava acontecendo.
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 o Pacote de Gerenciamento do SQL Server Reporting Services estava usando a conta de ação do sistema local. Assim que percebi isso, consegui fazer as alterações apropriadas para que ele usasse a conta do Data Reader para determinar se o SSRS estava disponível ou não. Gostaria que o seguinte fosse mencionado como precisando ser configurado nodocumentação. Se for mencionado em algum lugar, eu não vi.
- Vá paraAdministração-->Configuração Executar como-->Perfis
- Pesquise o perfil Run As do monitoramento do Microsoft SQL Server
- Adicionar uma conta Run As
- Nome da conta: Conta de implantação de relatório de data warehouse
- Uma classe, grupo ou objeto selecionado: Objeto
- Procure: MSSQL Reporting Services: Instância (modo nativo)
- Filtrar por:
- Adicione o item disponível apropriado
- clique em ok e salve
Assim que fiz isso, todos os alertas e eventos desapareceram do console.