With Cisco WebEx Connect installed (whether running or not) I have issues with Visual Studio 2010. When Visual Studio 2010 tries to run Team Explorer, it seems to try to run and/or connect to WebEx Connect. However, both applications crash. This happens whether WebEx Connect has been running or is closed.
I have also seen this on my Windows XP (32bit) development machine with Visual Studio 2010 and WebEx Connect.
On both machines, the problem goes away when WebEx Connect is uninstalled. However, it is required to be running here, so this is not a permanent solution.
The only errors I see in the Event log are in regards to Visual Studio (devenv.exe)
Fault bucket 2246339133, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: 1ed231d3-74fd-11e1-a6b2-d4bed99a2cd6
Report Status: 0
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidCastException
Todas las respuestas
Thanks for your post.
Don’t run the Team Explorer, only run your VS 2010, the VS 2010 can work correctly? You must install the WebEx Connect on TFS clients?
And as Jim said, please upgrade your VS 2010 to VS 2010 SP1, then try connect to TFS Server using Team Explorer again.
John Qiao [MSFT]
MSDN Community Support | Feedback to us
I turned off Team Members in Team Foundation Power Tools under Options, this seems to have resolved it. Yes, we use TFS, yes we need WebEx Connect. This is a workaround, not a solution.
Also, yes, we have SP1 on VS 2010.
I am using Cisco WebEx Connect 7.2.1 Build 16886. I'm having the same problem on Win 7 x64 SP1 with VS 2010 SP1. I also have Office 2010 x86 installed w/out SP1. Please post any updates. We are doing a 30 day trial of Cisco WebEx Connect and need an answer soon. I tried running VS as admin with no success. It still crashes.
I discovered a workaround that may be satisfactory for some. In the WebEx Connect preferences, select the Integrations category and uncheck the box labeled "Display WebEx Connect status in Microsoft Office applications". This appears to be sufficent for my environment.
Some of my coworkers had to make a second change for VS. Go into VS2010 and on a project, right click in Team Explorer on the “Team Members” selection under a project and select “Personal Settings”. Usually, the crash is caused by the “Collaboration Provider” having a selection set there. Just set it to “no provider…” and that should take
care of it.
Any response back from webex? Our team also experiences this issue.
Some choose to disable the integration and some choose to run with Webex Version 6.5.1 (which doesn't have the integration). It would be nice if this feature worked...
Tied up in knots...
Just to detail a bit your answers that worked for us:
We had the same problem for a while. This is due to the TFS PowerTools add-on, where the Team Member collaboration points to "Microsoft Office Communicator" by default (which I don't have ! but use WebEx instead) .
Just remove the default value, that way: In Team Explorer, for ex within VS2010:
- Right-click on the "Team Members" tree node (below "Work Items", "Reports" and "Builds")
- Choose the last option: "Personal Settings..." (it opens a pop-up)
- In the "Gereral" tab, you will see "Collaboration" group
- Change the default "Provider" from "Microsoft Office Communicator" to "<None>"
- You will end-up having "<no provider is configured>", then click "OK"
Then no more problems.
Vincent THAVONEKHAM www.thavo.com
- Editado Vincent Thavonekham jueves, 02 de agosto de 2012 12:30 Saw that KevinEw already answered