We are trying to use the Open in Microsoft Excel feature in VS2015 to open TFS query results in Excel when we receive the error: TF80068: Team Foundation encountered an error while communicating with the server. Please check your connection and try again. Excel TFS Error
I can open Excel (Office 365) and use the Team menu New List to connect to the server (2010) and pull the results of the query without issue.
It is only when we use the VS2015 option that it fails.
I've removed and added the AddIn numerous times.
I've tried to register the dll as well...no luck.
Thanks in advance!
TFS MS Office button
To fix the error open Excel to a blank workbook
Click File -> Options -> Add-Ins
At the bottom open the Manage drop down and select COM Add-Ins
Click Go…
In the Add-Ins Available list scroll to the bottom, you should see something like the attached image
add Ins list
You may have up to 3 Team Foundation Add-in items, although they look similar they are different
a. Select each one and check the location for each
b. Ensure ONLY the one labeled "C:\Program Files\Common Files\Microsoft Shared\Team Foundation Server\14.0\x86\TFSOfficeAdd-in.dll" is selected
Verify TFC Office Shim is unselected
Click OK
Return to VS2015 and open the project in Team Explorer
Open Work Items
Select Open in Microsoft Office drop down and click Open Query in Microsoft Excel
It should now work! You should see data in the worksheet
I guess you should install latest version of Office Integration: ISO and Web Installer.
Hope this helps!
I received this error and fixed it by re-signing in using the following steps. There might be a more straight-forward way to fix, but this is what worked for me:
Open a new Excel instance.
Creat a new workbook.
Click on the "Team" tab.
Select "New List" ("Connect to Team Foundation Server" dialog should appear)
Click "Switch User" in the bottom left.
Enter credentials.
Open original workbook.
Related
My team is developing an Office web add-in for Excel built in vanilla Javascript. To test and debug our project, we have been side-loading the add-in as per the usual steps.
Which are:
Navigate to /Users/USERNAME/Library/Containers/com.microsoft.Excel/Data/Documents/wef
Copy and paste manifest.xml file in above directory
Open Excel, click the insert tab, click My Add-Ins dropdown, then select the add-in described by the manifest.xml (which is under Developer Add-Ins)
This process works smoothly for everyone on the team except for one person. For that one person, after they have completed the steps, they see no Developer Add-Ins section, and no options to load the add-in described by the manifest.
What could be causing this issue?
More Info:
Problematic team member:
Non-problematic team members:
Hi I am trying to open Work item query results in microsoft excel but getting an error "TF208093 you cannot use work item query to generate reports in excel on this server because it is not configured for reporting"
Below are the steps which I performed
1. Installed excel extension from marketplace on Azure DevOps
2. Installed Visual Studio 2017
3. Installed Team Foundation Server Integration 2017
I tested the "open work item query result in microsoft excel" through the excel extension with below process:
Click the “Open in Excel” in Query Results after I installed the Excel extension for my organization:
Click the “Open TfsProtocolHandler.exe” button in popup dialog
Now we can see it in Excel opened automatically:
The only difference between my process and yours is that i didn't install Team Foundation Server Integration 2017 (I have Visual Studio 2017 on my computer), you can try to uninstall it and do the process again see if we can solve the problem.
Your error very similar to the error with the reports generation. Azure DevOps Service does not support Reports:
Try to open your query directly from Excel:
Visual Studio 2019 appears to not be installing the needed component (maybe only under certain workloads?).
Whether have VS 2019 or not, this download should solve the issue: https://visualstudio.microsoft.com/downloads/#azure-devops-office-integration-2019
Note: this isn't quite a direct answer to the question, since the questioner does have the TfsProtocolHandler.exe, rather this answer is a fix for "nothing happens when I click 'Open in Excel'"
VS2017, Click "Create Report in Microsoft Excel", Excel 2016 opens, once I click Finish, throws this
"TF208071: The following error occurred when the command was generating PivotTable and PivotChart reports. Close the Microsoft Excel workbook and try again, or press F1 for more information.
Object reference not set to an instance of an object.
"
Recently upgraded TFS server to 2017, I can still generate the reports using Visual Studio 2012/2013 by connecting to the same TFS server. However not on VS2017.
Where do I start looking? None of the event logs show any such error.
I have 4 columns of data from the WI to export, so its not the amount of data.
Seems you are talking about create Excel reports from a work item query, try to clear TFS and VS cache and test again.
Besides, since you are using TFS2017 and VS2017, you could try to use this extension--VSTS Open in Excel, you could use this extension for bulk editing work items, or to leverage Excel tools to analyze and visualize a large number of work items. You could directly open work items in web portal.
Besides, as a workaround, you could still generate the reports using Visual Studio 2012/2013 by connecting to the same TFS server.
Hope it helps someone!
The issue is with the 2017 TFS COM Add-in, this has an issue used with Excel 2016. seems like a bug from Microsoft!
So we removed all the TFS addin from Excel2016. Then do a repair install of 2015 Office integration which will set V14 Com Add-in to load at start. Then it will export through VS2017 (using the 2015 COM IN)
You can also edit this through regedit, make the V14 OR V13 COM Add-in to load at startup by editing that specific TFS Addin to a value of 3 and setting all the rest to 0.
I have an application that is developed using CommanBar tools. As there are much constraints in that, i have planned to shift to the Ribbon(view designer). I created a project like, File->New Project->Excel 2007->Excel Addin for 2010.
Created a sample addin and added a new project to the same solution as I wanted the addin to be added using installer(.msi). I registered the Com Addin in the Registry, but on uninstallation, the files are getting removed only in the registry entry, but not in the MS Excel, the addin still to be remained there. Please help me in this. As I am new to the implementation of Ribbon implementation.
I have used winform c# 4.0.
Thanks in advance.
#kiru - the screen shot for the path you mentioned
Check the path from where the addins are been loaded.
Open Excel
Click File => Options => Addins (Tab)
Select COM Add-ins in Manage dropdown box and click Go
Select the addin and you can see the path where it is been loaded.
If it is from bin directory then follow this
If you are running your msi on development pc clean your solution every time you test your msi.
Using Excel 2010 and TFS 2010. I've been using the "Team" tab in Excel for quite a while now (very useful!). Today, the "Refresh" took ages and I couldn't use Excel so I killed the process in Task Manager. I reopened Excel and the Team tab was missing. I added it back in File > Options > Add Ins > Manage COM Add Ins > Go > selected the Team Foundation Add-In and the Team tab is back. I can create/view lists etc. However, when I close and reopen Excel the Team tab is missing again.
How do I make the Team tab stay on the ribbon bar even when closing & reopening Excel?
For Excel 2013 x64 and Visual Studio 2012, I had to change HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.4\LoadBehavior to 3 (Load at startup).
I had previously disabled the add-in via the Excel COM Add-Ins dialog box. This changed the add-in load behavior to "do not load automatically". Attempting to re-enable the add-in through the dialog box now only changes it to "load on demand", which is only good for one session of Excel. There is an issue logged in Connect for this. Changing the registry manually works around the bug.
By chance, I re-enabled it (after having to manually re-add the tab again).
Excel > File > Options > Add-Ins > Manage > Disabled Items > select items > click Enable.
As easy as that.
I have had that same issue with TFS 2010 Office Add-in and Excel. The reason was because there were two TFS Office add-ins, the first version was for a 64 bit machine, while the other was for a 32 bit machine. So I removed both versions, restarted excel, and re-added the 32 bit version of the TFS add-in. I have had no issues since.
EDIT: My local machine is running Windows 7 64 bit and Excel 2010.
I just ran into this myself. The registry setting looked okay, and there weren't any add-ins listed under Disabled Items.
I launched Excel as Administrator, deleted all instances of Team Foundation Add-in (I had 3), and then re-added the add-in. It was then correctly showing as "Load at Startup." I closed Excel and re-opened from my usual shortcut, and everything looked good.
There were a number of Excel restarts peppered into that process as I was very much guessing and checking, but I believe that it was the act of re-adding the add-in that ultimately resolved the issue for me.
I had to remove the extension (listed as "Unloaded") from COM Add-Ins list and then add it again.
Follow the instructions below to manually add it to Excel:
Navigate to Com Add-ins manager:
File > Options > Add-Ins > set "Manage:" to "COM Add-ins" > Go...
Add it again:
Add... > "C:\Program Files\Common Files\Microsoft Shared\Team Foundation Server\11.0\x86\TFSOfficeAdd-in.dll" > OK
Restart Excel: Confirm the "Team" tab appears on startup
This is a workaround that helps several people. This is not a fix but still has worth.
Launch Excel as Administrator. You do this by right clicking the Excel Icon, then right click the Excel mini-icon then click "Run as administrator".
This is not a fix and can be a hassle but for many with this issue it will provide the features you want. Hopefully Microsoft will come up with a permanent solution in the future.
With latest versions this problem can be solved by installing Azure DevOps Office® Integration 2019 from
https://visualstudio.microsoft.com/downloads/#other-family
If you don't see Team Foundation Add in you can use this method which saved a lot of time for me
it will appear like this , file --> options --> add ins