HP-synchronizer – FAILED_TO_DOWNLOAD_ATTACHMENT
Question ID: 107141
0
0

In HP-Synchronizer, the full synchronization in one of the links is failing with following error:

Update: threw an exception,skipping this entity and moving to the next, exception:server.Attachments.FAILED_TO_DOWNLOAD_ATTACHMENT : Failed to download attachment RE DESKTOP_AND_PORTALS#4169 – Imperial_QA Same Maintenance event are appearing twice under Current and Planned Events and Maintenance History Tab on Event Board window.msg to directory C:\\Program Files\\HP\\HP ALM Synchronizer\\tmp\\link904. Error: fetchAttachment: Failed to copy attachment file C:\\Users\\SVC_HP~1\\AppData\\Local\\Temp\\TD_80\\kstlmqcau01\\0ccd8143\\Attach\\BUG\\4169\\BUG_4169_RE DESKTOP_AND_PORTALS#4169 – Imperial_QA Same Maintenance event are appearing twice under Current and Planned Events and Maintenance History Tab on Event Board window.msg to location C:\\Program Files\\HP\\HP ALM Synchronizer\\tmp\\link904\\RE DESKTOP_AND_PORTALS#4169 – Imperial_QA Same Maintenance event are appearing twice under Current and Planned Events and Maintenance History Tab on Event Board window.msg

Our link has been working fine all week, now this…

Can you please help?

Marked as spam
Posted by (Questions: 193, Answers: 14)
Asked on October 6, 2016 3:50 pm
139 views
Answers (1)
0
Private answer

This attachment file:

RE DESKTOP_AND_PORTALS#4169 - Imperial_QA Same Maintenance event are appearing twice under Current and Planned Events and Maintenance History Tab on Event Board window.msg

Has a very long filename.

Sync uses the QC API which uses the TD80 temp folder to hold the attachment temporarily, then it copies it to the C:Program FilesHPHP ALM Synchronizertmp folder before sending it to the JIRA location.

Perhaps that filename + path is too long, or the C: drive is out of space. How much free space is on drive C:?

What happens if you rename the attachment to a simple very short name?

Go into QC project with IE, Download attachment from QC to local drive (on your laptop), rename it to a simple name (8.3) and re-attach to the same defect or to a NEW one and run sync to see if attachment goes across.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on October 6, 2016 3:51 pm
0
Resolved after trimming the file name
( at October 6, 2016 3:54 pm)
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

X
Scroll to Top