本地TFS迁移至VSTS触发TF400898内部错误，求助排查方案
That generic TF400898: An Internal Error Occurred message is definitely frustrating, especially when the troubleshooting docs don’t have a direct match. But don’t worry—here are targeted steps to help you resolve this, using the activity ID c47a7fd7-2b13-4d47-8aa8-00a7b09367ca to dig deeper:
Validate your migration package: Corrupted or incomplete packages are a common culprit. Re-generate the migration package from your source TFS, making sure the process completes without any warnings or errors. Double-check that all required artifacts (work items, build definitions, source code repos) are included in the package.
Audit permissions end-to-end: The account running the migration needs full administrative access on both your source TFS (Project Collection Administrator role) and target VSTS instance. Also, check for locked work items, restricted build pipelines, or custom fields with permissions that might block the import process.
Confirm version compatibility: Ensure your source TFS version is supported for direct migration to your target VSTS environment. Older TFS versions (pre-2017) often require intermediate upgrades before migrating. Apply all latest updates and patches to your source TFS server before retrying.
Dig into migration logs: Even though the error is generic, the detailed migration logs (usually stored in your migration tool’s output folder or in VSTS’s migration history) will have entries tied to your activity ID. Look for failed steps, missing dependencies, or invalid data structures that might be triggering the internal error.
Test with a smaller scope: Try migrating a single, small project instead of your entire collection. If this succeeds, gradually add more components (like additional repos or work item types) to identify which specific artifact is causing the failure. This is a great way to isolate issues with large or custom objects.
Clear migration tool cache: Stale cached data can cause unexpected errors. Clear any local cache used by your migration utility, restart the tool, and attempt the migration again.
Reach out to support with your activity ID: If none of the above steps work, the activity ID
c47a7fd7-2b13-4d47-8aa8-00a7b09367cais key here. Microsoft’s support team can use this ID to pull detailed server-side logs that will pinpoint the exact cause of the internal error.
内容的提问来源于stack exchange，提问作者Tony
