OPS Hub - unable to migrate project - azure-devops

I am trying to migrate one project from tfs on prem to VSTSO . I am getting the following error
Ops Hub error
I have successfully migrated couple of projects before but this one wont go . I did notice one thing when i was migrating . It gave different name to the default collection as you see in the screen shot . I have deleted the account and recreated the account and still getting the same.Please advise.
thanks

The issue seems to be a recent change in VSTS as Nicolas pointed out. Currently, the OVSMU tool will not be usable directly. We would be releasing a patched version early next week which will solve this issue.

[Update]: This change is part of the following change annoncement: https://www.visualstudio.com/news/2016-apr-13-vso
I've been able to solve this "page not found" exception by using fiddler and the following rule: oSession.url = oSession.url.Replace("/NameOfTheCollection/Services/v3.0/","/defaultcollection/Services/v3.0/"); But I face another issue on HubOps.
Finally, I used TFS migration tools + fiddler rule described above and I'm able to move forward on this migration.
Another option is to contact microsoft in order to ask for early acces of TFS - VSO migration tool: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2264946-import-data-from-tfs-on-prem-into-vs-team-services
BR

Related

Red gate DLM Automation binding error using VSTS

I'm using Red gate DLM Automation version 2 on VSTS. I installed DLM on the build server, it's fully licensed, and I have noth the build and release VSTS plugins installed. But now, when I perform a build on VSTS, I receive the following error message:
System.Management.Automation.CmdletInvocationException: A parameter cannot be found that matches parameter name 'transactionIsolationLevel'. ---> System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'transactionIsolationLevel'.
My initial guess is that I have a version conflict between some Red Gate PowerShell libraries, but I cannot find any further information on this error.The build server is running PowerShell v4. The SQL code being built does not have any references to "transaction isolation" in it, but I don't think that's the problem. I have completed successful builds on this VSTS server in the past and am now confused what caused this error to start appearing.
Thank you!
You need at least 2.0.3 of the DLMA install on the local agent to work with the VSTS plugin - we added the Transaction Isolation Level option very recently, and VSTS auto-updates, but the DLMA install doesn't.
Sorry about that - we are looking into better update / communication mechanisms to keep these things in sync in future (or at least tell you what the problem is) but aren't quite there yet.
If you're still having trouble after updating the DLMA install on the local agent, please do get in touch via support#red-gate.com and we'll sort it out for you.

Visual Studio Team Services (was VS Online) not showing GitHub repository type

I'm trying to setup an integration between my GitHub and VSTS account.
I'm creating a build definition to build and deploy my code to my azure web app. From all the things I've read online (I've been trying to make this work for at least some 3h now) this should be so simple I'm reconsidering calling myself a developer... =/
I've added the Service Endpoint:
But it doesn't show up at the build definition:
The other service endpoints for azure work fine, I'm able to set them at the build definition, but the GitHub just won't work! I've tried signing out, using chrome's private window, removing and re-adding the endpoint, using IE, nothing makes that damn thing show up as an option in the dropdown.
Does anyone have any ideas?
EDIT - ScreenCast
http://screencast-o-matic.com/watch/cDif6XiUSZ
After 3 days and no answer from MS I kept trying to figure it out and it seems this account is running on an old version.(?)
I have another account that's working fine and I started to compare both, here's why I think that:
Different versions
no online column and different header (Account profile vs Account/acc_name)
Perhaps you are right that your account is running in an old server.
I created one in India South and experienced the same behavior.
Then I deleted it and created one in South US and I can see my GitHub repository.

Problems when migrating from on-premises TFS to VSO using OpsHub

We are trying to migrate from our on-premises TFS 2010 to Visual Studio Online (VSO). We did it a first time just to test it out. The OpsHub application stopped a couple of times, but we finally succeeded. We did our testing and deleted the project from VSO.
The second time dident go so well. It gives the following error after migrating a lot but not all of our change sets:
com.opshub.eai.config.exception.ConfigServiceException:
OH-CONFIG-0101: Exception while calling service, underlying cause :
could not execute query.
We can press OK and navigate into another view in the application but the same error occurs on every view. We have restarted the application, the service and even the server. We always get the same error. We decided to uninstall the application and reinstall it. That solved the problem, but it appears again after we have migrated about 60% of our source code (a day or so).
So, after 3 re installations we are about to give up. It doesn't crash on the same change set every time.
Does anyone know a way around this? Is there any way we can see the real cause of the problem and fix it?
We are using version V1.3.000B000 (latest version).
Not sure if this is the proper place to post the question, but OpsHub is referring to stack overflow for support.

VSO Migration: Unable to retrieve information for security object $PROJECT:vstfs:///

I have installed OpsHub and trying to migrate the source code from VSTF2013 to VSO. After selecting the TFS Endpoint and VSO Endpoint, clicking on Next. When trying to load the projects to be migrated I am getting this error, "TF50608: Unable to retrieve information for security object $PROJECT:vstfs:///Classification/TeamProject/faedd6e7-e2bc-4f91-917f-3823c951e71b, it does not exist."
When I select some other TPCs in the same VSTF server, I am able to load the projects in VSTF. Could not understand this error code if this is related to security configuration at TPC level or OpsHub is trying to load some project which is does not exist?
I have done some search on this error code TF50608, looks like this issue can occur if any Team Project is deleted and created with the same name. I am able to connect to TPC and load the projects using TFS Administration Tool (http://tfsadmin.codeplex.com/) but OpsHub fails to load the projects.
Is there any work around to skip this error and continue with the selection of the Team Project?
We have verified it is a defect. It will be resolved in the next build coming out soon.
use VERSION 1.0.1.005, in which this issue is resolved

Publish-AzureServiceProject is not updating files on the cloud

I have a PHP Azure project which I have to manage with Powershell cmdlets. One of these, Publish-AzureServiceProject doesn't seem to be detecting file changes so these are not updated on the cloud (even though no errors are displayed).
I have remote desktop'd into the machines and the code is definitely not updated from weeks ago.
If I deploy to the local emulator, it is fine but this is much more obvious because it displays "removing old package" and "creating local package". The cloud package definitely contains the latest files, so the packaging is working fine.
Can anyone tell me how to force the publish to update the files on the cloud and more importantly, why this is not happening? Also, if I force the update, will it deploy to a new box and get a new IP Address?
Thanks.
It seems to work now.
I have removed and reinstalled azure libraries from my machine and created a new project from scratch and copied the original files over into it. I have not included diagnostics (not sure if that's an issue) and I have modified the Publish-AzureServiceProject script to select the subscription each time before it publishes.
It is possible that the subscription confusion was not helping (I have two Azure subscriptions and it might have used the wrong one at some point and done something weird) and also it was possible there was some conflict with various versions of the Azure SDK since I have been using it for over 6 months but at the moment, all is good.
A related article on my blog here: Problems with PHP Azure
Thanks for the interest