Каждые 5 минут в журналах Operations Manager на Management Server дважды генерируется следующий журнал. Это определенно связано со службами отчетов. Я полностью удалил службы отчетов и удалил базу данных в SQL. Переустановите все и настройте новые базы данных для служб отчетов. Все еще генерируется этот журнал событий.
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)
В представлении событий также будут показаны идентификаторы событий 26328 и 26329 для учетной записи Data Reader и учетной записи Action. Идентификатор сеанса, похоже, указывает на учетную запись Data Reader. Учетной записи Data Reader назначены роли Operations Manager Report Operators и Operations Manager Report Security Administrators.
В данный момент в консоли нет оповещения. Но перед переустановкой я бы также получил оповещение о том, что не удалось подключиться к \ssrs
Я не уверен, что именно вызывает оповещение. Это не событие. Любая помощь в решении этой проблемы приветствуется. Я не нашел ничего конкретного в Интернете.
SSRS: Экземпляр не может подключиться к диспетчеру отчетов 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: Экземпляр не может подключиться к веб-службе 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:
Дополнительные журналы от служб отчетности:
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 ---;
решение1
Я наконец понял это после того, как потратил несколько дней на эту проблему. Включение HTTP-журнала сервера отчетов позволило мне увидеть, что происходит.
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) - - -
Похоже, что SQL Server Reporting Services Management Pack использовал учетную запись Local System Action. Как только я это понял, я смог внести соответствующие изменения, чтобы использовать учетную запись Data Reader для определения доступности SSRS. Хотелось бы, чтобы следующее было упомянуто как требующее настройки вдокументация. Если это где-то и упоминалось, то я этого не видел.
- Идти кАдминистрация-->Запустить как конфигурацию-->Профили
- Поиск профиля запуска Microsoft SQL Server Monitoring Run As
- Добавить учетную запись Run As
- Имя учетной записи: Учетная запись развертывания отчетов хранилища данных
- Выбранный класс, группа или объект: Объект
- Поиск: MSSQL Reporting Services: экземпляр (собственный режим)
- Сортировать по:
- Добавьте соответствующий доступный элемент
- нажмите ок и сохраните
Как только я это сделал, все оповещения и события в консоли исчезли.