Microsoft.VisualStudio.Services.WebApi.VssServiceResponseException: The controller for path '/_apis/wit/workItems/0' was not found or does not implement IController.

[anderssonpof]

I have been trying to debug some errors I'm receiving when testing migration of workItems.

Currently I'm stuck on two errors which I don't quite understand why they are happening.

When debugging in visual studio the exception is triggered at _targetDummyWorkItem.Save(); .

Microsoft.VisualStudio.Services.WebApi.VssServiceResponseException: The controller for path '/_apis/wit/workItems/0' was not found or does not implement IController.

For the second exception
I know that generally 'Work Item is not ready to save' points to a problem with iteration/area path mapping.
However, when I go through the code using debug, TF237124 happens when it tries to save image to dummyworkitem _targetDummyWorkItem.Save();

I feel that this doesn't point to an issue with iterations/area paths

configuration.json
migration.log

[MrHinsh]

I feel I agree with you. Its the /0 that inteagues me... that 0 should be the ID of the upload work item... and its missing.

[anderssonpof]

Yes, that one has me puzzled as well.
Now I will be honest here and my C# (including debugging) are far from good.

This is what I have gathered.

Two fields Release Notes Technical and Release Notes Functional
These have some text and one of them has 1 png image and the other 2 png images.

Images are downloaded and uploaded correctly, I can't discern any differences between the work items in source and target for these fields.

inprivate Microsoft.TeamFoundation.WorkItemTracking.WebApi.Models.AttachmentReference UploadImageToTarget(WorkItem wi, string filePath)
at this method var dummyWi = GetDummyWorkItem(wi.Type);
There is no DummyWorkItem so we try to create one.

_targetDummyWorkItem = type.NewWorkItem();
_targetDummyWorkItem.Title = TargetDummyWorkItemTitle;
_targetDummyWorkItem.Save();

I tried to get out some values of what it is trying to create

_targetDummyWorkItem	{Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem}	Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem
AreaId	372	int
AreaPath	"Migration Test"	string
Collection	null	
IterationId	372	int
IterationPath	"Migration Test"	string
NodeName	"Migration Test"	string
Reason	"New backlog item"	string
State	"New"	string 
Tags	""	string
Title	"***** DELETE THIS - Migration Tool Generated Dummy Work Item For TfsEmbededImagesTool *****"	string
Uri	{vstfs:///WorkItemTracking/WorkItem/0}	System.Uri
Count	73	int
IterationPath	"Migration Test"	string
NodeName	"Migration Test"	string
Reason	"New backlog item"	string
Revision	0	int
State	"New"	string
Tags	""	string
TemporaryId	-1	int
Title	"***** DELETE THIS - Migration Tool Generated Dummy Work Item For TfsEmbededImagesTool *****"	string
Uri	{vstfs:///WorkItemTracking/WorkItem/0}	System.Uri
AbsolutePath	"/WorkItemTracking/WorkItem/0"	string
AbsoluteUri	"vstfs:///WorkItemTracking/WorkItem/0"	string
LocalPath	"/WorkItemTracking/WorkItem/0"	string
OriginalString	"vstfs:///WorkItemTracking/WorkItem/0"	string
PathAndQuery	"/WorkItemTracking/WorkItem/0"	string
_targetDummyWorkItem.Title	"***** DELETE THIS - Migration Tool Generated Dummy Work Item For TfsEmbededImagesTool *****"	string

[anderssonpof]

I have been testing some more and I can't seem to find the cause.

Work items that doesn't make use of the fields Release Notes Technical and Release Notes Functional are created without issues. This makes me believe that there are some issue(s) with these fields or issue(s) with the data contained in these fields.

When I compare the json data of source and target (using /id/_apis/wit/workItems/id/) I cannot find any actual difference, which in my mind means the data is actually migrated correctly.

[MrHinsh]

Do you have any rules for work items or fields?

[MrHinsh]

The _targetDummyWorkItem.IsValid() also lists the fields that are the issue.

[anderssonpof]

I'm now running 16.0.10-Preview.4 and got a better error message. Much appreciated!
Dummy work item is being created correctly.
Found some more issues with field but managed sort these out with the help of the error messages.

I will consider this solved for now.
Thanks.

[chrissutton]

I'm on v16.1.0-Preview.3, and the same issue is happening. I fail with on _targetDummyWorkItem.Save(); line 263 in GetDummyWorkItem()

I get this exception:
Microsoft.TeamFoundation.WorkItemTracking.Client.VerbatimMessageException: TF237111: The current user does not have permissions to save work items under the specified area path. ---> System.Web.Services.Protocols.SoapException: TF237111: The current user does not have permissions to save work items under the specified area path.
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 MigrationTools.Tools.TfsEmbededImagesTool.UploadedAndRetrieveAttachmentLinkUrl(String matchedSourceUri, String sourceFieldName, WorkItemData targetWorkItem, String sourcePersonalAccessToken) in C:\git\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsEmbededImagesTool.cs:line 163
at MigrationTools.Tools.TfsEmbededImagesTool.FixEmbededImages(WorkItemData wi, String oldTfsurl, String newTfsurl, String sourcePersonalAccessToken) in C:\git\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsEmbededImagesTool.cs:line 94

[19:18:18 ERR] [16.0.10-Local.1] EmbededImagesRepairEnricher: Unable to fix HTML field attachments for work item 0 from

[MrHinsh]

Is your account a Collection Admin on the Target?

Can you manually create a new work item in the root of the target?

Are there any required fields on the Task work item?

[chrissutton]

I'm not a collection admin, I have broad permissions for one board/area path where we are exporting these tickets.

I'm pretty sure I can't edit at the root of the project. I'll ask once people at the client are online.

There is one required field, that I have to set when I create a User Story in the board I have access to in the UI.

Before .Save() happens in GetDummyWorkItem() , _targetDummyWorkItem.Validate() passes in my scenario. Shouldn't that fail if there is a required field that isn't properly set?

Anyway, any suggestions are welcome. I won't get collection admin permissions for this job.

[MrHinsh]

Collection admin is technically required for the tool to function correctly.

I'm pretty sure I can't edit at the root of the project.

That would be it...

Before .Save() happens in GetDummyWorkItem() , _targetDummyWorkItem.Validate() passes in my scenario. Shouldn't that fail if there is a required field that isn't properly set?

We override the rules engine so if that is working then it will ignore the required fields.

[chrissutton]

Ah, thanks, unfortunately I don't think I'll get that kind of access. Do you think not being a collection admin the cause of the api call not being able to save in this case? Everything else seems to be able to save properly, except this one scenario.

I'll work on the required field path. Thanks

[chrissutton]

I appreciate your help with this. I updated the dummy work item AreaPath to where my account has permissions and the dummy work item now can .Save(). So just a permissions issue as you noted.

[louisik1]

The short answer for me was I needed to use "PATCH" instead of "POST".