• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 15 subscribers
  • Views 4884 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DocLink - Unwanted "http://" added to the link during DOC Migration

cagri.hekim
over 6 years ago

Hello, 

I have a small question that I already checked in the Forum, yet could not find any answers.

I have migrated Notes Doc Rich Text field to a Word Document in a folder in Root.

The issue that we face right now is that, the tool adds “ http://“ just before the location path inside the link for some reason.

And interestingly, it is added only for some of the links but not all the links in the word doc.

 

From the following picture, you can see the row starting with Plan & Boards, in which the unwanted “http://“ field, circled with Red Color.

For the link in the second row, everything works fine, there is no “ http://“ added in the beginning of the link.

 

Do you know what would be the reason of this and how to solve It?

Parents
  • 0 over 6 years ago

    Hello Cagri,

    Thank you for posting to the Migrator for Notes to SharePoint (MNSP) forum. Unfortunately, SharePoint does not support absolute paths. Example: "x:\folder\file.doc" 

    Therefore MNSP is not able to support the migration of this type of link.

    Thanks,

    Trevor Taegder
    Senior Technical Support Engineer

    Quest | Support

  • 0 over 6 years ago in reply to Trevor Taegder

    Hi Trevor,

    Thanks for the answer. I would quickly like to ask you something more. 

    We have verified that file:\\<file path> format is working fine within SharePoint to open local folder.

    Is there any option that we can move the original link Example: "x:\folder\file.doc" as "file:\\x:\folder\file.doc" when exporting using Quest MNSP.

     

    Is there any workaround to do this ? 

    We really need to move the absolute paths as it is to the Word document, which we are placing to the SharePoint document library.

     

    Look forward to hearing from you,

    Best regards,

    CH

Reply
  • 0 over 6 years ago in reply to Trevor Taegder

    Hi Trevor,

    Thanks for the answer. I would quickly like to ask you something more. 

    We have verified that file:\\<file path> format is working fine within SharePoint to open local folder.

    Is there any option that we can move the original link Example: "x:\folder\file.doc" as "file:\\x:\folder\file.doc" when exporting using Quest MNSP.

     

    Is there any workaround to do this ? 

    We really need to move the absolute paths as it is to the Word document, which we are placing to the SharePoint document library.

     

    Look forward to hearing from you,

    Best regards,

    CH

Children
  • 0 over 6 years ago in reply to cagri.hekim

    Hi Cagri,

    Currently, there is no workaround within MNSP for this issue.

    You could change the path in the source to "\\server\share".

    Or

    You could change the path in the target and replace "http://" with "file://".

    I understand that having MNSP perform this type of conversion during the migration would likely be the most desired option. In order to bring this Enhancement Request up to the product team for consideration in a future version of MNSP, a Service Request would need to be created. You can create a new Service Request using the following link:

    https://support.quest.com/create-service-request 

  • 0 over 6 years ago in reply to Trevor Taegder

    Hi Trevor,

    Thanks for the help. I have submited service request yesterday. I have not got notified about the made sumission though, yet I believe I will be contacted soon.

    Look forward to haering form the team for some instructions.