Visual Studio Developer Center > Visual Studio Team System Forums > Team Foundation Server - Build Automation > GenCheckinNotesUpdateWorkItems throws "Object reference not set to an instance of an object"

Discussion GenCheckinNotesUpdateWorkItems throws "Object reference not set to an instance of an object"

  • Monday, August 11, 2008 5:24 PM
     
     

    Our builds throw errors in GenCheckinNotesUpdateWorkItems.  Some of the log:

     

    Target "CoreGetChangesetsAndUpdateWorkItems" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "R:\Teambuild\build\LGD\LGD\CI Build\LDG\CI Dev Build\BuildType\TFSBuild.proj":

    Using "GenCheckinNotesUpdateWorkItems" task from assembly "f:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll".

    Task "GenCheckinNotesUpdateWorkItems"

    GenCheckinNotesUpdateWorkItems TeamFoundationServerUrl="http://ohcleiis1375:8080/" BuildUri="vstfs:///Build/Build/3307" CurrentLabel="CI Dev Build_20080811.19@$/LDG" LastLabel="CI Dev Build_20080811.18@$/LDG" UpdateWorkItems=True BuildNumber="CI Dev Build_20080811.19" BuildUri="vstfs:///Build/Build/3307"

    Analyzing labels CI Dev Build_20080811.18@$/LDG and CI Dev Build_20080811.19@$/LDG.

    Querying item history.

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets(1036,5,1036,5): warning : Object reference not set to an instance of an object.

    The previous error was converted to a warning because the task was called with ContinueOnError=true.

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: The "GenCheckinNotesUpdateWorkItems" task failed unexpectedly.

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: System.NullReferenceException: Object reference not set to an instance of an object.

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: at Microsoft.TeamFoundation.VersionControl.Client.Changeset.get_WorkItems()

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: at Microsoft.TeamFoundation.Build.Tasks.GenCheckinNotesUpdateWorkItems.DoUpdateWorkitems(Dictionary`2 changesets)

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: at Microsoft.TeamFoundation.Build.Tasks.GenCheckinNotesUpdateWorkItems.ExecuteInternal()

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()

    C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning MSB4018: at Microsoft.Build.BuildEngine.TaskEngine.ExecuteInstantiatedTask(EngineProxy engineProxy, ItemBucket bucket, TaskExecutionMode howToExecuteTask, ITask task, Boolean& taskResult)

    The previous error was converted to a warning because the task was called with ContinueOnError=true.

    Build continuing because "ContinueOnError" on the task "GenCheckinNotesUpdateWorkItems" is set to "true".

    Done executing task "GenCheckinNotesUpdateWorkItems" -- FAILED.

    Done building target "CoreGetChangesetsAndUpdateWorkItems" in project "TFSBuild.proj".

    ------------------------------------------------------------------------------------------------------------------------------------------------

    Help - Any ideas?

     

All Replies

  • Tuesday, August 12, 2008 2:47 AM
     
     

     

    In the call stack:

     

    >>MSB4018: at Microsoft.TeamFoundation.VersionControl.Client.Changeset.get_WorkItems()<<

     

    Did you somehow truncate/delete workitems from the TFS project?

  • Monday, August 18, 2008 7:21 AM
     
     

    dockenator

     

    We are changing the issue type to “Comment” because you have not followed up with the necessary information. If you have more time to look at the issue and provide more information, please feel free to change the issue type back to “Question”.

  • Monday, September 29, 2008 6:49 PM
     
     
    I was wondering if you were ever able to reach a resolution to this issue. We are dealing with  the exact same issue you've listed. Any feedback you could provide would be greatly appreciated.