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…

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.