I have been getting this on a regular basis. OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: mccoy.FSBR.net Instance ID: {0C42CF41-4AD1-28F6-8AC7-618CCAD22ADA} Management group: MCCOY_MG These machines are running XP Pro with 2 GB of memory. I wouldn't think memory should be a problem with this. It seems when I get rid of one error message, another arrives tight behind it. Dorsn't seem to be problems with the machines as much as problems with the agents and/or program. An error occurred on line 120 while executing script 'MOM Backward Compatibility Service State Monitoring Script'Source: Microsoft VBScript runtime errorDescription: Out of memory One or more workflows were affected by this. Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring Instance name: ORIGINATION01.FSBR.net Instance ID: {C65D72BA-6DCF-63A7-2979-720A11035818} Management group: MCCOY_MG

Hi,To resolve this issue, enable SQL Server Service Broker. To do this, follow these steps at a time when the SCEServer services can be stopped:1. On the Management Server, open the Services.msc Microsoft Management Console (MMC) snap-in, stop the OpsMgr Health service, the OpsMgr SDK service, and the OpsMgr Config service.2. Start Microsoft SQL Server Management Studio on the Operations Manager database server or on a computer that has the SQL Server tools installed and that can connect to the Operations Manager database server.3. Click New Query.4. In the navigation pane, expand Databases, and then click OperationsManager.5. In the details pane, type the following command, and then click Execute:SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager'6. In the results that are displayed, verify the value that is displayed in the is_broker_enabled field. SQL Server Service Broker is disabled if this value is 0 (zero).7. In the details pane, type the following command, and then click Execute:ALTER DATABASE OperationsManager SET ENABLE_BROKERCheck for successful completion of the TSQL command. SQL Server Service Broker is now enabled.8. On the Management Server, restart the OpsMgr Health service, the OpsMgr SDK service, and the OpsMgr Config service.9. Close all open windows and dialog boxes.--------------------Regards,Eric Zhang

We get the same error message but this fix didn't help; The SQL Server Service Broker is already enabled (status=1). Any other thoughts?

I have the same issue. Did anyone ever come up with a fix? Is there someone moderating this forum still?????

Hi,Could you please check Event Viewer and post the error related to SCE?

I recieved the same error. Here is what I have in the Event's Manager Error Log: Event Type:WarningEvent Source:Health Service ModulesEvent Category:NoneEvent ID:11852Date:11/13/2008Time:10:47:25 AMUser:N/AComputer:CLENETMONDescription:OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: clenetmon.chart-ind.local Instance ID: {BE7E5B98-FF99-BFFC-1F6E-43354884A1CA} Management group: Chart For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Zhang:you haven't got a clue guy, this fix is not relavent to the problem

Help, I keep getting this message An error occurred on line 120 while executing script 'MOM Backward Compatibility Service State Monitoring Script' Source: Microsoft VBScript runtime error Description: ActiveX component can't create object One or more workflows were affected by this. Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoringHow can I fix.

JSB_MCSE - so - what is the solution? We are monitoring a server with SCOM Health Services Module - the service is running as Local System - we are attempting to check to make sure that the database connection is up. We get the following three events: Event Type: WarningEvent Source: Health Service ModulesEvent Category: NoneEvent ID: 11852Date: 6/18/2009Time: 12:16:26 PMUser: N/AComputer: ClientServerDescription:OleDb Module encountered a failure 0x80040e4d during execution and will post it as output data item. Workflow name: OleDbCheck_bc3665991d214fc7996db723ddba6c75.OpenTime Instance name: SQLServer ODBC Instance ID: {FC2CB169-1235-DEE2-3CF9-01314B51817C} Management group: Group Event Type: WarningEvent Source: Health Service ModulesEvent Category: NoneEvent ID: 11852Date: 6/18/2009Time: 12:16:26 PMUser: N/AComputer: ClientServerDescription:OleDb Module encountered a failure 0x80040e4d during execution and will post it as output data item. Workflow name: OleDbCheck_bc3665991d214fc7996db723ddba6c75.NoConnectionMonitor Instance name: SQLServer ODBC Instance ID: {FC2CB169-1235-DEE2-3CF9-01314B51817C} Management group: Group Event Type: WarningEvent Source: Health Service ModulesEvent Category: NoneEvent ID: 11852Date: 6/18/2009Time: 12:16:26 PMUser: N/AComputer: ClientServerDescription:OleDb Module encountered a failure 0x80040e4d during execution and will post it as output data item. Workflow name: OleDbCheck_bc3665991d214fc7996db723ddba6c75.InitTime Instance name: SQLServer ODBC Instance ID: {FC2CB169-1235-DEE2-3CF9-01314B51817C} Management group: Group

Hi, Please take a look at this post http://sentryboy.spaces.live.com/blog/cns!F2CBE6BAE5BB51E1!412.entry -- Anders BengtssonMicrosoft MVP - Ops Mgrwww.contoso.se

Hi.This solution from the MS KB article didn't help me. http://relatedterms.com/ViewThread.aspx?t=1751841talks about the RunAs account having the correct priviledges on the SQL DB. Will need to look into that.

Issue is happening for me to and the SQL Server Service Broker is already enabled (status=1). It started occurring after I moved the DB onto another server.

I am having the samwe issue as StephenLe. We moved the Database to a new SQL server to get better performance. Once we did this, the errors started. the system is working well, but I am getting this error...often.

check under the database properties of Scom operations manager database under option > service broker for that the value is true and if is still not working with you and keep rolling back to false you have to keep only single user for the database then you can add multi users after you finished The solution : SELECT IS_BROKER_ENABLED FROM SYS.DATABASES WHERE NAME = 'scomoperationsmanager' If the output is 0 then the broker is not enabled to the database, and the error will still appear, do the following: 1. The broker will not updated in the database options till you drop all the current sessions (connections) with the database. To do that run this query: a. alter database [scomoperationsmanager] set single_user with rollback immediate 2. The database is now single user, then run this query a. ALTER DATABASE [scomoperationsmanager] SET ENABLE_BROKER b. SELECT IS_BROKER_ENABLED FROM SYS.DATABASES WHERE NAME = 'scomoperationsmanager' c. The output must be 1 à to indicate that the broker is enabled. 3. Then return the database again to multiuser: a. alter database [scomoperationsmanager] set multi_user ---------------- ALL Thanks are to ALy el Nemr for his help

Hi Bryan, I figured out what the issue was (at least for me). I migrated the OperationsManager DB a while back to a new SQL server on a named SQL instance. I forgot to add the SQL instance in the registry and in the MT_ManagementGroup. After I added the instance name and bounced the System Center Data Access, Management and Management Configuration services all my DB related errors in the Operations Manager log on the RMS went away or turned to successful. The TechNet article http://technet.microsoft.com/en-us/library/cc540384.aspx for migrating the OperationsManager DB neglects to mention if your DB is on a named SQL instance (instead of SQLSERVER) then you need to add the instance in the MT_ManagementGroup table as well. Example: "SQLSERVER\SQLINSTANCE" I just wrote a blog post about it, for more details: http://www.blogmynog.com/2010/10/25/operationsmanager-database-connectivity-issues-after-migration/ Hope this helps!