Error in opening a CR when there is mismatch between the number of actual attachments and value of attachments.

0 Likes

Problem:

Error in opening a CR when there is mismatch between the number of actual attachments and value of attachments.

Resolution:

  • Product Name: StarTeam
  • Product Version: 2005 R2
  • Product Component: Server
  • Platform/OS Version: All

Question:

Error in opening a CR when there is mismatch between the number of actual attachments and value of attachments.


Answer:

The Attachment Count mismatch happens because of unstable network connection or network failure. The data corruption happens by data submission under reconnect condition if Reconnect timeout is enabled. There is an existing CR# 36733 for this issue. The CR is addressed in the CPC Build# 9.0.0.174.

The recommended workaround is as follows:

1. Shutdown StarTeam configuration.

2. Backup database and repository.

3. Start StarTeam configuration.

4. Open Project with problematic CRs.

5. Select Project > Properties menu and Editors tab.

6. De-select Use Alternate Property Editor for Change Requests. | Click Ok

7. Click the Change Request tab.

8. Select Change Requests > Filters > Show Fields menu.

9. Add Attachment Count and Attachment Name fields to the display and move the close to the CR Number field.

10. Notice how the Attachment Count does not match the list of Attachment Names for the problematic CRs.

11. Open Properties of a problematic CR.

12. Click Attachments tab.

13. Save the current attachment files to a safe location so that they can be re-added later.

14. Add a dummy attachment - some text file that you will delete in a later step. | Click OK.

15. Re-open that same CR.

16. Click Attachments tab.

17. Select the newly added dummy attachment and click Remove. | Click OK.

18. Repeat steps 15 through 17 until Attachment Count is zero and no attachments are listed.

19. Re-open the CR, add back the saved attachments to the CR and click OK.

20. Repeat steps 11 through 19 for each problematic CR.

21. Select Project > Properties menu and Editors tab.

22. Select Use Alternate Property Editor for Change Requests. | Click OK.

23. Attempt to open problematic CRs. The problem should now be resolved.

24. Repeat steps 4 through 23 for each project that is known to have problematic CRs.


Author: Rehan Haque

Updated by: Nuala Comiskey

Old KB# 27772
Comment List
Related
Recommended