WorkItemTypeDeniedOrNotExistException when trying to open work items.

Question

  Whenever a work item is clicked from a query result window a simple popup box with the following message is displayed.

Could not load type 'Microsoft.Teamfoundation.workItemTracking.Client.WorkItemTypeDeniedOrNotExistException' from assembly 'Microsoft.TeamFoundation.WorkItemTracking.Client, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.

Once OK (which is the only option) is clicked the selection focus is made and we can see the details of the work item. The only problem with this error is its nuisance factor in closing this popup message for any click/change in the query windows.

This error pops up on multiple machines and I could not find any references of this error and cant figure out what to do. Did anyone else experience something similar? Is there a fix? Please help!

Regards

Sucharith Vanguri

 

Answer 1

Sucharith,

Looks like you are running TFS 2008 - do you have SP1 installed? Have you try repairing your install?

Thanks,
Sunder

Answer 2

Sunder,

 My apologies for not providing more details. Yes, it is VS 2008 SP1. I also tried re-installing the team explorer without any results. I did not try repairing the install, for one thing this problem is present on many machines with the VSTS Developer edition. On a few machines we have the Architect edition and they seem fine. Also I did try installing the VS SDK 2008 on one machine, still no solution.

Regards

Sucharith Vanguri

Answer 3

Which process template did you use?
Have you modifed any of the workitemtypes?

Answer 4

Yes it is a custom work item in a custom template. We really dont use all the work item types and the process as it is, hence we took the MSF agile template and stripped it down to almost nothing and created our own custom template. If it is aproblem with the template, why is it that it only happens on some machines?

I have power tools with Architecture version on my machine and it does not give any errors on mine, Most of the machines that give this error are developer versions of VS  with no power tools or SDK etc. They just have VS 2008 SP1 with Team explorer 2008.

One other thing to add, most (99%) of the work items ( of our custom type) have been created using an automated process and are kept upto date with another Incident tracking system for backward compatibility.  Teh custom application uses TFS API and runs on the server itself.

Regards,

Sucharith Vanguri

Answer 5

 There has been some posts regarding the SP1 which refers to that particular error message.  Something seems to not being updated either when SP1 is installed or when Team Explorer is installed.  The way to solve it seems to be to at least reinstall VS 2008 SP1, that's also quicker than  a full reinstall of VS. 

See the following links:

http://blog.magenic.com/blogs/daniels/archive/2008/08/24/Fun-with-VS2008SP1-and-VPC.aspx

http://drowningintechnicaldebt.com/blogs/shawnweisfeld/archive/2008/09/01/fun-with-tfs.aspx

and this forum post
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3355168&SiteID=1

and this connect issue, which was closed as not reproducable, but suggests ways to fix it without reinstalling, note the comments!
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=356083

Answer 6

Hello,

This looks like a setup/upgrade issue - it seems like you're having a newer Team Explorer that somehow tries to use an old version of Microsoft.TeamFoundation.WorkItemTracking.Client assembly. I will try to find someone to look at this problem.

Alex

Answer 7

Osiris,

I shall try to reinstall SP1 and check.


Alex,

I believe that may be the case as I did look for this expection type in the dll when opened through the object browser and could not find it. However the versions do match with whatever DLL I have and what it is actually looking for. I assume that MS does change the version number when they release fixes.

Thanks all for the input, I will take a crack at it and see.

Regards

Sucharith Vanguri

Answer 8

Reinstalling SP1 did fix the problem.  When I launched SP1 it did show that it will fix any of the following  items, and team explorer is one of them. It seems that in our initial load the order of installation was VS 2008, SP1 and then Team Explorer. We will be fixing the order as well.

Visual C++ 2008 SP1 - x86 Runtime
Visual C++ 2008 SP1 - x64 Runtime
Visual C++ 2008 SP1 - IA64 Runtime
Microsoft Visual Studio 2008 Shell (integrated mode) - ENU
Microsoft Visual Studio 2008 Performance Collection Tools - ENU
Microsoft Visual Studio Team System 2008 Development Edition - ENU
Microsoft Visual Studio 2008 Team Explorer - ENU
Visual Studio Tools for the Office system 3.0 Runtime
Microsoft Windows SDK for Visual Studio 2008 SP1 Tools
Microsoft Windows SDK for Visual Studio 2008 SP1 Win32 Tools
Microsoft Windows SDK for Visual Studio 2008 .NET Framework Tools - enu

Thanks a lot guys for all the input.

Regards

Sucharith Vanguri

Answer 9

I have also had this problem, but it does not happen with the Administrator account, only with the other accounts.

---

Rafael