Chatta subito con l'assistenza
Chat con il supporto

Content Matrix 9.10 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration Promotion of First Level Subsites to Site Collections MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration Link Correction StoragePoint Content Migration
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Migrating SharePoint On Premises Using Proxies, Load Balancing or Alternate Access Mappings Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline' Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline'

Question

What does it mean when the message ERROR, the batch will be resubmitted to the import pipeline displays in the Information section of the Log Item Details dialog when a migration is performed using the Import Pipeline?

Azure Migration Error

Answer

You may see this message (which will begin with either ERROR or FATAL ERROR) during a migration when a batch fails to migrate in its entirety.  To address this issue, increase the value of the environmentsettings.xml key MaxAzureBatchRetryCount.  This key controls the maximum number of times Content Matrix will resubmit the batch until it is successfully migrated.  (The default value is 5.)

The batch retry mechanism will also be triggered for the following errors:

·Please try again. CallStack -- at Microsoft.SharePoint messages

·Access denied

·Save Conflict The system cannot find the path specified. (Exception from HRESULT: 0x80070003)

·Updates to system roles is not allowed.

·List does not exist

For any error not listed above (such as Item Does Not Exist, which is different than List does not Exist), a batch will be resubmitted only if the error message is added to the environmentalsettings.xml key ErrorMessagesForRetryAzureBatch.

IMPORTANT:  If adjusting this setting does not resolve the issue, the error may be with the CSOM connection.  See Retrying Failed Document Copies to SharePoint Online CSOM Connections for details.

Item Count at Target is Increased When Migrating Using the Import Pipeline

Question

Why is it that, after migrating a list with versioning enabled using the Import Pipeline, there are more items on the target than on the source?

Increased Items on Target

Answer

If you are migrating a batch that includes a list with a base type of CustomList (such as Announcements), versioning is enabled, and Content Matrix has had to resubmit the batch that includes the list, duplicate items may be migrated to the target.  By default, these types of lists are excluded from resubmissions, but can be included via the environmentsettings.xml key RetryBatchForCustomListWithVersions.

NOTE:  If custom lists are excluded from batch resubmissions and all items are not successfully migrated, you can migrate any outstanding items using incremental migration.

Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline

Question

Why is it that, after a migration using the Import Pipeline, some lists with versioning enabled do not appear on the target?

Answer

By default, lists with a base type of CustomList (such as Announcements) are excluded when Content Matrix must resubmit a batch that initially failed to migrate in its entirety (because if they are included, duplicate items may be migrated to the target).   These types of lists can be included via the environmentsettings.xml key RetryBatchForCustomListWithVersions)

NOTE:  If custom lists are excluded from batch resubmissions and all items are not successfully migrated, you can migrate any outstanding items using incremental migration.

Supported Nintex Actions for SPO Migration

Question

What are the supported Nintex actions that are available when migrating from SharePoint on premises to SharePoint Online?

Answer

The following table lists the supported Nintex actions that are available when migrating from SharePoint on premises to SharePoint Online.

NOTE: The following actions are supported, but not all their parameters will necessarily have a SharePoint Online equivalent. Make sure to review migrated Nintex workflows to ensure that they migrated as expected. Also ensure that actions requiring user interaction (such as Assign Flexi Task, Send Notification, etc.) have user mappings properly configured during migration.  

On-Premises Actions

Online Actions

Assign Flexi Task

Start a task process

Build String

Build String

Calculate Date

Add Time to Date

Change State

Set Next State

Check Out Item

Check Out Item

Convert Value

Convert Value

Create Item

Create List Item

Delete Item

Delete Item

Discard Check Out

Discard Check Out Item

End Workflow

Terminate Current Workflow

Filter

Filter

Log in History List

Log to History List

Loop

Loop with Condition

Math Operation

Do Calculation

Pause for...

Pause for Duration

Pause Until

Pause until Date

Query list

Query list

Regular Expression

Regular Expression

Run If

Run If

Run Parallel Actions

Parallel Block

Send Notification

Send an Email

Set a Condition

Conditional Branch

Set Field Value

Set Field in Current Item

Set Variable

Set Workflow Variable

Set Workflow Status

Set Workflow Status

State Machine

State Machine

Switch

Switch

Update Item

Update List Item

Wait for item update

Wait for Field Change in Current Item

Refer to Quest® Essentials for Office 365 documentation for an idea of the requirements and caveats involved in the migration to SPO.

NOTE: If the workflow contains an action that is not supported, this unsupported action will be created as a comment in the migrated workflow. The comment will contain the name of this unsupported action.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione