Content Matrix 9.11 - SharePoint Edition

How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account?

Question

I am running out of storage space in my Azure private storage account. How do I remove containers and queues created by Content Matrix to free up space for more migration actions?

Answer

Naming Conventions

Beginning in version 9.3, Content Matrix uses naming conventions that allow you to easily identify containers and queues created by Content Matrix during migration using the Import Pipeline.  

To remove items from your Azure blob storage account using Azure PowerShell:

1.Ensure there are no active migration actions running that use the Azure storage where the items are stored.

2.Open Azure PowerShell.

3.Connect to Azure using the New-AzStorageContext cmdlet. Your account name and account key are required parameters. Note that these are different from your Client ID and Application Secret.        $context = New-AzStorageContext -StorageAccountName $accountName -StorageAccountKey $accountKey

4.Use the information in the following table to determine the appropriate command to use.

Error: 'The object is associated with property AssociatedMemberGroup.'

Question

When attempting to copy an object to a SharePoint Online site or OneDrive, why do I receive the following error?

Object reference not set to an instance of an object on server. The object is associated with property AssociatedMemberGroup.

Answer

This error may occur when one or more of the default SharePoint groups (Owners, Members, and/or Visitors) are not present on the target.

NOTE: For OneDrives, none of these groups are present by default.

Create the missing default group(s) on the target.  Refer to the applicable Content Matrix Knowledge Base article for more information.

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?

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?

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.