import using witimport fails in VSTS Beta3

I try to import WorkItem, using witimport utility. WorkItem pass validation successfully (witimport with /v flag). Actual import fails with "Account not recognized" error. 

I have logged in as tfssetup user which is domain user and member of TeamSystem Administrators group.

Please help me out.

Installations

Installated Win2003 SP1 with latest updates, Team Foundation Server beta3 on server 
WinXP SP2 with latest updates, VSTS 2005 Release Candidate on client.



Answer this question

import using witimport fails in VSTS Beta3

  • FelipeLopez

    Hi,

    Thanks for the response. But I am using the latest RC. and TFS beta3.
    Yesterday I was not able to import today I am. So, again I created a new user and made it a member of same groups. Now for this user, again it is not working.

    The issue is that, till yst I was not able to import for the user and today I am.
    Now , the new user created today, is not able to import. May be i 'll be able to import tom'row.

    I feel this should not happen.

    regards,

  • wasabe dog

    Unfortunately, I am not an expert in this area; I will let the right person know about this problem.

    Thanks


  • sjmueller

    I added a new user in Active directory. It is made member of
    Administrators/Builtin,
    Enterprise Admins,
    Domain users,
    Users/Builtin,
    STS_WPG,
    DOmain computers,
    Domain Administrators. Refreshed it.

    Then i logged into the TFS client with the same credentials which I created above under same domain. On connecting to Team Foundation Server, it didn't connect. I was also not able to import. Tried it numerous times. Even removed the restrictred access when I use "Run as" from context menu to open VSTS.

    Logged off again...waited for 30 min or so...and then I was able to log in..and connect to TFS.

    I dont know what is happening. Does it take up some time to sync the Active directory and time in which this is made available to TFS client.


    HELP!!!!!

  • BrianXL

    Team System Administrators group - you mean is this "Team Foundation Administrators" group Could you perform the following and verify if tfssetup is part of this group:

    Right-click tfsserver on Team Explorer, point to "Team Foundation Server Settings" and then click "Group Membership". Click to select "Team Foundation Administrators" and then click Properties. Verify if tfssetup is listed.

    Right-click the project that you are using to import WIT under tfsserver on Team Explorer, point to "Team Project Settings" and then click "Group Membership". Click to select "[<ProjectName>]\Project Administrators" and then click Properties. Verify if tfssetup is listed.

    Please let us know if tfssetup is listed in anyof the above groups.

    Thanks
    Sagar



  • AndrewSorokin

    It sounds like you are running into the delay caused by our syncing with Active Directory.  Team Foundation has a background process that is scheduled to run once an hour.  This background process syncs the Team Foundation user database with Active Directory and the app tier's local users.  Until this process runs, any changes that you made in Active Directory will not appear in Team Foundation.

    This process is part of the Services web application, so if the Services web application is not running, the background sync will not occur.  If you need to force the sync to happen, you can do an IISRESET, and then connect to the Team Foundation server.  When the Services web application starts, it also kicks off a background sync with Active Directory.

    Hope this helps to clear up whats going on.
    --Matt Hoover
    SDE Visual Studio

  • joe20050

    Thank you for the response.

    Yes, tfssetup is listed in either of the cases. What next should I do


  • dangster_gangster

    This could happen for the following reasons:
    - You do not have enough permissions to import work item types. To do that you have to be administrator of that project or a TFS administrator.
    - Your work item type refers to a group that does not exist, and we do not handle such failures very well (the validation happens on the server, and all we're getting back is just an error code). Please review your XML for strings like [global]\xxx, [project]\xxx, or domain\xxx and make sure they all exist.
    - Or this can be bug in our code.

    Please note that we changed default group names in Beta 3 - your import may fail because you're using old global/project-scoped names which are no longer valid.


  • import using witimport fails in VSTS Beta3