An alert couldn't be inserted to the database. This could have happened because of one of the following reasons: - Alert is stale. The alert is generated by an MP recently deleted. - Database connectivity problems or database running out of space. - Alert received is not valid. The following details should help to further diagnose: %1.
An agent pending action was created. Agent name: %1 Management server name: %2 Pending action type: %3 Pending action data: ...
An agent pending action was created. Agent name: %1 Management server name: %2 Pending action type: %3 Pending action data: ...
An agent was rejected. Current security settings do not allow the automatic insertion of agents. Change either the security ...
An agent was rejected. Current security settings do not allow the automatic insertion of agents. Change either the security ...
An alert couldn't be inserted to the database. This could have happened because of one of the following reasons: - Alert ...
An alert couldn't be inserted to the database. This could have happened because of one of the following reasons: - Alert ...
An application with the name "{0}" has already been added to this application group. To configure "{0}" at "{1}" for monitoring ...
An attempt was made to load the component assembly '{0}' with an unmatched declared qualified name '{1}', the management ...
An Audit Forwarder disconnected. Name: %1 DbId: %2 Value: %3 Reason: Collector disconnected the forwarder because it is busy. ...