Alle 5 Minuten wird das folgende Protokoll zweimal in den Operations Manager-Protokollen auf dem Management-Server generiert. Es hängt definitiv mit den Reporting Services zusammen. Ich habe die Reporting Services vollständig deinstalliert und die Datenbank in SQL gelöscht. Installieren Sie alles neu und konfigurieren Sie neue Datenbanken für die Reporting Services. Dieses Ereignisprotokoll wird trotzdem generiert.
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)
Die Ereignisansicht zeigt auch die Ereignis-IDs 26328 und 26329 für das Datenleserkonto und das Aktionskonto an. Die Sitzungs-ID scheint auf das Datenleserkonto zu verweisen. Dem Datenleserkonto sind die Rollen „Operations Manager-Berichtsoperatoren“ und „Operations Manager-Berichtssicherheitsadministratoren“ zugewiesen.
Derzeit gibt es in der Konsole keine Warnung. Aber vor der Neuinstallation erhielt ich auch eine Warnung, dass keine Verbindung zu \ssrs hergestellt werden konnte
Ich bin nicht sicher, was genau den Alarm auslöst. Es ist nicht das Ereignis. Für jede Hilfe zur Lösung dieses Problems bin ich dankbar. Ich habe bei meiner Online-Suche nichts Konkretes gefunden.
SSRS: Instanz kann keine Verbindung zum SSRS Report Manager herstellen
Instance cannot connect to SSRS Report Manager.
PortalStatusCode: 200
Portal Error Message:
Http Status Code:
REST Status Code: 500
REST Service Error Message:
SSRS: Instanz kann keine Verbindung zum SSRS-Webdienst herstellen
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:
Zusätzliche Protokolle von Berichtsdiensten:
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 ---;
Antwort1
Nachdem ich tagelang an dem Problem herumgebastelt hatte, fand ich es endlich heraus. Durch das Einschalten des HTTP-Protokolls des Berichtsservers konnte ich sehen, was passierte.
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) - - -
Es scheint, dass das SQL Server Reporting Services Management Pack das lokale Systemaktionskonto verwendet hat. Als ich dies erkannte, konnte ich die entsprechenden Änderungen vornehmen, sodass das Data Reader-Konto verwendet wurde, um festzustellen, ob SSRS verfügbar war oder nicht. Ich wünschte, das Folgende wäre als Konfigurationsbedarf in derDokumentation. Falls es irgendwo erwähnt wird, habe ich es nicht gesehen.
- Gehe zuVerwaltung-->Ausführen als Konfiguration-->Profile
- Suchen nach „Microsoft SQL Server Monitoring Run As Profile“
- Hinzufügen eines „Ausführen als“-Kontos
- Kontoname: Data Warehouse-Berichtbereitstellungskonto
- Eine ausgewählte Klasse, Gruppe oder ein Objekt: Objekt
- Suchen Sie nach: MSSQL Reporting Services: Instanz (Native Mode)
- Filtern nach:
- Fügen Sie den entsprechenden verfügbaren Artikel hinzu
- Klicken Sie auf „OK“ und speichern Sie
Sobald ich dies getan hatte, verschwanden alle Warnungen und Ereignisse in der Konsole.