Formula una domandaFormula una domanda
 

Con rispostaRed X on Build node

  • giovedì 17 aprile 2008 13.10Lone VVolf Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

     

    I am currently having a very annoying problem with Team Explorer 2008.  Everything was working fine, and today, I have a red X on every Build node.  That means I can't execute or update builds.  Note that I said "Build", and not "Builds".  Because for some reason, even the name is wrong!  Everything else works, including the interface in the Build Notification Power Toy.  The TFS Web Interface also works fine with my login.  If I login on another PC, it also works fine.  Just not working in my main development environment.  Please help!

Risposte

Tutte le risposte

  • venerdì 18 aprile 2008 6.28Lone VVolf Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta
    Uninstalling the power tools for TFS 2008 seems to have solved the problem.

     

  • lunedì 21 aprile 2008 20.10Jason BarileMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    Which power tools release did you have installed?
  • martedì 6 maggio 2008 10.56Lone VVolf Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    I had had the power tools for TFS 2005 installed, as well as the December release for TFS 2008.  I uninstalled both.

  • giovedì 8 maggio 2008 14.17Aris Extra Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

     

    I'm having the same issue and I tried what is posted here but still did not work for me. Any ideas why.

     

    I have visual studio 05 and 08 on my box, when I open 05 everything is ok but when I open 08 the build is not accessble too, please help.

  • venerdì 9 maggio 2008 10.53Fern82 Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    I'm having the same problem, but all my partners can see the Build node except me.

     

    I'm working with VS2005. Any idea???

     

    Thanks in advance.

     

  • giovedì 12 giugno 2008 16.05Steve Strelzyk_Cdw_ Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    I am having this problem now, and I have not installed any of the power tools.  This just happened, and I have no idea why.  I uninstalled/reinstalled Team Explorer, but it makes no difference at all.

     

  • giovedì 12 giugno 2008 16.12Aris Extra Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Can you try using a different machine and see if you encounter the same problem, if this does not happen on a differenct machine then most likely your profile/account on the box is corrupted and may have to rebuild it. That's how I resolve my issue. 

     

    I posted my solution here: http://notes.arisx.com/?p=80

     

  • martedì 17 giugno 2008 7.28Fern82 Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Risposta suggerita

    Hi all,

    I found a solution, first of all you should to rename the cache folder por Team Fundation "C:\Documents and Settings\BiztalkAdmin\Local Settings\Application Data\Microsoft\Team Foundation\1.0"

     

    Then execute this command line: Start > Run : “devenv /resetuserdata".

     

    With this you reset your VS user data, you must to be care with this because you will lose all your personal options for VS, but this solve the problem for me.

     

    I hope that this can help someone.

     

  • martedì 14 ottobre 2008 19.51TheSpoonsAreWatching Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Thanks Fern,

    I had the same problem but followed your instructions and now I have access to my Build node again.

  • martedì 27 ottobre 2009 18.44bpeikes Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    I'm having the same problem, but I do not want to reset all of my personal settings. I also don't think I have power tools. Any ideas as to what causes this problem?