Sign In
Richard Murillo on Software Development
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
About
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
C#
Lambda Expressions
LINQ to SQL (DLINQ)
Team Foundation Server
Visual Studio
Archive
Archives
September 2009
(1)
August 2009
(1)
June 2009
(1)
February 2009
(1)
October 2008
(3)
March 2008
(1)
November 2007
(1)
April 2007
(2)
February 2007
(1)
October 2006
(3)
September 2006
(1)
July 2006
(1)
June 2006
(2)
May 2006
(1)
April 2006
(11)
March 2006
(7)
February 2006
(2)
Resolving The identity DOMAIN\Username is not a recognized identity error message on check in
MSDN Blogs
>
Richard Murillo on Software Development
>
Resolving The identity DOMAIN\Username is not a recognized identity error message on check in
Resolving The identity DOMAIN\Username is not a recognized identity error message on check in
Richard Murillo - MS
27 Feb 2006 6:07 PM
Comments
0
Some information is out on the web about a bug that exists when creating a project that results in an error message similar to "The identity [Project Name]\Project Administrators is not a recognized identity" (to resolve that issue see James Manning's blog entry:
http://blogs.msdn.com/jmanning/archive/2005/10/21/483682.aspx
). However, I ran into this issue when my account name changed and not my physical account.
When attempting to commit my changes after my account name change I received the following error:
"The identity DOMAIN\MyUserName is not a recognized identity"
To resolve the issue, the following steps had to be performed on the workstation that was giving the error:
Under the Release Candidate one could simply run tf /updateusername:DOMAIN\YourNewUserName and everything would work. However, I was running Beta 3 Refresh, so this syntax was not available.
For beta 3 refresh the following commands must be run:
tf workspaces /updateUserName /s:TFSSERVER
tf workspaces /remove:* /s:TFSSERVER
tf workspaces /s:TFSSERVER
If you're worried (like I was) that your pending changes would vanish, never fear! The /remove parameter works against a local cache file. The issue is that the /updateUserName parameter actually updates the workspaces on the server, but the cache file still has information about the old workspaces. the /remote:* command removes the workspace entries from the cache, so upon retrieving them again all is well.
Hope this proves useful.
0 Comments
Team Foundation Server
Blog - Comment List MSDN TechNet
Comments
Loading...