How to avoid the double-hop issue (4306073)

User cannot use any of the features that require direct SQL database read/write procedures (e.g. Workflow Instances, Preserve item IDs in Document Libraries, Preserve Deleted AD users). You may find that the migration log shows no errors, but also, that there are no logged items for the workflow instances.

The user can establish a connection to the Metalogix Extensions Web Service (MEWS) and can migrate content. However, they do not get the full set of features available. When they right click on the connection node that uses MEWS, the search option is either:

• Disabled or grayed-out
• Accessible, but it returns the "Logon failed for user NT Authority\Anonymous Logon" error message.

  

• When we make the SQL database RPC T-SQL calls, it is under the name of the migrating account (e.g. Domain\user) for auditability.
• However, this identity cannot be persisted from the Web Service to the SQL back-end in an NTLM authentication scenario.

The most common way to work around this problem is to avoid using the MEWS connection adapter. In this case, the Content Matrix Console is run on the target SharePoint WFE or App server and a Local Object Model (OM) connection is made. The source SharePoint environment is connected using the Read-only Database Connection.

If it is not possible to reconfigure the environment as described above, there is a built-in utility called "DB Override" which will also resolve the issue. To use this utility, you must have a SQL authentication account available.

How to Use the DB Override Utility

1. Open the C:\Program Files (x86)\Metalogix\Content Matrix Consoles\SharePoint Edition\SupportUtilities folder.
2. Copy the executable to each WFE Server in the source SharePoint farm (i.e. the farm you are remotely connecting to).
3. On each source WFE server, launch DBOverride.exe.
4. Enter the SQL authentication account credentials.

   

5. Press Encrypt. This will encrypt the user name and password by machine.
6. Press "Save". The tool will open the C:\ProgramData\Metalogix folder. Save the file as DBOverride.xml. If this folder does not exist, you must create it manually.
7. Close the DB Override Utility dialog window.
8. Run IISRESET on the server.

Note: Make sure to perform steps 3 to steps 8 on each WFE server.

There is an alternate method of avoiding this issue by configuring Negotiate (Kerberos) Authentication on the SharePoint farm. Please see this document for more information.