Team System Developer Center > Visual Studio Team System Forums > Team Foundation Server - General > tfsbuild.exe errors when trying to start a build (beta 3)
Ask a questionAsk a question
 

Answertfsbuild.exe errors when trying to start a build (beta 3)

  • Tuesday, January 10, 2006 5:17 PMJoeyBB Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I can start the build manually through team explorer but when trying to do so via the command line using tfsbuild on the build box i get the following error. I tried putting the url in quotes and using fqdn as well. Any thoughts? Is there another console app that i can use in conjuction with windows schedular to kick off a build?

    C:\Program Files\Microsoft Visual Studio 8\Common7\IDE>"C:\Program Files\Microsoft Visual Studio 8\C
    ommon7\IDE\TFSBuild.exe" start http://6nytp71:8080 ProjectX ProjectXBuild
    Microsoft (R) TfsBuild Version 8.0.0.0
    for Microsoft (R) Visual Studio 2005 Team System
    Copyright (C) Microsoft Corporation 2004. All rights reserved.


    Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an ob
    ject.
       at Microsoft.TeamFoundation.Build.Common.WebServiceUrls.GetServerUrl(String server)
       at Microsoft.TeamFoundation.Build.CommandLine.TeamBuild.StartBuild(StartBuildParameters startBuil
    d)
       at Microsoft.TeamFoundation.Build.CommandLine.CommandLineBuild.StartCommand()
       at Microsoft.TeamFoundation.Build.CommandLine.CommandLineBuild.Main(String[] args)

    C:\Program Files\Microsoft Visual Studio 8\Common7\IDE>

     

Answers

  • Wednesday, January 11, 2006 4:21 PMJoeyBB Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    I disassembled the code in the error message and it's looking for the servers in this key - HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers.

    I added a new string value with the non-fqdn name of the server (6nytp71) as the name and the actual url ( http://6nytp71:8080 ) as the value to resolve the error.

     

     

All Replies

  • Wednesday, January 11, 2006 6:37 AMkhushboo Sharan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Joey

    This is a known issue in the beta3 builds which we have resolved in the later bits. The issue is that a registry key HKCU\Software\Microsoft\VisualStudio\8.0\TeamBuild\AllowedTeamServer is missing on your build machine (from where you are trying to kick off builds using command line). This registry key is created when you first fire a build using VS. You can do one of the following to get this working

    - Fire off a manual build from the TE of your build machine (the same way that you are doing from your client machine right now)

    OR

    - Create this registry key and set it to point to your server.

    Let us know if this doesnt work

    Thanks

    -Khushboo

  • Wednesday, January 11, 2006 4:21 PMJoeyBB Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    I disassembled the code in the error message and it's looking for the servers in this key - HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers.

    I added a new string value with the non-fqdn name of the server (6nytp71) as the name and the actual url ( http://6nytp71:8080 ) as the value to resolve the error.