Hi I have an error on my SCE 2007 server Alert subscription data source module was unable to find alerts that match the subscription because of database errors. The following error(s) were encountered: Exception Message: A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.) One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectAlertData Instance name: myserver-name-here Instance ID: {6Exx1998-xxxx-29FB-58A1-D6xxxxxx41} Management group: myserver-name-here_group I got this when I rebooted the server due to windows updates. Anyone help? Thanks Paul

Ah I was looking for this error that I lost but I found it again- I also got this after reboot GetSQL2005BlockingSPIDs.vbs : Cannot login to database [myserver-name-here][MSSQLSERVER:master] And there is another that says this: 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: myserver-name-here Instance ID: {6Exx1998-xxxx-29FB-58A1-D6xxxxxx41} Management group: myserver-name-here_group They maybe related? ---- point to note---- I have 1 subscription only and I AM receiving alerts. Thanks Paul

Hi Paul, For this error: 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: myserver-name-here Instance ID: {6Exx1998-xxxx-29FB-58A1-D6xxxxxx41} Management group: myserver-name-here_group Please try the following steps: 1. On the Management Server, open the Services.msc Microsoft Management Console (MMC) snap-in, a. stop the OpsMgr Health service, b. stop the OpsMgr SDK service, c. stop the OpsMgr Config service. Note: if you don't stop the services before you run the query it executes forever (hangs). 2. Start Microsoft SQL Server Management Studio on the Operations Manager database server or on a computer that has the SQL Server tools installed a. Connect to the Operations Manager database server. b. Click New Query. c. In the navigation pane, expand Databases, and then click OperationsManager. d. In the details pane, type the following command, and then click Execute: i. SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager' e. 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). Note: even if the SQL Server Service Broker is enabled, I would suggest that you proceed to next step. f. In the details pane, type the following command, and then click Execute: g. ALTER DATABASE OperationsManager SET ENABLE_BROKER h. Check for successful completion of the TSQL command. SQL Server Service Broker is now enabled. 3. On the Management Server, a. Start the OpsMgr SDK service. b. Start the OpsMgr Health service. c. Start the OpsMgr Config service. 4. Close all open windows and dialog boxes.

As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as Answered as the previous steps should be helpful for many similar scenarios. If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. In addition, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks!

Hi Eric, We have two management servers in our envoirnment for load balancing, 50% servers are on scom02 and rest 50% are on scom03. RMS server is scom01 and Iam getting the same error on my scom01 server. As per your solution above, should I stop the mentioned services on both the management servers ? Please Help!!!