Upgrading SharePoint from 2010 to 2013 with Farm Solution

Hi All,
I am working on multiple SharePoint versions.
I have to migrate the SharePoint 2010 to 2013. This is having multiple procedures but what about the Farm solution? I found the answer on
this link.
But I did not found any details about the impact on the workflows. I am using Visual Studio 2010 Workflows for the approval process.
should I need to restart the workflows again? All tasks will be deleted. I don't want lost my tasks and history details.
Waiting for your valuable reply.
Thanks.
- Khan Abubakar Disclaimer: The opinions expressed herein are my own personal opinions and do not represent any others view in anyway.

Hi,
According to your post, my understanding is that you wanted to know the impact on workflow when migrating the SharePoint 2010 to 2013.
For SharePoint 2010 custom activities to work in SharePoint 2013, the “authorizedType” node needs to be defined in a new sub-section “targetFx” under the “authorizedTypes” section. If this is not changed, an error will be encountered: ‘The type or namespace
name '?' could not be found (are you missing a using directive or an assembly reference.'
You can refer to the following article which about how the authroizedTypes were setup in SharePoint 2010 vs how they should be setup in 2013.
http://blogs.technet.com/b/sharepointdevelopersupport/archive/2013/05/09/migrating-sharepoint-2010-workflow-custom-activity-to-sharepoint-2013.aspx
There are three ways in which you can upgrade and version a workflow.
Option 1: Move all content to new site and re-execute incomplete workflows.
Option 2: Code workflow so it can continue or restart all in-process workflows.
Option 3: Run old workflows to completion with old assembly and new workflows with new assembly.
More reference:
http://kmsnet.blogspot.in/2013/07/upgrade-custom-workflow-in-sharepoint.html
http://habaneroconsulting.com/Insights/Approach-to-upgrading-custom-SharePoint-workflows.aspx#.UwK-s_mSx8A
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Jason Guo
TechNet Community Support

Similar Messages

Upgrade Office from 2010 to 2013 script

Hi Everyone,
I am planning upgrade of 500+ clients to the latest version of Office.
Currently everyone has Office 2010 32bit installed which I would like to uninstall prior to upgrading. What is the easiest way of doing this? Startup script? GPO?
Thanks,
Mladen

Hi Mladen,
To do an Uninstall upgrade, the idea is uninstall Office 2010 via command line (/uninstall [ProductID]), and then deploy Office 2013 by using Group Policy computer startup scripts.
For command line option for Office 2010, please refer to this article:
http://technet.microsoft.com/en-us/library/cc178956(v=office.14).aspx
Deploy Office 2013 by using Group Policy computer startup scripts:
http://technet.microsoft.com/en-us/library/ff602181(v=office.15).aspx#Script
Here is a great example of how to perform an uninstall-upgrade, although it's about upgrading to Office 2010, there should not be much difference:
http://blogs.technet.com/b/odsupport/archive/2011/04/06/how-to-perform-an-uninstall-upgrade-to-office-2010.aspx
Hope this helps.
Thanks,
Ethan Hua CHN
TechNet Community Support

Upgrade EDGE from 2010 to 2013

Hey guys,
does anoyone have a suitable update process for upgrading EDGE 2010 to EDGE 2013? I have two EGDE 2010 Servers in the DMZ. My thoughts are to install two new EDGE 2013 servers, then to use ExportEdgeConfig.ps1 on both 2010 Servers and to import settings
to the new servers. After that, I would create to new edge subcriptions. I already have inbound and send connector. So which command should I run?
New-EdgeSubscription -FileName C:\Edge.xml -Site "My-Site" -CreateInternetSendConnector $false - CreateInboundSendConnector $false ?
I hardly find any information about the upgrade process.
Woul be nice, if anyone has experiences in that case.
Thanks

You can simply:
Take care of the name resolution. If you are planning to use DNSBL on the Exchange 2013 servers, be careful with the DNS servers that you specify (ex. Google's DNS servers 8.8.8.8 and 4.4.4.4 always provide negative response, and Barracuda DNSBL will not
work with the internal DNS servers unless they are registered).
Create new Edge subscriptions on the Exchange 2013 EDGE servers (with New-EdgeSubscription ...)
Copy and import the generated XML files (on the internal MBX servers).
Double check and set if necessary the internal SMTP servers (Get-TransportConfig | select InternalSMTPServers).
Initiate a sync (Start-EdgeSynchronization -ForceFullSync).
(Optional) Configure IP Block List providers.
Redirect SMTP traffic through the Exchange 2013 EDGE servers.
Remove the EDGE subscriptions for the Exchange 2010 EDGE servers (Remove-EdgeSubscription -Identity ...).
Step by Step Screencasts and Video Tutorials

SharePoint 2013 Upgraded Sites from 2010 Missing Title on Home Page

Hi All,
I have upgraded site collection from 2010 to 2013 but I can't see site tiles on site Home page. We are using our template to create default web part page. I can see titles when I do Site Actions->Site settings->Look and Feel->Title but
not on default page of site.
Need help to solve the issue. Thanks in advance.
Jayprakash Dhore

Hi,
The following steps for your reference:
1.Open the problem site in SharePoint Designer 2013 (SPD)
2.Choose All Files option on the left hand quick launch
3.Click on default.aspx
4.On the Home tab, switch to Advanced Mode.
5.Search for "PlaceHolderPageImage" … it’s near the top
6.Paste the following on the next line (or after the closing </asp:Content> tag)
<asp:Content ContentPlaceHolderId="PlaceHolderPageTitleInTitleArea" runat="server">
<label class="">
<SharePoint:ProjectProperty Property="Title" runat="server"/></label>
</asp:Content>
7. Save and refresh your page
Or check the blog below:
SharePoint 2013 Upgraded Sites Missing Title on Home Page
http://sharepointcherie.blogspot.com/2013/10/sharepoint-2013-upgraded-sites-missing.html
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

File Attachments in Conferences: Permissions don't follow when upgrading from 2010 to 2013

Hello all,
   Here at Unisys we are upgrading our Lync Enterprise Infrastructure from 2010 to 2013. We have found that when we do this, any conference that has an attached file the permissions of the file do not follow.  The
options for a file permissions are Organizer, Presenter, and Everyone. If in 2010 it is Everyone, after the upgrade, it is always reset to Organizer. Not a big deal, but every user will need to be trained to
go back in and reset the permissions on the file, else, they will not be visible by the other conference attendees.
   We have a case open with Microsoft on this, and I've scoured the web trying to find others that have seen this. Any thoughts?
   Thanks, and it's very cold in Texas today :-)
Jason Weaver
Jason J. Weaver

Thanks for the update Eason.
Here are a few notes from the Msoft case that we are not 100% in agreement with:
This is not only in the case of migrating user
from 2010 to 2013. This happens even when the user is not migrated to 2013.
You can reproduce the behavior by joining the same meeting in 2010. This is a
default behavior of meeting configuration and this has been set this way for
security reasons so that if organizer is not present, nobody can view the
attachments without the permission of organizer.
However, when we test in our environment, we can add the attachment and like you say, it is set to EVERYONE. When we exit the meeting and rejoin with OR WITHOUT the organizer present, the attachment is still there, Everyone can see it.
However, when we migrate users from 2010 to 2013, the attachments are set to organizer only.
Go figure. Not the end of the world, we just need to make sure we are able to explain to our users that the attachments are still there and that the organizer of each meeting will need to go back in and re-permission each conference.
Take care, see you all in Vegas-
Jason J. Weaver

User metadata values is showing as plain text in Mysites after upgrading from 2010 to 2013

We have upgraded our Mysite from 2010 to 2013, after upgrading User metadata values is showing as plain text where
as in 2010 it has shown as hyperlinks.
In Mysite 2010 by clicking on user metadata for favorite sports, Favorite Movies etc...it will give the results from search containing same value for other user
by going to search results page. After upgrading it to 2013 (with 2010 UI) and running full crawls, I am able to search by clicking on any user property.
After upgrading look and feel to 2013 version these fields showing as plain text. Can anyone suggest how can we get hyperlinks and how can we make user
metadata searchable directly by clicking on Property value from Mysite. Below screen print explain you the difference clearly.
Santosh

Hi Inderjeet, thanks for the update.
I am running with SP1 + july2014 CU.
Search is working fine, I am able to get search results from search page, here the problem is I cannot go to search results by directly clicking on a property.
In SP 2010, If I click on favourite sports team, (Chelsea football) it will open search results page with all users who have given this team name.
Where as in SP 2013, this data is appearing as plain text in mysites(Please note before UI upgrade, I am able to search as in SP 2010). You can notice the difference in my above screenshot.
Is this default behaviour in SP 2013? Has anything changed or am I missing something.
Santosh

Custom Auto Attendant Prompts through TUI not working for users who migrated from 2010 to 2013

In Exchange 2010, we started using unified messaging and set up Auto Attendants. We setup a admin role/RBAC for people of a security group to be able to update the message on the auto attendants. They have the UMPrompts assigned role. All of this is working
great in 2010. We have now migrated to 2013, and the users who were migrated from 2010 to 2013 can no longer update the messages through TUI. Newly created 2013 users can and are assigned the EXASCT same permission as the users who have been doing this for
well over a year on 2010. When they call the AA and press #,* they are asked to provide their extension, after doing so the system tells them that extension is not correct. and asks for the extension again. Newly created users with the same permissions
get prompted for their PIN and can log in and change the message just fine.
Confirmed Bug? anybody else having this issue?
What would be different for this process between a user who was migrated from a previous version like 2010 compared to a newer user who has only ever existed on 2013?

What if the migrated 2010 users are in the same DB as the system mailbox? I had a similar issue during a migration; http://www.skypeadmin.com/2014/11/10/known-issue-um-automated-attendant-tui-editing-broken-migration/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Getting error while uploading multiple files in sharepoint hosted app in 2013 with REST API

Hi All,
In one of my tasks, I was struck with one issue, that is "While uploading multiple files into custom list with REST API".
Iam trying to upload multiple files in library with REST calls for an APP development, my issue is if i wants to upload 4 image at once its storing only
3 image file and further giving "Conflict" error". Below is the attached screenshot of exact error.
Error within screenshot are : status Code : 409
status Text :conflict
For this operation i am uploading different files as an attachment to an list item, below is the code used for uploading multiple files.
my code is
function PerformUpload(listName, fileName, listItem, fileData)
var urlOfAttachment="";
// var itemId = listItem.get_id();
urlOfAttachment = appWebUrl + "/_api/web/lists/GetByTitle('" + listName + "')/items(" + listItem + ")/AttachmentFiles/add(FileName='" + fileName + "')"
// use the request executor (cross domain library) to perform the upload
var reqExecutor = new SP.RequestExecutor(appWebUrl);
reqExecutor.executeAsync({
url: urlOfAttachment,
method: "POST",
headers: {
"Accept": "application/json; odata=verbose",
"X-RequestDigest": digest
contentType: "application/json;odata=verbose",
binaryStringRequestBody: true,
body: fileData,
success: function (x, y, z) {
alert("Success!");
error: function (x, y, z) {
alert(z);

Hi,
THis is common issue if your file size exceeds
upload a document of size more than 1mb. worksss well for kb files.
https://social.technet.microsoft.com/Forums/office/en-US/b888ac78-eb4e-4653-b69d-1917c84cc777/getting-error-while-uploading-multiple-files-in-sharepoint-hosted-app-in-2013-with-rest-api?forum=sharepointdevelopment
or try the below method
https://social.technet.microsoft.com/Forums/office/en-US/40b0cb04-1fbb-4639-96f3-a95fe3bdbd78/upload-files-using-rest-api-in-sharepoint-2013?forum=sharepointdevelopment
Please remember to click 'Mark as Answer' on the answer if it helps you

Exchange server name not changing in mail profile after migration from 2010 to 2013

Following a migration from 2010 to 2013 we are finding that for a number of users the old exchange server address stays in the mail profile (control panel -> mail -> e-mail accounts) which causes Outlook not to load.
We are able to go into control panel -> mail -> e-mail accounts and change this manually to the new exchange 2013 server address but we have quite a number of users and don't really want to do it manually.
Shouldn't it be updating automatically and if so why is it?

Hi,
Yes, it should be changed by autodiscover. Does this issue occur to all the migrated users?
I have seen this kind of issues before when migrating from Exchange 2003/2007 to Exchange 2010. The most efficient way is to rebuild the Outlook profile.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Error while upgrading web application with SSRS from 2010 to 2013

I am trying to upgrade a site collection which has SSRS reports in it. When I run Test-SPContentDatabase
with database of SP2010 and the new web application of 2013 I obtain the errors:
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
erWebPart] from assembly
[Microsoft.ReportingServices.SharePoint.UI.WebParts,
Version=10.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91]) is referenced [6] times in
the database [Areas_10100], but is not installed on the
current farm. Please install any feature/solution which
contains this web part.
Remedy : One or more web parts are referenced in the database
[Areas_10100], but are not installed on the current farm.
Please install any feature or solution which contains these
web parts.
Locations :
Category : MissingAssembly
Error : True
UpgradeBlocking : False
Message : Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=10.50.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [Areas_10100], but is not installed on the current
farm. Please install any feature/solution which contains
this assembly.
Remedy : One or more assemblies are referenced in the database
[Areas_10100], but are not installed on the current farm.
Please install any feature or solution which contains these
assemblies.
Locations :
SSRS are configured in both farms (2010 and 2013). In 2010 farm is SSRS 2008 R2. In the environment of 2013 farm is SSRS 2012.
Any idea?

Similar Thread:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/68cc3179-8ed8-4435-b645-11f79f8bdc1f/upgrade-test-testspcontentdatabase-reporting-services-error?forum=sharepointadmin
This post is my own opinion and does not necessarily reflect the opinion or view of Slalom.

Upgrade 2010 to 2013 with SQL Reporting Services

I'm getting ready to upgrade to 2013.
When I run the Test-SPContentDatabase I get:
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
erWebPart] from assembly
[Microsoft.ReportingServices.SharePoint.UI.WebParts,
Version=10.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91]) is referenced [24] times
in the database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this web part.
Remedy : One or more web parts are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
web parts.
Locations :
Category : MissingAssembly
Error : True
UpgradeBlocking : False
Message : Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=10.50.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this assembly.
Remedy : One or more assemblies are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
assemblies.
Locations :
Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [is.photomask.com] web application is configured with
claims authentication mode however the content database you
are trying to attach is intended to be used against a
windows classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of
target web application and the source web application.
Ensure that the authentication mode setting in upgraded web
application is the same as what you had in previous
SharePoint 2010 web application. Refer to the link
"http://go.microsoft.com/fwlink/?LinkId=236865" for more
information.
Locations :
The first two have to do with reporting services. I'm trying to workout how to go about getting these errors to go away. I don't want to remove SQL reporting or migrate a broken site and fix it later. FYI it does migrate but reporting services
is of course broken.
So what I was wanting to do was to upgrade SQL Reporting Services for SharePoint 2010 from 2008 SQL to 2014 SQL first. This would be in the hopes that it would make the migration to SharePoint 2013 work as the assemblies would change to the proper
version.
Can anyone elaborate on my upgrade path?
I'm still looking up the "Claims Based" authentication thing. I've found an article on how to migrate it so not a big deal. I do wonder however if this is tied to the issue I saw with default.aspx and home.aspx being denied to all users
after I did migrate a content db.
David Jenkins

Hi David,
The following sections describe the basic steps needed to upgrade or migrate from 2008 versions of Reporting Services SharePoint mode to 2014 version.
SQL Server 2008 R2 to SQL Server 2014
Starting environment: SQL Server 2008 R2, SharePoint 2010.
Ending environment: SQL Server 2014, SharePoint 2010.
In-place upgrade is supported and there is no down time for your SharePoint environment.
Install the SQL Server 2014 version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server 2014 installation wizard or by downloading the add-in.
Run SQL Server 2014 installation to upgrade SharePoint mode for each “report server”. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.
If you also want the ending environment to run SharePoint 2013, you need to complete a database-attach upgrade of the SharePoint 2010 to SharePoint 2013.
For more scenarios information, please refer to:
http://msdn.microsoft.com/en-us/library/ms143747.aspx#bkmk_sharePoint_scenarios
Per the supported combinations of SharePoint and Reported Services Components, I’d recommend you firstly upgrade Reporting Services to 2014, then upgrade SharePoint to 2013.
For more information:
http://msdn.microsoft.com/en-us/library/gg492257.aspx
The link below is the reference for migrating a Reporting Services:
http://msdn.microsoft.com/en-us/library/hh759331.aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Excel file error after upgrade from 2010 to 2013

Hi there,
I did the upgrade from 2010 (Enterprise) to 2013. The excel files are not opening giving error.
ULS Log: "Unexpected error when trying to access service settings in the configuration database. Make sure the proxy for this service application is a member of the default proxy group for the active web application. Error = ExcelServerWebServiceApplication.Local:
Could not get the web application associated with this context. This indicates that the Excel Server service is not properly registered or provisioned.."
Question : Do I need to create New Excel Service Application separately on SharePoint 2013 Server?
I followed this link for upgrade
http://technet.microsoft.com/en-us/library/jj839719.aspx but it doesn't say anything for Excel SA.
Note: I have plan to configure separate Office APP Server to give user access the documents on iPad/iPhone. Should I need to do any configuration related to this error on Office App Server?
Please advice.
Thanks,
Khushi

Hi Khushi ,
Yes, you need to create New Excel Service Application separately on SharePoint 2013 Server. Due to only the following service applications have databases that can be upgraded when you upgrade from SharePoint
Server 2010 to SharePoint Server 2013:
Business Data Connectivity service application
Managed Metadata service application
PerformancePoint Services service application
Search service application
Secure Store Service application
User Profile service application
Attaching and upgrading these databases configures these service applications. Settings for other services will have to be reconfigured when you upgrade.
Reference:
Services upgrade overview for SharePoint Server 2013
For configuring Office Web Apps Server , you can refer to the blog:
http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
Best Regards,
Eric
Eric Tao
TechNet Community Support

Unable to Create Workflows with either SharePoint Designer 2010 or 2013 to our SharePoint Online Service

Hey there
I was wondering if anyone could shed some light on our current issue using SharePoint Online (hope this question is in the correct place)
We are using SharePoint Online and I believe we are using the SharePoint Plan 1 for EDU - which I believe is the A2 Free plan.
I have being trying to get my head around the new changes (as we currently run a standalone 2010 deployment) and decided to see what workflow options I had. I had read to use SharePoint Designer 2013 with the online service and after installation opened
the package, connected to the site and tried to create a simple email workflow. I first saw a loading screen stating
"The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is Microsoft.Activities, Version 1.0.0.0, Culture=neutral, PublicKeyToken=731bf3856ad364e35.
Contact your server administrator for more information."
after this it tried loading some metadata and then I saw:
Server-side activities have been updated. You need to restart SharePoint Designer to use the updated version of activities.
I close SPD down and rebooted and then same happened again and continues too.
After research I applied a hotfix that was known to resolve the issue, but it still remains. I also tried running SPD in admin mode but the same still happens.
Lastly I tried selecting workflows 2010 from the drop down field when creating the workflow to see what happened. I go the same. I also keep getting the following as a pop from time to time.
The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
Contact your server administrator for more information.
I have also tried to do the same in SharePoint Designer 2010, but receive the same massages.
What should I be looking at or doing to help rectify this?
Regards
RDH

uninstalled Language Pack and it worked!
Uninstalling the Preview and installing SharePoint Designer 2013 resolved the error.
http://community.office365.com/en-us/f/154/t/74327.aspx
According to the link as linle provided, there are two deletions in local, please double check these two places:
1.Delete all folders in the following directory:
C:\Users\USER\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache\
2.Delete the files in all folders in this directory:
C:\Users\USER\AppData\Local\Microsoft\WebsiteCache\ (don’t delete the folders, just delete the contents of the folders)
Then, try to create a new workflow in SharePoint Designer 2013 to see if it works.
You can first keep the list for the current status, and save it as a template which will be used to create another list.
1.Login and locate the associated list on your SharePoint Online.
2.Click List Settings under List tab, and click Save list as template.
3.Type a File name, Template name, select Include Content, and click OK. Click OK.
4.Click Site Actions->More Options->List.
5.Locate and click the newly saved template, type a name, and click Create.
Then, create a workflow in your SharePoint Designer 2010 associated to the new list to see if it works.
Moreover, please check if there are any maintenances on your SharePoint Online which may cause the issue.
1.Login to Office 365 Portal (https://portal.microsoftonline.com/).
2.Click Service Health in the left pane of Admin page.
3.Check the status of SharePoint Online
If this helped you resolve your issue, please mark it Answered

Upgrade share point 2010 web application to share point 2013 with BI solutions.

HI
we have sharepoint portal web application ( publishing enabled , Annonymous access for internet users)
and BI dashboards also we published in this portal.
1 ) so for content db upgrade to 2013 we will follow db attach method, but what about BI pointers list,dashboards list
it also be upgrade with content database.
2) now the BI dashboards connected to SQL Serve Analysis server 2008 r2 datasources, so after upgrade ,
we need to be must upgrade these SSAS datasources to SSAS 2012 ?
adil

Given you aren't using PowerPivot for SharePoint, you can continue using SSAS 2008 R2 for your cubes and data connections. BI dashboards, Lists, and so forth are just SharePoint content, and they get upgraded when you migrate to 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Recovering the deleted files of One Note after MS office upgradation from 2010 to 2013

Hi Team,
After up gradation of my MS office 2010 to 2013, I could see that few of my files were not present in the one note 2013. Could you please let me know if the data would be archived somewhere in the machine.
Regards
Vijay

Hi Vijay,
Where are these missing notebooks stored? In local or in the cloud?
As far as I know, some notebooks may be closed after the gradation. We may try to reopen any of your previously used notebooks using following steps:
1. Click the File tab, and then click Open.
2. Under Recent Notebooks, click to open any of the notebooks that are listed.
3. Look through the sections and pages of your reopened notebooks, or perform another notebook search.
Hope this helps.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Upgrading SharePoint from 2010 to 2013 with Farm Solution

Similar Messages

Maybe you are looking for