TF10139 Error when checking in files: Check in policy error when policies have been satified

Question

I am getting the TF10139 error when attempting to check in items in VS 2005-TFS.  Looking at Policy Warings I get the following:

Internal error in Builds - popup: Error loading the Builds policy (The policy assembly 'Microsoft.TeamFoundation.Build.Controls, Version=9.0.0.0, Culture=neutral, PublicKeyToken=...' is not regeistered.). Installationinstructions:

 

and

 

Error loading the Changeset Comments Policy policy (The plicy assembly 'Microsoft.TeamFoundation.PowerTools.CheckinPolicies.ChangesetComments, Version=9.0.0.0... is not recognized). ...

 

I should add that we are not violating any of the policies that I am aware of (Require comment, Associate Work Item)

I have the TFS Powertools but come to think of it I am not certain the 2005 power tools were ever installed (I have both 2005 and 2008, this error was generated in 2005).  Any other thoughts on the source of this error?   To resolve this I assume I need to install power tools locally?  I am hoping to move our team and this app up to 2008, but we would still need to install PowerTools on every users machine, correct? 

Answer 1

Yes, you are correct.  Each developer would need to install the (correct version of) TFS Power Tools on their development PC in order to make use of the Check-In Policies.  If they do not have the TFS Power Tools installed, they will receive an exception at check-in time (much like the one you listed in your post).

 

Hope this helps.

 

Answer 2

 

IS this the case even if we ae using a seperate build server that does not have VS2005 IDE installed on it ???

Answer 3

Some of my users are experiencing the same error.  They're using VS2005 connecting to TFS 2008 and have power tools installed but when they attempt to check in, they still get this error.  They also have Team Explorer 2008 installed with powertools, and again, they have VS2005 Team Edition installed with Powertools 2005 too.

What are possible next steps?

Answer 4

Got... The problem is that the BUILD was setup as part of the check in policy.  Disabled that, and i'm good to go.

Answer 5

Hi, Could you please let me know where I can disable this? I am having the same problem as you mentioned above

Thanks