RESOLUTION:
- Enable verbosity and check for any log generated under these folder:
C:\ProgramData\Quest\Migrator for Notes to SharePoint\Log Files
Folder C:\ProgramData might be hidden
- Unfortunately, at the moment, there is no way to export the logs from link finalization tab.
1. The MNSP tool will add the link source information
and target field in link tracking database during migration.
In this case, the target field name is 'XXXX Doc'. But this column could not be found in target list
in SharePoint
during link finalization.
The column in SharePoint might have been changed by the user after data migration.
So changing the column name can fix this issue.
2. Did you remigrate those failed items before link finalize?
If not, it's better to remigrate those failed items(Select records based on UNID), then finalize the links.
Ensure the option of "Replace existing item" and "Use the Link Tracking Service" are selected.
- Re-migration can update the link tracking database which may fix the outdated data.
- If the issue has occurred in only few items, try to compare the difference in link tracking database
between the successful and failed item
using SQL command: select info from Linkage where SourceID=''
3. If the issue was caused by the column name that has been changed to "YYYY Doc":
An other option/solution is to recover the column name as "XXXX Doc" before link finalizing.
Then change back to "YYYY Doc" when finishing the link finalizing.
Try also these steps:
a. Open MNSP designer
b. Select note source in "Notes" Tab
c. Select "Site URL" and "List Name" in "SharePoint" Tab
d. Add new portal "Save Note Link to LTS..." in designer, and click it
e. All document links will add into LTS DB without migration any data into SharePoint.
See also this article:
https://support.quest.com/migrator-for-notes-to-sharepoint/kb/140013/the-item-already-exists-or-was-deleted-by-another-user-when-migrating-to-a-document-set-140013-
