Search

Team Foundation server 2012 by jclarkson

Closed
as Fixed Help for as Fixed

2
0
Sign in
to vote
Type: Bug
ID: 779130
Opened: 2/13/2013 4:48:53 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
We have Visual Studio installed on our Team Foundation server and since installing the Visual Studio Update 2 CTP onto this server we have lost the ability to update workitems from the web portal i.e dragging tasks between swimlanes on kanban board. The error that is received is

◾TF400898: An Internal Error Occurred

This is not stopping us working as we can still update work items through visual studio and also through the old sharepoint portal.
Details (expand)

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

Team Foundation Server 2012

Steps to reproduce

Install Visual Studio 2012 update 2 CTP onto Team Foundation Server 2012.
Try and view or amend workitems through web access

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

◾TF400898: An Internal Error Occurred

Expected results

Workitem to be viewable and editable
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/15/2013 at 9:42 AM
James, thank you for taking the time to talk with us this morning.

We think what we have here is an issue when VS and TFS are installed side-by-side on the same box. The VS Update 2 - CTP3 updated some client DLLs impacted the server installation.

We are investigating the bug, so we can fix this for the final release of VS Update 2. Thank you very much for reporting it.

Your workaround is to unintall VS Update 2 - CTP3.
Posted by Microsoft on 2/14/2013 at 10:11 AM
James, thank you for submitting this bug, and for being willing to talk with us on the phone. We will be contacting you via phone tomorrow (2/15).

Gregg Boer - TFS Product Team
Posted by Microsoft on 2/13/2013 at 4: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.