Skip to main content

TF84032: Team Foundation could not insert the work item list.

Last week I upgraded my Office 2007 installation to Office 2010. After the installation was complete, the Team Foundation Server integration started failing. Everytime I tried to open a work item list in Excel, the following error message was returned:

clip_image002

If I tried to open Excel from inside Visual Studio, another error was returned:

image

On the Internet the following possible solutions were mentioned:

  • Repairing the  Visual Studio Tools for Office Runtime. Didn’t help for me.
  • Repairing the Microsoft Office 2010 installation. Didn’t help either
  • Re-registering the TFSOfficeAdd-in.dll (regsvr32 "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\TFSOfficeAdd-in.dll")

Then I found some information on the MSDN forums about how to get extra tracing info:

1. Copy the following contents to a config file and name it as Excel.Exe.Config (for TFS Excel Add-In) or WinProj.exe.config (for TFS Project Add-in)

<?xml version="1.0"?>

<configuration>

<system.diagnostics>

    <switches>

<add name="General" value="4" />

</switches>

<trace autoflush="true" indentsize="4" />

</system.diagnostics>

</configuration>

2. Copy this config file to the folder where Excel.exe/WinProj.exe is installed (Program Files\Microsoft Office\Office14) . On Vista if UAC is turned on then you won't be able to save a file under Program Files. So save this file under some other folder (say %temp%) and copy this file to Office install directory under Program Files

3. Close and re-launch Excel or WinProj

4. Re-try your scenario. For Excel trace information will be added to %temp%\tfs_msexcel.log and for MSProject it will added to %temp%\tfs_msproject.log

This returned the following information:


[Error, PID 5032, TID 1156, 10:08:16.248] Exception:  {
Exception Message: Error HRESULT E_FAIL has been returned from a call to a COM component. (type COMException)

Exception Stack Trace:    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
   at Microsoft.TeamFoundation.WorkItemTracking.Client.DataStore.MetadataProvider.get_ConstLookupName()
   at Microsoft.TeamFoundation.WorkItemTracking.Client.DataStore.MetadataProvider.FindConstant(String name, Int32& id)
   at Microsoft.TeamFoundation.WorkItemTracking.Client.Provision.WitExporter.get_GlobalLists()
   at Microsoft.TeamFoundation.WorkItemTracking.Client.Provision.WitExporter.ExportGlobalLists()
   at Microsoft.TeamFoundation.WorkItemTracking.Client.Provision.WitExporter.Export()
   at Microsoft.TeamFoundation.WorkItemTracking.Client.Provision.ProvisionClass.ExportWorkItemType(Int32 projectId, Int32 typeId, Boolean withGlobalListsFlag)
   at Microsoft.TeamFoundation.OfficeIntegration.Client.Common.OfficeProjectContext.CalculateHashCode()
   at Microsoft.TeamFoundation.OfficeIntegration.Client.Common.OfficeProjectContext.Initialize()
   at Microsoft.TeamFoundation.OfficeIntegration.Client.Common.OfficeProjectContext..ctor(NamespaceData namespaceData, String teamProjectName, String projectLocation)
   at Microsoft.TeamFoundation.OfficeIntegration.Client.ExcelAddIn.InsertListObject()
   at Microsoft.TeamFoundation.OfficeIntegration.Client.ExcelCommands.NewWorkItemListCommand_Click_Internal()

}

Didn’t know what to do with that, so as a last resort I re-installed Team Explorer 2010 and this solved the issues. Finally!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more