Error in XML document - nmsp

Hi, I have 6 jobs that I would like to run through a .bat file.  I used to be able to do this.  

When we upgraded to the latest version, I keep getting the error "Migration Failed: There is an error in XML document (76,5)".  The line number is different for the other job.

However, these jobs all run with no problem when I run them individually through the Migrator designer.

Any thoughts?  Thanks much.

  • Thanks for posting in the Migrator for Notes to SharePoint (MNSP) community forum. I understand that you are running into issues when attempting to run a migration using command line arguments within a batch file. What exact version of MNSP are you currently using (Help | About)?


    I can then try running a test in my lab environment using the same version of MNSP as you.

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • In reply to Trevor Taegder:

    Thanks. We are using 6.9.1.2572.

    We built it using the designer and the jobs run fine through the designer. However, we get the XML error when running the bat file.

    The other weird thing is, which is a separate issue from above, we built a job using the same version of the tool (but the test version only) on one machine and tried running it on the version with a license on another machine. We were unable to open the job and got the XML error as well for this scenario.
  • In reply to jmrivera:

    Thanks for the update. I installed Migrator for Notes to SharePoint (MNSP) version 6.9.1.2572 in my lab environment and was able to migrate from the command-line successfully.

    The following KB article may be related to the issue you are experiencing:

    support.quest.com/.../113915

    In order to investigate further, we would need a copy of the job file you are using and the complete command you are using with arguments. The best way to send in this data, while maintaining privacy, would be to create Service Request:

    support.quest.com/create-service-request

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • In reply to Trevor Taegder:

    We removed this line from the job xml file and we were able to run the job through the command line.

    <ReUpdateMmFieldByCsom>false</ReUpdateMmFieldByCsom>

    However, we got another error:
    Migration Failed: Could not load file or assembly 'Quest.NSP.Transform.Notes' or
    one of its dependencies. The system cannot find the file specified.
  • In reply to jmrivera:

    Thanks for the update. I am glad to hear you were able to get past the first XML error you are experiencing. I understand you are now experiencing a new, "Could not load file or assembly 'Quest.NSP.Transform.Notes'" error.

    1.) Have you tried running the batch file from within a Command Prompt that was created "as Administrator"? Migrator for Notes to SharePoint (MNSP) does rely on third-party APIs, such as the Notes Client API, which can be limited if MNSP is not running with elevated permissions.

    2.) This type of error can also occur when MNSP is unable to launch the Notes Client API. Are you able to launch the Notes Client and connect to the Domino server on the MNSP migration server?

    3.) If you open MNSP Designer | Tools | Options | Notes, is the Notes password set?

    4.) Sometimes there can be errors with MNSP launching the Notes Client API when it is not set as part of the system PATH variable. The following KB article provides more details:

    support.quest.com/.../44056

    Let me know if any of these suggestions help lead to a resolution of the issue you are experiencing.

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • In reply to Trevor Taegder:

    1.) Have you tried running the batch file from within a Command Prompt that was created "as Administrator"? Migrator for Notes to SharePoint (MNSP) does rely on third-party APIs, such as the Notes Client API, which can be limited if MNSP is not running with elevated permissions.
    --> Yes, I run it as admin

    2.) This type of error can also occur when MNSP is unable to launch the Notes Client API. Are you able to launch the Notes Client and connect to the Domino server on the MNSP migration server?
    --> We can run the job on the designer but not on the command line. We can connect to LN.

    3.) If you open MNSP Designer | Tools | Options | Notes, is the Notes password set?
    --> The password is set properly

    4.) Sometimes there can be errors with MNSP launching the Notes Client API when it is not set as part of the system PATH variable. The following KB article provides more details
    --> The system variables are also set properly
  • In reply to jmrivera:

    Thanks for the update. I have a few more suggestions/questions:

    1.) Have you tried creating a simple brand new job file from scratch as a test and see if that can be used in your batch file?

    2.) In MNSP Designer, can you go to Tools | Options and on the General tab, verify that all the locations got updated to the new "Quest" path during the software upgrade?



    3.) What version of Windows are you using for the MNSP migration server? What is the path that the Notes Client was installed in?

    If you are using Windows Vista or Windows 7, it is recommended to install the Notes Client to a location outside of the Program Files folder, such as C:\Lotus\Notes.

    3.) My next suggestion would be to uninstall MNSP, then open a Command Prompt as Administrator and launch the MNSP client install MSI file from within the administrative Command Prompt. Try the batch file migration again after reinstalling MNSP.

    If you continue to experience the same issue, then the next step would be to investigate this issue further with a Technical Support Engineer by creating a Service Request:

    support.quest.com/create-service-request

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • In reply to Trevor Taegder:

    Thanks. Here are the information

    1. Yes, we created a new job but has the same error below. The DLL is there in the machine. Why is it saying that it cannot load it?

    General: [General] Cookie Expiration, Cookies expire 10/11/2017 9:06:23 PM
    Migration Failed: Could not load file or assembly 'Quest.NSP.Transform.Notes' or one of its dependencies. The system cannot find the file specified.


    2. All the quest default path are there

    3. We have Windows Server 2008 R2