Search

MTM test step attachment cannot be opened ("...is being uploaded") by Mat Kramer

Closed
as By Design Help for as By Design

1
0
Sign in
to vote
Type: Bug
ID: 778840
Opened: 2/8/2013 9:11:04 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Attempting to open a test step attachment, I get the error "attachment cannot be viewed, the attachment is being uploaded", see attached image. The test run is not currently opn on any computer and the attachment is not currently being uploaded.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Attach spreadsheet to a test step.
Attempt to open from another computer.
(We have not attempted to reproduce this - other attachments in the same results work OK.)

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

Error window. (attached)

Expected results

Attachment open in Excel.
File Attachments
File Name Submitted By Submitted On File Size  
cannot-open-test-attachment.PNG 2/8/2013 23 KB
Sign in to post a comment.
Posted by Microsoft on 3/17/2013 at 11:49 PM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 3/14/2013 at 1:21 AM
Did you tried after sometime when the upload was complete? During closing of mtm client did you see any upload dialog box?

Posted by Microsoft on 2/10/2013 at 6:48 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/8/2013 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.