Team Explorer : External component has thrown an exception: Beta 3 Refresh on TFS with RTM on Vi
When connecting to TE (Tools|Connect to Team Explorer) we get the following errors:
1. Event Viewer:
.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)
2. Dialog Box:
Microsoft Visual Studio
External component has thrown an exception.
OK
Win XP, No legacy versions have been installed on the box - just Beta3 Refresh on TFS and RTM on the client.
We are running Beta 3 Refresh on TFS with RTM on Visual Studio
Hi Jean-Pierre,
When this issue occurs, do you see any errors in the event log on the application or data tier?
Try attaching a debugger to devenv.exe to figure out from the callstack which component throws the exception.
Dmitry.
Jean-Pierre,
The best thing to do is to attach a debugger before you try to connect to a Team Foundation Server. Once you've attached, in the debugger process open the Exceptions dialog (Debug | Exceptions) and enable first chance exceptions for CLR exceptions. To do that, check the "Thrown" column next to Common Language Runtime Exceptions.
It is not uncommon to hit a few exceptions along the way - we're only concerned about the one resulting in the message (for now at least).
If you have any problems, feel free to contact me via the email address in my profile.
- Tim
Tim,
Thanks for being on the ball.
I have tried to attach the vs debugger, using the options you mentioned above (catch exceptions for CLR). I'm using remote debugging, hosting the msvsmon.exe on the remote computer.
I'm not sure that I'm getting what you want. The devenv on the remote machine raises the dialog box, but no exception is thrown. I've checked the event log (system and app) and I findo no recent entries indicating an exception or error condition.
So if you have any more answers, please roll them this way!
Thanks
Jean-Pierre
Jean-Pierre,
From the steps you outlined in the e-mail sent to me the only obvious thing I can think of to check is whether or not "Enable Just My Code" debugger option is set under Tools | Options.
If that isn't the problem please send me email again.
Regards,
Tim
Tim,
This doesn't help :)
I'm not receiving anything on the remote debugger. I have followed all of the steps you mentioned.
To add more to the soup:
When installing Team Explorer (and we have done this 3 times), the install forces a restart. I don't recall having this happen in my other (successful) installations.
Jean-Pierre
I'm not sure what specifically would cause a restart to be needed. This is almost always because a file was in use that needed to be replaced during the install. To see that list *before* you restart, run REGEDIT.EXE and look at the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Please try enabling breaking on all exceptions including C++ and Win32.
Tim,
I have tried all of your suggestions. I can't get it to work.
Perhaps I am doing something wrong. I can't get any thing to work on the debugger. Perhaps it isn't throwing an exception? It just shows a dialog box and then continues as normal.
Jean-Pierre
