System.AggregateException while migrating tickets

[ArpitaDixitM]

Hello,

I am new to the tool and I was successfully able to migrate workitems between organizations. In one of the work items I am facing this issue.

Error while running WorkItemMigration
System.AggregateException: One or more errors occurred. ---> Microsoft.TeamFoundation.WorkItemTracking.Client.UnexpectedErrorException: There is a problem on the server. Contact your Azure DevOps Server administrator. ---> System.Web.Services.Protocols.SoapException: %error="600177";%:AddConstant: The following string is not supported by database collation: %String="Cici Chen??";%.
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.RetryHandler.HandleSoapException(SoapException se)
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.WorkItemServer.Update(String requestId, XmlElement package, XmlElement& result, MetadataTableHaveEntry[] metadataHave, String& dbStamp, IMetadataRowSets& metadata)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.SendUpdatePackage(XmlElement package, XmlElement& result, Boolean bulk)
--- End of inner exception stack trace ---
at VstsSyncMigrator.Engine.WorkItemMigrationContext.d__36.MoveNext() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 597
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at VstsSyncMigrator.Engine.WorkItemMigrationContext.InternalExecute() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 257
at MigrationTools._EngineV1.Processors.MigrationProcessorBase.Execute() in D:\a\1\s\src\MigrationTools_EngineV1\Processors\MigrationProcessorBase.cs:line 47
---> (Inner Exception #0) Microsoft.TeamFoundation.WorkItemTracking.Client.UnexpectedErrorException: There is a problem on the server. Contact your Azure DevOps Server administrator. ---> System.Web.Services.Protocols.SoapException: %error="600177";%:AddConstant: The following string is not supported by database collation: %String="Cici Chen??";%.
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.RetryHandler.HandleSoapException(SoapException se)
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.WorkItemServer.Update(String requestId, XmlElement package, XmlElement& result, MetadataTableHaveEntry[] metadataHave, String& dbStamp, IMetadataRowSets& metadata)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.SendUpdatePackage(XmlElement package, XmlElement& result, Boolean bulk)
--- End of inner exception stack trace ---
at VstsSyncMigrator.Engine.WorkItemMigrationContext.d__36.MoveNext() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 597<---
[15:24:52 ERR] [v14.3.7] WorkItemMigration The Processor MigrationEngine entered the failed state...stopping run

Is this because of the emoticon in the creator name?

I am using version 14.3.7 and is there any workaround for this?

Also, I wanted to know can I get error logs in a file instead of the command line?

Thanks,
Arpita

[MrHinsh]

@ArpitaDixitM the log files are automatically created in the installation folder. You can use winget --info to find the location for installs... for me its %LOCALAPPDATA%\Microsoft\WinGet\Packages.

For my install the logs are located in C:\Users\MartinHinshelwood\AppData\Local\Microsoft\WinGet\Packages\nkdAgility.AzureDevOpsMigrationTools_Microsoft.Winget.Source_8wekyb3d8bbwe\logs

For the other issue with the icon, it seems that the database collation that you are using for Azure DevOps on the target environment does not support that icon.

You will not be able to migrate that work item!

What version of TFS/ADO is your target environment, and what is the database collation?

[ArpitaDixitM]

Hi @MrHinsh
Thank you for your response.
ADO Version Dev19.M231.1 (AzureDevOps_M231_20231228.1)

How do I check the database collation settings? As per what I read it is selected by default based and based on SQL server that ADO is using.
So, the difference between my source and destination:
Source is Hosted xml based and hosted in region West US 2.
Target is Inherited process based and hosted in region North Europe.

[MrHinsh]

If both the source and the target are Azure DevOps, then its the API that does not support this character.

So that we can support any version from 2013-> ADO we use the ObjectModel API. This is based on soap and I'm guessing does not support this character. You will have the same issue with Excel integration and other tools.