The error message i'm getting is "current version of the following service is not supported: GitOdb".
Build pipeline is for ASP.NET CORE(v3) API project.
When i click on the error it says "Build not found"
After investigation, there is a recently event of availability degradation of Azure DevOps, which affected these services, and it has been resolved now. If you want to know more information, please click here: https://status.dev.azure.com/_event/188718946 .
The issue is now fully mitigated. To mitigate, we stopped updates and
upgraded the impacted databases. We recognize the wide impact this had
to our customers in this region and will be following up on learnings
and improvements to prevent the chance of recurrence. We apologize for
the impact this caused.
In this case, many users encountered the same problem (starting a build pipeline immediately fails with TF400860: The current version of the following service is not supported: GitOdb. Version: 1700, MinVersion: 1700), which has now been fixed.
Related
I'm trying to create a build and release to a actors service in Visual Studio Online. I already created build and release to anothers services fabric without problem. But with this specific service I getting the error below:
The BuildLayout of the application in E:\SFabric\SP\SP2DS\Fabric\work\ImageBuilderProxy\AppType\SchedulerServiceAppType is invalid. Config is missing for service SchedulerServicePkg.
The first time the release works fine, but after the first version is released, the others releases I got this error.
The others services are Stateless, I dont know why this problem happens and just with this service that is Stateful.
New Information
I'm trying to change advantages setting and I got successful sometimes.
Even that, I want to know how I do correctly
# Novac - Just noticed a duplicate post on Github addressing this specific issue. More importantly, a member of Azure's Service Fabric Dev team is actively engaged and waiting for your response to his followup questions - ref snip below:
Currently tracked via GitHub issue:https://github.com/Azure/service-fabric-issues/issues/802. Strongly recommend redirecting this conversation to the Github thread/url above.
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.
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
I noticed this afternoon that my Bluemix IoT Application was in the 'Unknown' state. When I mined into the app to see what the problem could be, I got the following pop-up:
App staging failed in the buildpack compile phase
I haven't made any changes to my NodeRED flows in months, and if I spin up a new IOT Foundation app, it starts just fine.
Any ideas on what is going on here?
A recent update to the underlying application stack has caused an incompatibility with older versions of the IoTF boilerplate.
The fix is to edit your application's package.json file and remove the 'mqlight' entry under the dependencies section. New instances of the boilerplate already have this entry removed - hence why they work.
Perhaps check the bluemix server status at https://developer.ibm.com/bluemix/support/#status
There were some issues reported around scheduled maintenance. There are also buildpack updates scheduled.
I started a migration source code from TFS (not work items) to Visual Studio Online and it has been running for more than 24 hours but the status still shows "Reading and Analysis". CPU usage for the application is showing 0.
Should I keep waiting or is there a way to find out if an exception is thrown? I am not too familiar with debugging procedure for Java applications.
Which version you are using?
There is performance issue with label which is fixed in version 1.0.1.005.
Can you try current version?
Error : TF14045: The identity 19b7a3e0-b25b-4c48-90a8-813202d6d1b4 is not a recognized identity.
above error comes while connecting to tfs server that's why utility continuously displaying reading and analysis because everytime utility connects to source TFS for fetching total number of change sets and lables it encounters same error.
As per microsoft blogs, people are encountering this type of issue after upgradation/db restore for collection. After this process when user tries to connect tfs, it always throws the same error which you have encountered. Have you done any of the above process for the collection you are trying to migrate? You can refer following thread which contains resolution for same error.
http://social.msdn.microsoft.com/Forums/vstudio/en-US/b67ad1d6-d763-4602-bf14-489a3389a30d/getting-tf14045-the-identity-guid-is-not-a-recognized-identity-after-db-restored?forum=tfsadmin
Let us know in case you won't be able to resolve this with the above information and also in case you have not done any upgradation/db restore procedure. In that case we would like to know your source tfs version and older upgrade history of this instance (If any).