Skip to main content

Missing documents after migrating from SharePoint 2010 to SharePoint 2013

I had a task to migrate the content database of a web application in SharePoint 2010 to SharePoint 2013.
I performed the database-attach method (the only possible with SharePoint 2013 migration) and everything seemed to be working.

The problem came when I navigated in the document libraries. There were a lot of missing files.

At first, it looked scary but the reason was logical:
    - I migrate the web application to a new farm with different Active Directory
    - The missing files didn’t have published version so they were not missing but hidden
    - Even I was logged with the System Account the security trimming hide these files

The way to make the files visible is to publish them.
Just navigate to  Library Settings -> Manage files which have no checked in version .
From here you can take the control over the documents and to publish them:

Looks simple but it took me time to identified the issue.

Comments

  1. Unknown26 November 2016 at 06:58

    Hi guys,
    Thank you so much for this wonderful article really!
    If someone want to know more about the Tzunami Migration Masters I think this is the right place for you!

    ReplyDelete

Post a Comment

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration       < wssawc : ClientPeoplePicker          Required ="true"          ValidationEnabled ="true"          ID ="peoplePicker"          runat ="server"   ...
14 comments
Read more

SharePoint and List Joins with CAML

This came to me as an issue when I started migrating one project from SharePoint 2010 to SharePoint 2013. The code uses LINQ to SharePoint and it was not written in a clever way. We decide to use CAML queries and optimize the code. The scenario: Create gridview that gathers information from three(or more) lists. The problem: How to create the CAML query joins and projected fields correctly. Explanation : Option 1: Get generated CAML query from LINQ to SharePoint code This doesn’t work. I wrote the LINQ to SharePoint code connected the three lists. When I executed the code the following error was thrown – “ The query uses unsupported elements, such as references to more than one list, or the projection of a complete entity by using EntityRef/EntitySet. ” Here is some explanation about it and why this can’t be used. Option 2: Write the query yourself I found this article in MSDN . Read it ! The second part in it is exactly my scenario. But it takes me a lot of time to un...
Post a Comment
Read more

SharePoint User Group Bulgaria

In the past year I invested my free time in activities related to the SharePoint User Group Bulgaria. This is the reason why I stopped writing in this blog. Please start following this new place  www.sugbg.com . I promise you that you will find there truly valuable content.
Post a Comment
Read more