Error after migrating for one of the page

sns 9,246 Reputation points
2021-04-16T12:10:20.233+00:00

We used DB method to migrate , but it seems one of the page showing below error, we have migrated from 2010 to 13 and to 16
Please see the difference when browsing same page from 2010 and 2016:
88568-2010.jpg

88627-2016.jpg

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
3,081 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Echo Du_MSFT 17,316 Reputation points
    2021-04-19T03:27:38.977+00:00

    Hi @sns ,

    If all of your KWizCom products are not on the same release version, it is possible for SharePoint to not be able to find a required version of Telerik.Web.UI.dll.

    After you deploy the latest version, please check the "OWSTIMER.EXE.CONFIG" file on the server where the SharePoint Timer runs.

    1.Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\BIN folder

    2.Find and open OWSTIMER.EXE.CONFIG file
    Note:Please check that you have bindingRedirect for KWizCom Foundation. Make sure that it redirect always to version 13.3.0.0.

    <runtime>  
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">  
    <dependentAssembly>  
    <assemblyIdentity name="KWizCom.SharePoint.WikiPlus.Telerik.Web.UI" publicKeyToken="30fb4ddbec95ff8f" culture="neutral" />  
    <bindingRedirect oldVersion="1.0.0.0-20.0.0.00" newVersion="13.3.0.0" />  
    </dependentAssembly>  
    <dependentAssembly>  
    <assemblyIdentity name="KWizCom.SharePoint.WikiPlus.Telerik.Web.UI" publicKeyToken="30fb4ddbec95ff8f" culture="neutral" />  
    <bindingRedirect oldVersion="1.0.0.0-20.0.0.00" newVersion="13.3.0.0" />  
    </dependentAssembly>  
    </assemblyBinding>  
    </runtime>  
    

    3.Please make sure that you restart SharePoint Timer (OWSTimer) and restart IIS after you deploy the latest version or make any changes in OWSTIMER.EXE.CONFIG file.

    Here is a similar blog for your reference.

    Thanks,
    Echo Du

    =======================
    Updated Answer ======================

    Hi @sns ,

    1)Remove Site collection using PowerShell:

    • Remove-SPSite cmdlet with -GradualDelete switch

    The -GradualDelete parameter instructs to delete the site collection gradually, instead of consuming all system resources to delete the site collection instantly in a single stretch. This reduces the load on the system when deleting large site collections.

    Remove-SPSite -Identity "Site-collection-URL" -GradualDelete  
    

    - Force delete SharePoint site collection with PowerShell

    If you face any difficulty in deleting SharePoint site collection either from Central Admin or with PowerShell, you can force delete site collection from the content database as:

    #Get the site collection to delete  
    $Site = Get-SPSite http://site-collection-url  
    
    #Get the content database of the site collection  
    $SiteContentDB = $site.ContentDatabase   
    
    #Force delete site collection  
    $SiteContentDB.ForceDeleteSite($Site.Id, $false, $false)  
    

    2)In SharePoint 2016, only one attachment can be uploaded at a time, but you can add attachments multiple times.

    90995-attachments.gif

    3)Personal list view can be retained after migration.

    Thanks,
    Echo Du

    =======================

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    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.