Verify the synchronization process for TFS-Project Server integration

TFS 2015 | TFS 2013


TFS 2017 and later versions no longer support native integration with Microsoft Project Server. If you upgrade to TFS 2017 or want to use a third party option, see Synchronize TFS with Project Server.

If you suspect that the data in Visual Studio Team Foundation Server and Microsoft Project Server is not synchronizing as you expect, you can review the following checklist to verify or troubleshoot operations.

  • Resolve post-installation and configuration issues. If you configure the two server products but synchronization does not start as you expect, you can review the following configuration elements:

  • Verify the health of the synchronization engine: If synchronization had been performing as you expect before a problem occurred, you can perform the following procedures:

    • Check synchronization messages. By using the /GetSyncMessages option of the TFSAdmin ProjectServer command-line tool, you can display the errors that were logged most recently for a project collection. For more information, see View error messages.

    • Review how fields get updated. If you find that one or more fields are not being updated as you expect, review the information in Understand how updates to specific fields are managed. In particular, you might discover why a field is not being updated even though no synchronization messages are being logged. The data type of the field, the OnConflict attribute for mapping fields, and the task hierarchy affect how the synchronization engine updates specific fields.

    • Review the synchronization process. You can manage the integration of the two server products more effectively if you understand how the synchronization engine manages the flow of data between them. The engine synchronizes data in three ways. It captures and updates task-related and resource-related data in both server products while respecting the ownership of data by the project manager in the project plan. For more information, see Synchronization process overview.

    • Check known issues and workarounds. If an error appears, you can determine whether you have encountered a known issue and whether a workaround has been identified. For more information, see Known issues and workarounds.

    • Verify that the Team Foundation Background Job Agent is running. For more information, see Stop and start services, application pools, and websites.

    If you have reviewed these suggestions and you still suspect a problem, visit the following forum on the Microsoft website: Team Foundation Server and Project Server Integration.

Known issues and workarounds
Administer TFS-Project Server integration