logo
down
shadow

OpsHub migration utility failure due to large file attachment


OpsHub migration utility failure due to large file attachment

By : Pradeep Mohan
Date : November 21 2020, 09:01 AM
wish helps you This is caused by VSO attachment size limitation. Refer to this question to change the maximum attachment size for VSO.
code :


Share : facebook icon twitter icon
OpsHub TFS to VSOnline Migration Utility - Will WorkItem # not stay the same?

OpsHub TFS to VSOnline Migration Utility - Will WorkItem # not stay the same?


By : user3333645
Date : March 29 2020, 07:55 AM
wish helps you Workitem # is auto-generated field in VS Online, OpsHub Migration Tool do not migrate them. OpsHub starts migration of workitems across workitem types(Bug, Test Case, etc) in parallel. Thus there is no guarantee that workitem# will be same in both end point.
Does OpsHub migration utility consider project names case sensitive?

Does OpsHub migration utility consider project names case sensitive?


By : Randy Green
Date : March 29 2020, 07:55 AM
I think the issue was by ths following , Yes. The project name is case sensitive. And you can rename the VSO project by following steps:
Open your VSO account from Web Portal. (https://xxxxxx.visualstudio.com/DefaultCollection/, without project name) Click "Manage Account" button in up right corner. Click "Manage collection security and group membership" link. Click "Overview" panel. Expand the context menu of the project and select "Rename".
OpsHub Visual Studio Migration Utility MetadataException

OpsHub Visual Studio Migration Utility MetadataException


By : Bill MacKay
Date : March 29 2020, 07:55 AM
this one helps. The proxy utility suggestion worked as described by @OpshubInc. in their last comment. I have put the suggestion below for future reference.
OpsHub Visual Studio Online Migration Utility - Error saving configuration OpsHub-001105

OpsHub Visual Studio Online Migration Utility - Error saving configuration OpsHub-001105


By : pélican973
Date : March 29 2020, 07:55 AM
I wish this help you This is something that is being fixed in the tool. Until then the workaround for this issue would be to change the machine locale to 'US'.
Once you change the locale (by being logged in as some machine user), you'll have to configure your OS to run the tool as that user (since by default 'Local System' runs most services). So, open services.msc, find the service named 'OpsHub Visual Studio Online Migration Utility' and change it's log-on user as the one whose locale you changed.
Why is OpsHub Visual Studio Online Migration Utility Kicking off Builds

Why is OpsHub Visual Studio Online Migration Utility Kicking off Builds


By : Hampus Jakobsson
Date : March 29 2020, 07:55 AM
like below fixes the issue You'd want to either disable all of your build definitions until the migration is completed, then delete any queued builds and re-enable them or have NO_CI added to the comments to prevent triggering builds. I'd recommend just disabling the build definitions during the migration.
shadow
Privacy Policy - Terms - Contact Us © animezone.co