OpsMgr Agent Discovery Hanging after Enabling Broker Service?
When OpsMgr discovery hangs it’s because the SQL Broker service has not been enabled in the operationsmanager database. Just a quick BING search will show you tons of hits about this issue – and I’ve never seen one case where this wasn’t the case – until now. I just finished working an issue where OpsMgr discovery would hang but the SQL Broker service was enabled. I didn’t know much about the Broker service and definately had never had to troubleshoot it before. What is the SQL Broker service? MSDN offers the following statement to describe what Broker does. A more complete discussion can be found at http://msdn.microsoft.com/en-us/library/ms166043(SQL.90).aspx This new technology, a part of the Database Engine, provides a message-based communication platform that enables independent application components to perform as a functioning whole.
Here is the original post:
OpsMgr Agent Discovery Hanging after Enabling Broker Service?
