使用witadmin导出配置遇权限错误，请求解决方法

Hey there! Let's work through this authorization issue you're hitting with witadmin exportcategories. First, let's start with the obvious fixes that often resolve this kind of problem:

1. Fix Your Command Syntax First #

Looking at the command you ran, there are a couple of syntax mistakes that might be contributing to the error (or at least making it harder to debug):

witadmin exportcategories /p:https://dev.azure.com/my-org /p:my-proj :f/"file-path"

Here's what's wrong:

• The project parameter should be /n: (not a second /p:) — /p: is reserved for the Azure DevOps collection URL.
• The file path parameter is miswritten: it should be /f:"file-path" (not :f/"file-path").

Your corrected command should look like this:

witadmin exportcategories /p:https://dev.azure.com/my-org /n:my-proj /f:"file-path"

2. Verify Your Permissions #

Even with the right command, you'll hit this error if your account doesn't have the correct permissions in the project. To export work item categories, you need either:

• Project Administrator permissions for the target project, or
• The Edit project-level information permission enabled (you can check this in Azure DevOps: go to Project Settings > Permissions > select your user > look for the relevant permission under "Project-level permissions").

3. Clear Stale Credentials #

Logging out and back into Visual Studio sometimes doesn't clear cached credentials properly. Try this:

• Open Control Panel > Credential Manager > Windows Credentials
• Find all entries related to dev.azure.com or your organization's URL
• Delete those credentials, then restart your command prompt/VS and re-authenticate to Azure DevOps

4. Use Azure DevOps CLI Instead (More Reliable) #

Witadmin is a legacy tool, and the Azure DevOps CLI is more modern and handles authentication more smoothly. If you have the Azure CLI installed, run this command instead to export categories:

az boards work-item category export --project my-proj --organization https://dev.azure.com/my-org --output-file "file-path"

If you don't have the CLI installed, you can grab it via standard installation channels (like the Microsoft Download Center or package managers).

5. Double-Check Organization Spelling #

Wait a second — your error message says https://dev.azure.com/my-orgnization (note the extra 'n' in "orgnization"), but your command uses my-org. Make sure your organization URL is spelled correctly! A typo here would definitely cause an authorization failure.

Give these steps a try, and let me know if any of them resolve your issue.

内容的提问来源于stack exchange，提问作者Shachar297