Common Language Runtime detected an invalid program error when using team explorer

Question

I have been using Visual Studio 2005 Professional plus team explorer to connect to a Team Foundation Server 2005 for a few weeks. I have also installed Visual Studio 2005 SDK. I had been able to connect to TFS and create Team Projects, check in source code, run builds, run work item quries etc. absolutely fine for some weeks now.

 

I installed Visual Studio 2005 Power Tools and while this installed OK, I had problems running the samples that use Microsoft.TeamFoundation.WorkItemTracking.Controls assembly. The samples would fail at runtime with an InvalidProgramException. But apart from this I could still connect to the TFS OK.

 

Yesterday, I ran Windows update and 96 updates were installed. Now anytime I try to connect to TFS via Team Explorer to runany of the work item queries I get a "Common Language Runtime detected an invalid program" message from Visual Studio. There is nothing in the Event Log apart from a couple of entries earlier today (which have not repeated) :

 

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date:  20/02/2008
Time:  10:10:33
User:  N/A
Computer: DEVPC4
Description:
Hanging application devenv.exe, version 8.0.50727.42, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 48 61 6e 67   ion Hang
0010: 20 20 64 65 76 65 6e 76     devenv
0018: 2e 65 78 65 20 38 2e 30   .exe 8.0
0020: 2e 35 30 37 32 37 2e 34   .50727.4
0028: 32 20 69 6e 20 68 75 6e   2 in hun
0030: 67 61 70 70 20 30 2e 30   gapp 0.0
0038: 2e 30 2e 30 20 61 74 20   .0.0 at
0040: 6f 66 66 73 65 74 20 30   offset 0
0048: 30 30 30 30 30 30 30      0000000

 

Followed by:

 

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date:  20/02/2008
Time:  10:10:33
User:  N/A
Computer: DEVPC4
Description:
.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A2B45A2) (0)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

I then removed Visual Studio 2005 Power toys. I then tried repairing the Team Explorer installation, but that failed with approx 20 event log entries of a similar nature (although these errors are possibly to do with removing the Power Toys):

 

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11309
Date:  20/02/2008
Time:  14:52:37
User:  xxDOMAIN\purplekate

Computer: DEVPC4
Description:
Product: Microsoft Visual Studio 2005 Team Explorer - ENU -- Error 1309.Error reading from file: c:\Program Files\Microsoft Visual Studio 8\Microsoft Visual Studio 2005 Team Explorer - ENU\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Common.Library.dll.  System error 3.  Verify that the file exists and that you can access it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 45 30 32 37 46 45 32   {E027FE2
0008: 45 2d 33 46 46 35 2d 34   E-3FF5-4
0010: 44 43 39 2d 41 38 33 38   DC9-A838
0018: 2d 33 46 32 31 43 43 46   -3F21CCF
0020: 37 34 45 46 45 7d         74EFE} 

 

Finally I reinstalled Visual Studio 2055 Professional and Team Explorer. I still have the 'Common Language Runtime detected an invalid program' message from Visual Studio every time I try and run a Work Item query.

 

Can anyone help?

 

Cheers,

 

Kate

 

 

 

 

 

Answer 1

Kate,

Do you have Service Pack 1 for Visual Studio installed?  If not, give it a go.

Thanks,


Steve - www.platinumbay.com

Answer 2

Kate,

You might also try running a repair of Visual Studio.

Hope this helps,


Steve - www.platinumbay.com

Answer 3

Hi,

 

I thought an update might be appropriate. I did install Service Pack 1 and I did attempt a repair, with no luck. I even uninstalled and reinstalled VS 2005, still no luck. I never resolved the issue and so in the end I had to completely rebuild my PC.

 

Cheers,

 

Kate