Error 31569
WelchMarch 25, 20154 0 0 0 Today I worked with a user…a smart user. He told me a story I'd heard before - "I didn't touch anything butSCOM broke!" -and is not allowed to access data warehouse under login I have to say this time I believed him…. Basically out of management group with id is not allowed to access data warehouse under login the blue, his management servers (MS) were unable to talk to the DW. And when we looked thru the events below, we noticed that the MSwere trying to use the SCOM Action Account instead of the Data Warehouse action accounts. The OpsDB appeared fine, the console ran, and agents were communicating with the management group. Errors seen on the Management Servers Log Name: Operations ManagerSource: Health Service ModulesEvent ID: 31557Task Category: Data WarehouseLevel: ErrorDescription: Failed to obtain synchronization process state information from Data Warehouse database. The operation will be retried.Exception ‘SqlException': Management Group with id "xxxx" is not allowed to access Data Warehouse under login "[ID]" One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.MaintenanceMode Instance name: Data Warehouse Synchronization Service Instance ID: {xxx} Management group: [name] +++++++++++++++++Log Name: Operations ManagerSource: Health Service ModulesEvent ID: 31561Task Category: Data WarehouseLevel: ErrorDescription: Failed to enumerate (discover) Data Warehouse objects and relationships among them. The operation will be retried.Exception ‘SqlException': Management Group with id "xxxx" is not allowed to access Data Warehouse under login "[name]" One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Discovery.StandardDataSet Instance name: Alert data set Instance ID: {xxx} Management group: [name] +++++++++++++++++ Log Name: Operations ManagerSource: Health Service ModulesEvent ID: 31563Task Category: Data WarehouseLevel: ErrorDescription: Failed to enumerate Data Warehouse components for deployment. The operation will be retried.Exception ‘SqlException': Management Group with id ‘xxxx" is not allowed to access Data Warehouse under login "[name]" One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component Instance name: Data Warehouse Synchronization Service Instance ID: {xxx} Management group: [name] +++++++++++++++++Log Name: Operations ManagerSource: Health Service ModulesEvent ID: 31569Task Category: Data WarehouseLevel: ErrorDescription: Report deployment process failed to request management pack list from Data
OparnicaJanuary 30, 20150 0 0 0 Hi, I have faced with issue with Report deployment and event: Log Name: Operations ManagerSource: Health Service ModulesDate: 01/01/2015 3:07:42 PMEvent ID: 31569Task Category: Data WarehouseLevel: ErrorKeywords: ClassicUser: N/AComputer: xxxx.xxxx.xxxxDescription:Report deployment process failed to request management pack list from SQL RS Server. The operation will be retried.Exception 'SoapException': https://blogs.msdn.microsoft.com/nicole_welch/2015/03/errors-connecting-to-the-data-warehouse-health-service-module-events-31557-31561-31563-31569/ An internal error occurred on the report server. See the error log for more details. --> An internal error occurred on the report server. See the error log for more details. --> Access is denied. (Exception from HRESULT: https://blogs.technet.microsoft.com/predrag_oparnica/2015/01/30/31569-health-service-modules-soapexception-0x80070005/ 0x80070005 (E_ACCESSDENIED)) One or more workflows were affected by this. ……. Resolution Added the SDK (Data Access) account to the Windows Authorization Access Group (ManagementServer$ if you are using LocalSystem for SDK account) Tags 0x80070005 31569 SoapException Comments (0) Cancel reply Name * Email * Website Follow UsPopular TagsSCOM Upgrade Certificates ACS script 31569 /ManagementServerInitiatesConnection authored reports Gateways reset monitors visible Error 25211 PowerShell PAL baselining Adrian Bliss 0x80070005 scom 2012 reporting SoapException Archives June 2016(2) December 2015(1) January 2015(1) August 2014(1) March 2014(1) February 2014(1) November 2013(5) July 2013(4) All of 2016(2) All of 2015(2) All of 2014(3) All of 2013(9) Privacy & Cookies Terms of Use Trademarks © 2016 Microsoft
SCOM generates errors 31555 and 31569 with a TypeLoadException exception SCOM, System Center The other day we saw another error on the SCOM RMS that looked familiar in some way, but of course I had lost the links to the KB articles. So what happens? We see these alerts coming from the event log and reflected in SCOM alerts: Data Warehouse configuration synchronization process failed to read data from the operational database. Failed to generate data to be forwarded to the Data Warehouse. The operation will be retried. Exception 'TypeLoadException': Could not load type 'System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Data Warehouse failed to request a list of management packs which contain reports deployed to SQL Reporting Services Server. Report deployment process failed to request management pack list from SQL RS Server. The operation will be retried. Exception 'TypeLoadException': Could not load type 'System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Especially look for the part where it says TypeLoadException. As there can be more types of exceptions why for instance the list of MPs from SRSS can not be retrieved. These errors come after some hotfixes released in June 2010 are run on the RMS. These are updates 982167 and 982168 .Net Framework 3.5 hotfixes that also touch the .Net Framework 2 feature layer. If you run into this go to http://support.microsoft.com/kb/2262911/en-us. That article ponts to a hotfix 975954 which can be found here http://code.msdn.microsoft.com/KB975954/Release/ProjectReleases.aspx?ReleaseId=3839. After that run the fix mentioned in the 2262911 article or manually run msiexec /f {C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F} in order to make all features in the .NET Framework 2.0 SP2 product to reevaluate its installation state. Reboot when it asks for reboots. Bob Cornelissen No feedback yet Comment feed for this postLeave a commentYou must be a member of this blog to comment. Log in now!Comment text:You must be a member of this blog to comment. Preferred Products BICTT This blog is run by Bob Cornelissen, a System Center enthousiast for a number of years now and managing consultant for BICTT. I work daily with SCOM in designing, implementing, configuring and extending this great product. Also I work with SC