Troubleshooting

The following section lists the error codes that can be displayed from TeamPulse.

 

 

Error Code Message Description
TTP20001 TeamPulse Host URL has not been set and is required for synchronization of attachments. To enable synchronization of attachments, enter Host URL on the TeamPulse Settings screen. To disable it set SyncAttachments = false on the Edit Synchronization Mappings screen. See User Guide for more details.

This error can arise if attachment syncing is turned on for your project and the TeamPulse Host URL is not set.  The host URL is required so that links back into TeamPulse can be built correctly.

 

For more information, see Attachment Linking.

TTP20002 Could not find TeamPulse entity definition for '{0}'. This error can arise if an entity definition could not be found in the project settings for a TeamPulse work item type that is mapped to a TFS work item type.
TTP20003 Could not find TFS entity definition for '{0}'. This error can arise if a work item type definition could not be found in TFS for a work item type that is mapped to a TeamPulse work item type.
TTP20004 The allowed values for the Status/State field for the TeamPulse '{0}' entity and the TFS '{1}' work item type do not match.

This error can arise when the statuses for a TeamPulse work item type and the states for a mapped TFS work item type do not match exactly.  The statuses and states must match because in order to support a well-defined workflow, when syncing to or from TFS, each state transition is replayed in the exact order it occurred in either TeamPulse or TFS.

 

For more information, see Configuring Synchronization.

TTP20005 The allowed transitions for the Status/State field for the TeamPulse '{0}' entity and the TFS '{1}' work item type do not match.

This error can arise when the workflow transitions for a TeamPulse work item type the mapped TFS work item type do not match exactly. The transitions must match because in order to support a well-defined workflow, when syncing to or from TFS, each state transition is replayed in the exact order it occurred in either TeamPulse or TFS.

 

For more information, see Configuring Synchronization.

TTP20006 Multiple ({0}) field mappings found on TeamPulse entity {1} for TeamPulse field name {2}. This error can occur if the same field of a TeamPulse work item type is mapped to more than one TFS field.  Field mappings are always one-to-one.
TTP20007 Multiple ({0}) field mappings found on TeamPulse entity {1} for TFS field name {2}. This error can occur if the same field of a TFS work item type is mapped to more than one TeamPulse field. Field mappings are always one-to-one.
TTP20008 {0} for TeamPulse entity {1} is mapped to both rich text and plain text fields. Please map to only 1 text type for this field.

Some fields in TeamPulse (such as the description of a story) are stored as both plain text and rich text.  Depending on the fields available in the TFS work item type, it is possible to sync either the plain text or the rich text to TFS, but never both at the same time.  This error can occur if both the plain text and the rich text version of a TeamPulse field are mapped to a TFS field.

 

For more information, see Editing the Synchronization Mappings.

TTP21001 Project with ID '{0}' does not exist on this TeamPulse server.

This error can occur if the ProjectID attribute of the <SyncConfiguration> element in the sync mappings XML is set to a number that does not correspond to a Project ID of any project on the TeamPulse server.  The ProjectID value is auto-populated by the system and should not be changed.

 

Care must also be taken when copying sync mappings from another project because the value of the ProjectID attribute must be changed to that of the TeamPulse project the sync mappings are for.

 

For more information, please see Editing the Synchronization Mappings.

TTP21002 Entity type '{0}' does not exist in TeamPulse.

This error can occur if the TeamPulseEntityName of an <EntityMapping> element in the sync mappings XML does not correspond to a valid TeamPulse entity type name.  The only valid values are Story, Task, Bug, Issue, and Risk.

 

For more information, please see Editing the Synchronization Mappings.

TTP21003 '{0}' is not a syncable field for entity '{1}'.

This error can occur if the TeamPulseFieldName of a <FieldMapping> element in the sync mappings XML does not correspond to a TeamPulse field that can be synced to TFS.  This error will be shown if the field name does not exist in TeamPulse or if the field is not syncable.

 

For a list of all the syncable fields, see Editing the Synchronization Mappings

TTP21004 Cannot sync entities of type '{0}' because no entity mapping was found with TeamPulseEntityName="{0}".

This error can occur if you click the "Sync item now" button to sync a single item and there is no entity mapping for the type of TeamPulse entity you tried to sync.

 

