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 2016: High Availability Farm Topology

MinRole concept was introduced in SharePoint 2016 and it aims to simplify the process of designing the farms. However, I still find ambiguous information about the count of servers in SharePoint 2016 farm. Let's ask ourselves the question - What is the minimum number of servers which allow High Availability MinRole farm? According to technet   we have the following options: Small High Availability (HA) MinRole farm 4 Four servers with two shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 6 Six servers with both dedicated and shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application servers ·    ...
Post a Comment
Read more

Load dynamically JavaScript file inside Custom Action

This starts to be very common scenario in the SharePoint online projects: You want to have custom actions (“My Action”) that execute custom logic. The main challenge is how to load the JavaScript file with this custom logic (/sites/demo/SiteAssets/Actions/dts.demo.script.js) only when the custom action needs it. One approach described in many posts is to use a Script link.  Here is a working example: function RegisterScriptLink() { var scriptBlock = 'var headID = document.getElementsByTagName("head")[0];var newScript = document.createElement("script");newScript.type = "text/javascript";newScript.src = "' scriptBlock += '/sites/demos/SiteAssets/Actions/dts.demo.script.js' + '?ver=' + ((new Date()) * 1); scriptBlock += '";headID.appendChild(newScript);'; var context = new SP.ClientContext.get_current; this.site = context.get_web(); var collU...
Post a Comment
Read more