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

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more