The TFS Object Model logs various events to the Windows event log to signal connectivity issues with TFS. This monitor watches for these events and sets the health state of TFS Collection instance based on these events.
The monitor will automatically reset the health state to Healthy when connectivity to TFS is restored. You can see the monitor health history to analyze past connectivity issues.
This monitor controls the health state of TFS Collection instance and generates alerts related to TFS connectivity, when new TFS work items are created:
1101 "TFS Object Model is not installed on the server"
1102 "Team Foundation services are not available from server (url)"
1104 "TF30063: You are not authorized to access <server>"
TF26193: The team project does not exist. Check the team project name and try again.
Any other TFS errors or module failures that have "TF[N]", where "N" stands for the TFS Object Model error code.
The "TFS collection was not found" alert might occur when the template was manually deleted. The Operations Manager administrator needs to delete "System Center TFS Work Item Synchronization Management Pack" using the Operations Manager console.
If you see "TFS Object Model is not installed on the server", you need to install TFS Object Model on all servers in the selected machine pool. For more information, see
TFS Object Model download page.
If you see "Cannot access "TFS server", verify that your TFS server is running and accessible from all servers in the machine pool that are selected in the template.
If you see "TFS projects access denied" or any other TFS security error, the account specified in the template does not have sufficient rights to access the TFS project. Grant the account user the required TFS permissions to view projects and create/modify work items.
The "TFS collection was not found" alert might occur when the template was manually deleted. The Operations Manager administrator needs to delete "TFS Work Item Synchronization Management Pack" using the Operations Manager console