1
votes

Does anybody have any experience with TFS no longer letting somebody queue a new build?

Everybody else on my team can still queue new builds, but when i try to, it shows a little red 'x' as tho it can't connect to that part of the server.

I'm still able to check in/out code and get latest versions, but I can no longer queue up the builds.

There have been no recent configuration changes on my machine that would not have also been preformed on all other team machines. I have the proper security to access the builds and queue new ones.

I've tried every from of restarting/reconnecting to the server short of re-installing visual studio.

Anybody have any ideas on this?

3
Can you do it from Team System Web Access or does it affect VS only? - Richard Berg
I'm not familiar with Team System Web Access. - jblaske

3 Answers

2
votes

The problem stemmed from the Team Foundation package being shut off.

First, Close Visual Studio

Then, in the Visual Studo Command Prompt Run the command

devenv /ResetSkipPkgs

And you will be ready to go when you open visual studio back up.

0
votes

Is the build agent down? Meaning the server that is actually running the build is offline or shutdown? If the build agent is unreachable you will get the behavior you are experiencing. Check if its down by going into team explorer then right clicking on builds and then left clicking on manage build agents from the context menu. I am assuming you are dealing with TFS 2008.

0
votes

Red X on a single user almost always means a permissions problem when talking about the Documents or Reports nodes, but would be quite strange for Builds. My guess is some sort of connectivity problem, such as an errant proxy. I'd use Fiddler2 to troubleshoot. (granted, you have to have some idea what "normal" Fiddler traces look like -- maybe diff your traces against one of your coworkers who doesn't have the issue)