XML parsing : illegal xml character migration error

by XDK 15. March 2016 13:09

Exception:

Microsoft.TeamFoundation.Migration.Toolkit.ErrorManagement.MissingErrorRouterException: Runtime error does not meet the error routine policy and there is no conflict manager to log a conflict. ---> System.Data.UpdateException: An error occurred while updating the entries. See the InnerException for details. ---> System.Data.SqlClient.SqlException: XML parsing: line 1, character 78999, illegal xml character

Explanation:

This error might occur when stacktraces are pasted directly into the HTML fields in the work item. In my case, the stacktraces with illegal characters were in Repro Steps field.

Workaround:

I ignored the work items which were causing the failure using the below clause in the migration query.

And processed the ignored work items manually.

Tags:

Azure DevOps on-premises

The updated arguments of a build process template not getting refreshed in the process section of a build definition

by XDK 2. March 2016 18:53

Workaround:

  • Delete the registered build process template in the collection database

          use <Collection database>;
          delete from tbl_BuildProcessTemplate where ProcessTemplateID = 'updated Process Template ID';

  • Create the build definition again

Tags:

Azure DevOps on-premises | TFS 2012

How to create a report to review changesets that are checked in without work item association?

by XDK 26. February 2016 13:54

Solution:

You may query the TFS cube thru excel to pull the information. Select the fields and configure as shown in the below screenshot.

 

Tags: ,

Azure DevOps on-premises | TFS 2012 | TFS 2013 | TFS 2015

Meaning of AcceptYours,AcceptTheirs and AcceptMerge during merge conflicts

by XDK 18. February 2016 09:13

Explanation:

AcceptYours - Local version is to be used for merge
AcceptTheirs - Server version is to be used for merge
AcceptMerge - Resolve conflict by doing manual merge

Tags: , , ,

Azure DevOps on-premises | TFS 2012 | TFS 2013 | TFS 2015

MIssing "Find by Status" and "Find by Wildcard" in Source Control Explorer

by XDK 11. January 2016 12:49

Solution:

"Find by Status" and "Find by Wildcard" plug-ins are from TFS power tools. You need to install TFS power tools to gain access to "Find by Status" and "Find by Wildcard" menus.

Tags:

Azure DevOps on-premises | TFS 2012 | TFS 2013 | TFS 2015 | Visual Studio 2010 | Visual Studio 2012 | Visual Studio 2013 | Visual Studio 2015

About the author

My name is Xavier Dilip Kumar Jayaraj having 13+ years of IT experience which includes solid experience and depth Knowledge in Application Life Cycle Management, Configuration Management, Implementation and Support using TFS on-premises and Azure DevOps. I have invested in gaining DevOps knowledege to expertise with Cloud Computing providers namely Microsoft Azure and Amazon Web Services in recent years. I am very positive to learn and adapt emerging technologies to client’s environment.

Microsoft Certified: Azure Administrator Associate

Microsoft Certified: Azure DevOps Engineer Expert

DevOps Engineer Certificate Program | Transcript 

OTP-AWSD5: AWS IoT: Developing and Deploying an Internet of Things

[PCEP-30-01] PCEP – Certified Entry-Level Python Programmer

Quotes I Like

"Failure will never overtake me if my determination to succeed is strong enough."  - Dr. APJ. Abdul Kalam

"Always be yourself, express yourself, have faith in yourself, do not go out and look for a successful personality and duplicate it." - Bruce Lee

"Technology is just a tool. In terms of getting the kids working together and motivating them, the teacher is the most important." - Bill Gates

"Innovation distinguishes between a leader and a follower." - Steve Jobs

CategoryList

Disclaimer

The information provided here is based on my expreriences, troubleshooting and online/offline findings. It can be used as is on your own risk without any warranties and I impose no rights.