An entity mapping is required because it defines which TFS work item type the TeamPulse entity maps to as well as which TeamPulse fields map to which TFS fields.

 

For more information, see Configuring Synchronization and Editing the Synchronization Mappings.

TTP21005 Expected '{0}' as TeamPulseFieldType but got '{1}' for field mapping with TeamPulseFieldName '{2}' in entity mapping with TeamPulseEntityName '{3}'.

This error can occur if an incorrect value is specified for the TeamPulseFieldType attribute in a FieldMapping element.  The value for the TeamPulseFieldType attribute must match the actual type of the TeamPulse field being mapped.

TTP22001 Project named '{0}' does not exist on TFS server '{1}'.

This error can occur if the TfsProjectName specified in the <ConfigSettings> section of the sync mappings XML does not correspond to a project that exists on the TFS server.  This value is auto-populated by the system and should not be changed.  The error can also arise if the TFS project is deleted.

 

Care must also be taken when copying sync mappings from another project because the value of the ProjectID attribute must be changed to that of TeamPulse project the sync mappings are for.

 

For more information, please see Editing the Synchronization Mappings.

TTP22002 Work item type '{0}' does not exist in project '{1}'.

This error can occur if the DestinationEntityName of an <EntityMapping> element in the sync mappings XML does not correspond to a work item type in the TFS project that the TeamPulse project is mapped to.

 

This error is most likely a result of one of these two scenarios:

1) The TFS project has a custom work item type which is being mapped to a TeamPulse work item type and the name of the custom TFS work item type was typed incorrectly.

2) The default mappings created by the system do not correctly match up with the work item types available in the mapped TFS project.  When connecting a TeamPulse and TFS project for syncing, the value chosen in the TFS Process Template drop-down is used to create default mappings.  If the TFS project has been customized or the wrong value is chosen from this drop-down, the mappings created by the system may be incorrect.  To resolve the error, go to the Edit Synchronization Mappings screen and manually modify the mappings.

 

For more information, see Choosing a TFS Project to Synchronize With and Editing the Synchronization Mappings.

TTP22003 Field '{0}' does not exist in work item type '{1}'.

This error can occur if the DestinationFieldName of a <FieldMapping> element in the sync mappings XML does not correspond to a field that is available on the mapped TFS work item type.

 

This error is most likely a result of one of these two scenarios:

1) The TFS work item type has custom fields which are being mapped to a TeamPulse field and the reference name of the TFS field was typed incorrectly.

2) The default mappings created by the system do not correctly match up with the fields available in the mapped TFS work item type. When connecting a TeamPulse and TFS project for syncing, the value chosen in the TFS Process Template drop-down is used to create default mappings. If the TFS work item types have been customized or the wrong value is chosen from this drop-down, the mappings created by the system may be incorrect. To resolve the error, go to the Edit Synchronization Mappings screen and manually modify the mappings.

 

For more information, see Editing the Synchronization Mappings.

TTP22004 Could not find query '{0}' in project '{1}'.  Ensure that the query exists and is visible to everyone.

This error can occur if a <ConfigSetting> element with a key of TfsQuery is added to the sync mappings XML and the value does correspond to a path to a TFS query in the mapped TFS project.  The error could also be a result of the permissions applied to the query.

 

For more information, see Using a TFS Query.

TTP22005 Expected '{0}' as DestinationFieldType but got '{1}' for field mapping with DestinationFieldName '{2}' in entity mapping with DestinationEntityName '{3}'.

This error can occur if an incorrect value is specified for the DestinationFieldType attribute in a FieldMapping element.  The value for the DestinationFieldType attribute must match the actual type of the TFS field being mapped.

 

TFS 2012 Upgrades

Another way this error occurs is if a TFS server is upgraded from TFS 2010 to TFS 2012. In TFS 2012 the System.Description field has been changed to be of type 'html'. To fix this error, change the field mapping as follows:

  1. Change the DestinationFieldType to html
  2. Use the 'rich text' version of the TeamPulse field (if available)
    • Change the TeamPulseFieldName to DescriptionRichText
    • Change the TeamPulseFieldType to richtext

 

These changes should result in a field mapping that looks like this:

<FieldMapping TeamPulseFieldName="DescriptionRichText"
TeamPulseFieldType="richtext" DestinationFieldName="System.Description"
DestinationFieldDisplayName="Description" DestinationFieldType="html" />