I am getting an error code related to excel running into problems with 'tfcofficeshim.connect.16' add-in that I use for importing data from Azure DevOps with a macro

Question

I have been able to use an excel macro that was passed onto me for quite some time. However, just recently it crashed when I was trying to run the macro by going to "Team" tab in the ribbon, clicking on "configure drop down" and clicking "list" where it allows me to select the query I would like to run from Azure DevOps. Please note that I have not altered the VBA or macro that was created originally and was doing nothing out of the ordinary, so this was a random issue.

At this point I am getting the following error message: "Excel is running into problems with the 'tfcofficeshim.connect.16' add-in. If this keeps happening, disable the add-in and check for available updates. Do you want to disable now?"

I have been working with my organizations IT team to trouble-shoot the issue, but have been unsuccessful. I have tried the following, among other things I may be missing:

• unblocking the file manually and creating trusted file locations to eliminate security blocks
• re-enabling disabled add-ins and activating com add-in "Azure DevOps Add-in"
• Control panel > MS office 365 > tried quick repair and online repair

Answer 1

Hi @Vincent Swanson ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

This error typically indicates that the Azure DevOps Office Integration add-in is failing to load due to a registry configuration issue or an assembly binding conflict (often with Newtonsoft.Json).

Since you have already tried repairing Office and re-enabling the add-in without success, please follow these advanced troubleshooting steps from the official Microsoft documentation:Resolve Azure DevOps and Office integration issues

Step 1: Force the Add-in to Load via Registry The LoadBehavior registry key determines how the add-in loads. If it is set to 0, the add-in is disabled.

1. Open Registry Editor (regedit).
2. Navigate to the following path (if 16 is not present, check for the highest version number available): HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.16
3. Double-click LoadBehavior and set the Value data to 3.
4. Click OK and restart Excel.

Note: If the key does not exist under HKEY_CURRENT_USER, check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins.

Step 2: Resolve Assembly Binding Conflicts (TF80070) If the registry fix does not work, the crash may be caused by a version conflict with the Newtonsoft.Json library. You can resolve this by creating a configuration file for Excel.

1. Navigate to your Excel installation folder. Typical paths include:
   • Microsoft 365 / Office 2016+: C:\Program Files\Microsoft Office\root\Office16\
2. Open Notepad as an Administrator.
3. Paste the following XML content:

      <?xml version="1.0" encoding="utf-8"?>
      <configuration>
        <runtime>
          <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
              <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30AD4FE6B2A6AEED" culture="neutral"/>
              <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="13.0.0.0"/>
            </dependentAssembly>
          </assemblyBinding>
        </runtime>
      </configuration>
   

4. Save the file in the Excel installation folder as excel.exe.config.
   • Important: Ensure the file is not saved as excel.exe.config.txt.
5. Restart Excel and try to connect again.

Step 3: Clear Team Foundation Cache If the issue persists, cached data may be corrupted.

• Close Excel.
• Delete the contents of the following folder: %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache (Replace x.0 with your highest version folder, e.g., 7.0, 8.0).

Answer 2

The error you are encountering with the 'tfcofficeshim.connect.16' add-in in Excel can be attributed to several issues, often related to assembly binding conflicts or problems with the add-in itself. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Verify if the Add-in is Disabled:
   • Go to File > Options > Add-ins in Excel.
   • From the Manage dropdown menu, select Disabled Items and click Go. If the Azure DevOps Add-in is listed, enable it.
2. Repair Office:
   • Since you have already tried quick and online repairs, ensure that you have followed the correct procedures for repairing Office applications. Sometimes, a full repair can resolve underlying issues.
3. Update the Registry:
   • You may need to check the registry settings for the add-in. Open the Registry Editor and navigate to:
     • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Excel\Addins
     • Ensure that the LoadBehavior value for the add-in is set to 3. If it is set to 0, the add-in will not load.
4. Run Gacutil Tool:
   • If the issue persists, you might need to run the Gacutil tool to ensure that the necessary assemblies are correctly registered. Open the Visual Studio Command Prompt as an administrator and run the appropriate commands for your version of Office.
5. Check for Assembly Binding Conflicts:
   • The TF80070 error can occur due to conflicts with the Newtonsoft.Json library. If you have other applications that might be using different versions of this library, creating a configuration file to redirect the assembly bindings may help.
6. Contact Microsoft Support:
   • If none of the above steps work, consider reaching out to Microsoft support or the Developer Community for further assistance.

By following these steps, you should be able to troubleshoot the issue with the Azure DevOps add-in in Excel.

---

References:

• Resolve Azure DevOps and Office integration issues
• Resolve Azure DevOps and Office integration issues