locked
Error when loading Visual Studio after installing October Power Tools

    Question

  • Hi,

    I've installed the October edition of the TFS Power Tools (after uninstalling the July edition) and now this strange error pops up everytime I start Visual Studio.

    "Team Foundation error

    Specified cast is not valid"

    It seems to occur as Team Explorer is loading all the Team Project objects.  Downgrading to the July edition makes the error dissappear.

    Has anyone else experienced this and knows what the problem might be?

    Thanks.
    Monday, December 15, 2008 1:40 AM

Answers

  • It seems to be an error in the integration to Microsoft Office Communicator, if I disable the integration to this, I do not get an error.

    I can start up VS2008 without errors, but if I re-anable the integration, the error comes right away.

    Suggested solution / workaround:
        1.       From
    Team Explorer, right click ’Team Members’
        2.       Click ’Personal Settings’
        3.       In Collabaration, Provider click Change
        4.       Change to 
    <None>

    • Marked as answer by Hua Chen Monday, February 23, 2009 2:38 AM
    Friday, February 20, 2009 8:57 AM
  • Hello Gishmibop,

       Sorry for the inconvenience.

       I have tested several settings, I cannot re-produce the same issue

       I have also searched widely, it seems to be a new problem.

       here is an link of the October Release on Power Tools.

        http://blogs.msdn.com/bharry/archive/2008/11/08/oct-08-tfs-power-tools-are-available.aspx

       Thanks.
    Please mark the replies as answers if they help and unmark them if they provide no help
    • Marked as answer by Bill.Wang Wednesday, December 24, 2008 7:10 AM
    • Unmarked as answer by Bill.Wang Wednesday, December 24, 2008 7:10 AM
    • Marked as answer by Hua Chen Wednesday, December 24, 2008 7:13 AM
    Friday, December 19, 2008 3:44 AM
  • Hi,

    I have exactly the same error. I also heard of this from another colleague using a different foundation server.

    I have VC6.0, VS2005 pro, VS2008 pro (not a team edition) on my computer. VS2008 was installed with SP1, then team explorer, then SP1 re-installed.
    Finally I installed the power tools from October. I have not had any other versions of power tools installed.

    My colleague is using a team edition version of VS2008.

    Hope this can help to provoke the error.

    Thanks.
    • Proposed as answer by Alan Hauge Friday, February 20, 2009 8:44 AM
    • Marked as answer by Hua Chen Monday, February 23, 2009 2:37 AM
    Wednesday, February 18, 2009 8:21 PM

All replies

  • Hello Gishmibop,

       Sorry for the inconvenience.

       I have tested several settings, I cannot re-produce the same issue

       I have also searched widely, it seems to be a new problem.

       here is an link of the October Release on Power Tools.

        http://blogs.msdn.com/bharry/archive/2008/11/08/oct-08-tfs-power-tools-are-available.aspx

       Thanks.
    Please mark the replies as answers if they help and unmark them if they provide no help
    • Marked as answer by Bill.Wang Wednesday, December 24, 2008 7:10 AM
    • Unmarked as answer by Bill.Wang Wednesday, December 24, 2008 7:10 AM
    • Marked as answer by Hua Chen Wednesday, December 24, 2008 7:13 AM
    Friday, December 19, 2008 3:44 AM
  • Hi,

    I have exactly the same error. I also heard of this from another colleague using a different foundation server.

    I have VC6.0, VS2005 pro, VS2008 pro (not a team edition) on my computer. VS2008 was installed with SP1, then team explorer, then SP1 re-installed.
    Finally I installed the power tools from October. I have not had any other versions of power tools installed.

    My colleague is using a team edition version of VS2008.

    Hope this can help to provoke the error.

    Thanks.
    • Proposed as answer by Alan Hauge Friday, February 20, 2009 8:44 AM
    • Marked as answer by Hua Chen Monday, February 23, 2009 2:37 AM
    Wednesday, February 18, 2009 8:21 PM
  • It seems to be an error in the integration to Microsoft Office Communicator, if I disable the integration to this, I do not get an error.

    I can start up VS2008 without errors, but if I re-anable the integration, the error comes right away.

    Suggested solution / workaround:
        1.       From
    Team Explorer, right click ’Team Members’
        2.       Click ’Personal Settings’
        3.       In Collabaration, Provider click Change
        4.       Change to 
    <None>

    • Marked as answer by Hua Chen Monday, February 23, 2009 2:38 AM
    Friday, February 20, 2009 8:57 AM
  • Thanks, Gishmibop.  I was starting to think I had done something to one of the process templates, but that makes sense about it being the October 2008 TFS Power Tools because that's when it started showing up for me too.
    Tuesday, March 10, 2009 5:57 PM
  • I have started getting the same error after I my PC was updated to XP SP3. (Large corporate IT often lags a bit behind :-)

    Assuming office connection is through "Office Communicator 2007 R2"

    Version info
        VS2008 Professionl SP1 (307299)
    Plugins
        TeamExplorer also 30729
        VS 2008 Tools for Office (no version available)
        10 VS HotFix starting from KB944899 to KB948127
        5 TeamExplorer hotfix starting from 946260 To KB948816

    Vent back to a spare PC with same configuration, but still running SP2 to check, and it doesnt show this error

    VS2010 B2 does not show this problem either. (If autoconnects to TFS, which i belive VS2009 did once, but hasen't done for a logn time)

    Hope this may shed a bit more light :-)

    regards Henrik
    Friday, December 18, 2009 9:50 AM