Skip to main content

Upgrading TFS–Don’t change the language of your TFS deployment during upgrade

I helped a customer upgrading their existing TFS 2010 environment to TFS 2015. Where the old version of TFS was using the English bits, for the 2015 installation they provided me the Italian installation media.

When I started the configuration process to trigger the upgrade, the installation wizard gave the following warning:

image

OK, it’s just a warning I thought, what harm could be done? So I clicked on the checkbox next to “I have read the above warning and would like to continue anyway”?

Turns out, that this was not one of my brightest ideasSmile. A few hours into the upgrade process, a failure popped up;

[Info   @19:00:17.421] Executing step: 'Add Process Templates' ConfigurationProcess.AddProcessTemplates (716 of 765)

[Info   @19:00:17.439] Loading process template: Deploy\ProcessTemplateManagerFiles\1033\MsfAgile\Metadata.xml

[Error  @19:00:17.476] Value cannot be null.

Parameter name: input

[Info   @19:00:17.509] System.ArgumentNullException: Value cannot be null.

Parameter name: input

   at System.Xml.XmlReaderSettings.CreateReader(Stream input, Uri baseUri, String baseUriString, XmlParserContext inputContext)

   at System.Xml.XmlReader.Create(Stream input, XmlReaderSettings settings, String baseUri)

   at Microsoft.TeamFoundation.Admin.Deploy.Application.ProcessStepPerformer.ProcessTemplateMetadata..ctor(Stream metadataResourceStream, AddProcessTemplateStepData template)

   at Microsoft.TeamFoundation.Admin.Deploy.Application.ProcessStepPerformer.ProcessTemplateMetadata.GetMetadata(IVssRequestContext requestContext, ServicingContext servicingContext, AddProcessTemplateStepData template)

   at Microsoft.TeamFoundation.Admin.Deploy.Application.ProcessStepPerformer.AddProcessTemplates(IVssRequestContext targetRequestContext, ServicingContext servicingContext, AddProcessTemplatesStepData stepData)

   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformHostStep(String servicingOperation, ServicingOperationTarget target, IServicingStep servicingStep, String stepData, ServicingContext servicingContext)

   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformStep(String servicingOperation, ServicingOperationTarget target, String stepType, String stepData, ServicingContext servicingContext)

   at Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformServicingStep(ServicingStep step, ServicingContext servicingContext, ServicingStepGroup group, ServicingOperation servicingOperation, Int32 stepNumber, Int32 totalSteps)

[Info   @19:00:17.509] [2016-07-14 17:00:17Z] Passaggio del servizio 'Add Process Templates' non riuscito. (Operazione del servizio: 'ToDev14M95Deployment'; Gruppo di passaggi: 'UpgradeProcessTemplates')

[Info   @19:00:17.509] [StepDuration] 0,0883791

[Info   @19:00:17.510] [GroupDuration] 0,0900522

[Info   @19:00:17.510] [OperationDuration] 0,252088

[Info   @19:00:17.510] Clearing dictionary, removing all items.

[Error  @19:00:17.511]

Messaggio eccezione: TF400711: errore durante l'esecuzione del passaggio del servizio 'Add Process Templates' per il componente UpgradeProcessTemplates durante ToDev14M95Deployment: Value cannot be null.

Parameter name: input (tipo TeamFoundationServicingException)

Traccia dello stack eccezione:    at Microsoft.TeamFoundation.Framework.Server.ServicingContext.FinishStep(Exception exception)

   at Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformServicingStep(ServicingStep step, ServicingContext servicingContext, ServicingStepGroup group, ServicingOperation servicingOperation, Int32 stepNumber, Int32 totalSteps)

   at Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformOperations(Int32 stepsToPerform)

   at Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.Execute(Int32 numberOfStepsToPerform)

   at Microsoft.TeamFoundation.Admin.UpgradeConfigDbDriver.Execute()

   at Microsoft.TeamFoundation.Admin.ConfigureUpgradeConfigDB.Run(ActivityContext context)

I had no clear indication if this issue was caused by the language change, but the fact that I had to click a checkbox had made me suspicious.

So I asked to download the English installation media, restored the backup and restarted the upgrade process. This time the process completed without any errors.

Lesson learned; don’t ignore warnings…

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more