Invalid SharePoint Online list 'CPN' (ErrorCode: 0x0201000D) OriginalMessage: Web Issue when doing SP Query The operation has timed out

Edward Chong 20 Reputation points
2023-08-11T21:45:13.1333333+00:00

Attempting to migrate a number of SharePoint 2013 sites to SharePoint Online. A few have gone through without issue, however on this one site, I keep getting the error:

Invalid SharePoint Online list 'CPN' (ErrorCode: 0x0201000D) OriginalMessage: Web Issue when doing SP Query The operation has timed out

When attempting multiple times, the reported list in the error (CPN) changes each time, so it doesn't look like it's an issue with a specific list. Seems more like a timeout issue.

I've got admin access to both SP2013 and SPO site.

SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
11,230 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Yanli Jiang - MSFT 31,561 Reputation points Microsoft External Staff
    2023-08-14T07:05:13.6466667+00:00

    Hi @Edward Chong ,

    According to your description, the cause of the problem cannot be confirmed yet. But please don't worry, let's check the following aspects to find out the cause of the problem:

    1. Check the list mentioned in the error message to make sure it is not corrupted or has any issues that could cause the migration to fail. You can do this by going to the list in SharePoint 2013 and checking for any errors or issues.
    2. Check the SharePoint Online site to make sure it is functioning properly and there are no issues with the site that could cause the migration to fail. You can do this by visiting the site in SharePoint Online and checking for any errors or issues. For more details, please see:https://learn.microsoft.com/en-us/sharepointmigration/troubleshooting-common-spmt-issues#spmt-error-codes
    3. Try migrating the site again after a few hours or on a different day. Migration may fail due to high traffic or server load, waiting a while may help resolve the issue.

    If the above checks still have no clue to the problem, you can consider increasing the timeout value for the migration process. This can be done by modifying the web.config file for the SharePoint 2013 site. Here are the steps to do this:

    1. Open the web.config file for the SharePoint 2013 site in a text editor such as Notepad.
    2. Locate the <system.web> section of the web.config file.
    3. Add the following line to the <system. web> section:

    <httpRuntime executionTimeout="3600" />

    This will increase the timeout value to 3600 seconds (1 hour). You can adjust the value as needed, depending on the size of your migration and the amount of time it is taking.

    1. Save the web.config file and close the text editor.

    Note that modifying the web.config file can be risky, so it's a good idea to make a backup of the file before making any changes.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Yanli Jiang - MSFT 31,561 Reputation points Microsoft External Staff
    2023-08-16T06:22:34.24+00:00

    Hi @Edwardcc ,

    According to my research, it should be a random event.

    The content being migrated was stored in Azure File Storage with local caching. The Migration Tool was using the local network drive mapping (to the cache) and often the content being accessed needed to be retrieved by the cache from Azure.

    The issue is sometimes the file isn’t in the cache and the migration tool doesn’t wait for it to download. The result is the file is zero bytes long and as not file metadata to read.

    One solution is to connect directly to Azure File Storage rather than using the cache by mapping a drive.

    For more information, please refer to:

    https://steveknutson.blog/2019/08/02/azure-storage-and-sharepoint-migration-tool-errors/

    And I also found a related post for your reference:

    https://sharepains.com/2021/08/27/migrating-file-shares-with-sharepoint-migration-manager/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from all above links.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.