3
Vote

System.Web.Services.Protocols.SoapException: SourceAreaId

description

I‘m trying to use this tool for migrating some WIs from one 2012 server to another, and I got this error.

Is there anyone can help me out here?



System.Web.Services.Protocols.SoapException: SourceAreaId
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.ClientServiceProxy3.GetWorkItemLinkChanges(Int64 rowVersion)
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.WorkItemServer.GetWorkItemLinkChanges(String requestId, Int64 rowVersion)
at Microsoft.TeamFoundation.Migration.Tfs2010WitAdapter.Tfs2010WorkItemServer.GetWorkItemLinkChanges(String requestId, Int64 rowVersion)
at Microsoft.TeamFoundation.Migration.Tfs2010WitAdapter.TfsMigrationWorkItemStore.GetLinkChanges(Int64& linkChangeIdHighWaterMark, DateTime excludeItemsChangedBeforeTime)
at Microsoft.TeamFoundation.Migration.Tfs2010WitAdapter.TfsMigrationWorkItemStore.GetItemsWithLinkChanges(Int64& linkChangeIdHighWaterMark, DateTime excludeItemsChangedBeforeTime)
at Microsoft.TeamFoundation.Migration.Tfs2010WitAdapter.Linking.Tfs2010LinkProvider.GenerateNextLinkDeltaSlice(LinkService linkService, Int32 maxDeltaSliceSize)

comments

AdamDriscoll wrote May 13, 2016 at 8:53 PM

We worked around this by making sure the account doing the migration had the "View system synchronization information" permission allowed at the collection level.