This migration utility helps customers to migrate the most commonly requested data from an on-premises Team Foundation Server to their Visual Studio Online account. It is designed for basic migration scenarios to migrate history of version control changesets, work items etc.
Worked very smoothly and completely migrated ~15 realtively simple projects and ~1,300 changesets. After configuring online security and mapping logins, the process couldn't have been much smoother. The only issue I've noticed so far is that check in timestamps for revisions will be set to the time of migration check-in; however, the comments have the original check-in user and original timestamp. Overall, this is an excellent utility - highly recommended for moving collections from TFS to Visual Studio Online!
My migration fails on the user mapping task with the following error :
OpsHub-014371: Could not instantiate metadata implementation for For User List | TFS Source 1412109029732 ALM TFS 1412109029738, due to (301)Moved Permanently
i am running v1.0.1.006.
When creating a new migration, the migration fails on user mappings with the following information. I am running v1.0.1.006.
Operation failed getUserList. Server Error: Server was unable to process request. ---> There was an error generating the XML document. ---> TF20507: The string argument contains a character that is not valid:'u0144'. Correct the argument, and then try the operation again. Parameter name: value
I posted the above issue some time ago on Stackoverflow and received a request for information from OpsHub support. I sent the requested information on 9/15 but have not received a reply. OpsHub support, please acknowledge if you have received my information and advise next steps. Regards, TSBob.
Got this error:
"Validation failed due to following reason(s), please contact
email@example.com fo an advanced solution
Error: 1) Template Customization or Template Mismatch Error
Reason: 1) Project(s) have some process template customization
which Visual Studio online do not support
Reason: 2) Process templates do not match. Please verify that the process template
in Visual Studio Online matches with that of the source project"
Is there a way to see more detailed info about the cause here, which Reason for exampe or which template..?
The error that you are getting would be encompassed in a Tree Widget. Please expand the tree and the trace should show you detailed Validation Failure over each project.
This would help you understand the individual failures.
I posted a question to stackoverflow (http://stackoverflow.com/questions/25555689/opshub-vs-online-migration-service-error-read-timed-out) 6 days ago w/o response so I thought I would post here in hopes of getting some feedback.
I'm running into an error using the migration utility after installing v1.0.1.006. I have previously used v1.0.1.001 to migrate a sandbox/test project with success. I attempted to use the .001 version to migrate the full project but ran into the Processing blocked problem. The recommendation was to update to the .006 version.
Now after running for 30-60 minutes, I get the following error:
com.opshub.eai.metadata.MetadataException: OpsHub-014371: Could not instantiate metadata implementation for xxx to xxx| TFS Source 1409181936489 ALM TFS 1409181936495, due to ; nested exception is: java.net.SocketTimeoutExeption: Read timed out.
Restarting the app appears to make the process resume, only to have the same error repeat after another 30-60 minutes. As a side-note, the Work Item never shows me a count like it did in version .001, it just says Running.
Whilst syncing work items and source code for all team projects, I receive the following error:
OH-SCM-009: Error occurred while sync. Value cannot be null.
Parameter name: key
I will zip up the logs and send to ovsmu.
Have tried the newly released 1.0.1.006, still getting an error with merges, but different this time:
OH-SCM-009: Error occurred while sync. The item $/XXX/XXX/XXX.cs does not exist at the specified version, or you do not have permission to access it.
Have sent updated logs back to ovsmu.
Getting error while giving Endpoint details while migrating to VSonlineError: Error creating the webProxy specified in the 'System.net/defaultProxy' configuration section.
Iam running opshub on win12 64bit os, .net framework also installed and The machine is behind proxy, hence added new environment variable with the name "_JAVA_OPTIONS based on http://opshub.com/main/index.php/ovsomu-proxy
added below variable
2. -Dhttp.proxyHost=ipaddress -Dhttp.proxyPort=8080 -Dhttp.proxyUser=username -Dhttp.proxyPassword=mypassword -Dhttps=false
can someone please let me the workaround for this issue.
When I try to run this, on the User Mapping page, I get the following error:
OH-TFS-Connector-0051: Operation failed getUserList. Server Error:
Object reference not set to an instance of an object.
I know this just came out but I hope these errors get fixed. I have tried a number of migration strategies and none of them have worked.
Can you please zip up and send us the log files from location <c or d>:\Program Files\OpsHub Visual Studio Online Migration Utility\logs and email them to firstname.lastname@example.org
Please include a reference to this request in your email
Please send us the zip of log files at the above email address (email@example.com). We need the logs to analyze and find the root cause for this issue. also, how many users are there in the source and target project?
I've got same error.
That's because I had a team project using the same project collection name.
The getUserList method calls ReadIdentity (TFS client object model) passing the wrong domain, team project domain instead of collection project domain.
Rename the project collection...
I was able to migrate most of the projects to VOS except for two. I'm getting the same error:
OH-TFS-Connector-0051: Operation failed getUserList. Server Error:
Object reference not set to an instance of an object
I will send the logfiles to firstname.lastname@example.org.
I am using the latest version of opshub and I am also getting the error when trying to migrate a small project with three users. I already sent the logs to the mentioned e-mail adress, but it returns that I have to state y request here first :) Please let me know what I can do to resolve this
It is not possible to migrate from one VSO team project to another using the free utility. Free utility is restricted to migrating from TFS On premise to VSO.
It is possible to migrate from one VSO team project to another using the commercial OpsHub Integration Manager (which is a paid product).
We're migrating 126 projects from tfs to tfs online. It failed halfway through (approx. 11k changesets) giving this error: OpsHub-012010: Processing blocked - earlier event(s) for entity 6117 have to be processed first.
When I hit retry and start the process again it just stops by itself after a few minutes and give the same message. I have no clue why it does that.
Logs are over here http://productdownloadtest.blob.core.windows.net/uploadedfiles/logs.zip Help appreciated. Thanks
There is not enough hard-disk space on your machine, Can you please make sure you can have some of the space free on your machine for C: (Windows Drive). Additionally You can follow below steps to free some space but that can take some extra time in processing.
Step: In your machine there is one extra drive created temporarily for processing change-set , the name of that drive may be O: (O Drive) , Go to that drive and delete all files and folder in that drive, On Next processing of change-sets, the required flies will be downloaded as needed hence it will take some extra time for processing
Thanks for your help, I had already extended the disk and made another try.
We're currently hitting the windows 260 chars limit for paths because your tools creates a 4 characters (5 with the slash) at the root of the virtual drive you create. Any way to fix this issue?
Can you please make sure you are using the latest version of the utility (we have fixed some bug in this area recently). If with the latest version you are still running into this issue, please send us the logs.