The F5 Monitoring Service Data Source Singleton Error

Michael,

Definitely the account running the F5 Monitoring Service has to have read/write access to the F5_ManagementPack SQL database. One simple way you would set this up is to use the SQL Server Management Studio and suggested as follows. I'll use a generic name to point to your account running the F5 Monitoring Service e.g. 'f5acct'.

- Under the SQL Server instance hosting the F5_ManagementPack :: Security :: Logins :: look for the 'f5acct' account :: is there?

- if yes :: select 'f5acct' :: right click :: Properties :: User Mapping :: check/enable F5_ManagementPack :: check/enable 'db_owner' and 'public' for the related user roles.

- if not :: select Logins :: right click :: New Login :: enter login name :: Search 'f5acct' and point to it :: select 'User Mapping' :: check/enable 'F5_ManagementPack' :: check/enable 'db_owner' and 'public' for the related user roles.

The DBAs in your SQL Server environment may choose to further restrict this access to just 'read/write', and in this case the approach would be slightly different, but bottom line is, the F5 Monitoring Service account needs to have read/write access to the F5_ManagementPack database.

Also, make sure the SQL Service Broker is enabled for the OperationsManager SQL database. You can do this through the following SQL command.

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

In summary, according to Microsoft: the SQL Service Broker enables internal or external processes to send and receive guaranteed asynchronous messaging by using extensions to Transact-SQL. In distributed SCOM management server environments this service needs to be enabled.

Julian