I am not able to access both the Source control in Visual Studio 2010 as in 2012 when I try to access this error is shown: "TF14045: The identity is not a Recognized identity". This error started after I detach the project collection from TFS 2010 and attach on Team Foundation Server 2012, anyone knows how to fix this?
Asked
Active
Viewed 7,563 times
3 Answers
0
Never had this error, because the migration is planned for January, but I found this entry with some suggestions and answers from MS:
http://social.msdn.microsoft.com/Forums/en-US/tfsadmin/thread/b67ad1d6-d763-4602-bf14-489a3389a30d

MikeR
- 3,045
- 25
- 32
0
I guess you have TFS 2012 with Update 1 installed? If so you have to wait for the upcomming patch that will contain a bugfix for this error. Have a look at Microsoft Social:
http://social.msdn.microsoft.com/Forums/en-US/tfsadmin/thread/238cad96-8e74-4f14-869a-3bb5e0629fd7

PVitt
- 11,500
- 5
- 51
- 85
-
I just ran across this issue, I have VS 2012 with Update 3, and connecting to TFS 2012 , It is happening on a viewing history of a few controllers so far – Tom Stickel Jul 16 '13 at 05:37
-
@TomStickel So what is the current patch level on your TFS? – PVitt Jul 16 '13 at 07:44
-
On this current project i'm working remotely and currently just connect to TFS via both VS 2012 and then I also use their TFS website for tasks and bugs. I don't know where I would see or find that information. Do you? Or do I have permissions? Where should I look ? – Tom Stickel Jul 16 '13 at 07:57
-
@TomStickel You need admin access to the TFS. Just contact the responsible administrator. – PVitt Jul 16 '13 at 08:28
-
One my users is having this issue as well with TFS 2012 with update 4 installed – Lareau Dec 09 '13 at 15:27
-
And again someone is downvoting without leaving a comment. Thanks a lot for giving me no chance for improvement. – PVitt Jul 14 '15 at 07:22
0
Just be sure that you have not opened two instances of Visual Studio & trying to connect two TFS servers which needs two different credentials/ domain.
I was facing that issue & after closing one of the instances, it started working fine.

Biki
- 2,518
- 8
- 39
- 53