다음을 통해 공유

Tasks not working?

  • 아티클

If you are experiencing any issue where notifications aren't working, which can manifest itself as the UI not having management pack related information updated or tasks never completing (like discovery), one thing to look at is broker settings in SQL. If you run the following command (replacing the database name with whatever you named the Operations Manager database):

SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'

The result should be 1. If it is not, you need to run the following to enable it:

ALTER DATABASE OperationsManager SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE

Warning: WITH ROLLBACK IMMEDIATE will terminate any currently running transactions, but the command needs exclusive access to the db, and thus is required.

Update: Dustin Hannifin also put up a post regarding this issue and running SQL Server with an account that does not have proper permissions on the SQL Brroker queue. This usually is caused by running SQL as a local user.

Comments

  • Anonymous
    April 25, 2007
    Dustins post mentions "This event is triggered when the SQL Service Broker does not have access to Active Directory". What is the broker querying from the AD exactly? Is this to suggest running SQL services in LocalSystem  context should not work?

  • Anonymous
    April 25, 2007
    The broker just needs to check permissions for the SDK service account against the queue. I am not entirely sure why this goes through a different code path than regular SQL authentication (windows in our case), but it does. Nonetheless, LocalSystem will work fine as this is considered the computer account in AD.