Tag Archives: great sharepoint hosting


SharePoint 2013 Hosting :: How to Migrate DocRead from SharePoint 2010 to SharePoint 2013

How to migrate DocRead from SharePoint 2010 to SharePoint 2013

If you are considering migrating your SharePoint Farm to SharePoint 2013 (from SharePoint 2010) then please read through this article for steps on how to achieve this. Before proceeding, it’s important that you read ‘migrating between editions’ to understand how this effects your licensing.

Preparing your SharePoint 2013 Farm :

It is important to know that we only support migrations that have followed Microsoft’s recommended approach.

Note: We don’t support migrations that have been completed using custom code, or by using 3rd party migration tools such as those offered by AvePoint and Metalogix.

If you do wish to use one of these approaches then it may still be possible to migrate your DocRead data but it would require one of our DocRead developers to work with you as a chargeable piece of work.

Before you start the migration :

Before you start the migration you will need to download the latest version of DocRead for both 2010 and 2013. It’s very important that you are migrating from the one version of DocRead to another with the same build number. (e.g “v2.5″). If you aren’t running the latest version of DocRead on SharePoint 2010 you will need to carry out an upgrade which is detailed in our Installation Guide. Once you have completed the upgrade – it’s important to test DocRead to ensure that it is still fully operational and working as expected on SharePoint 2010.

Migration Steps (Central Admin) :

  • Complete the build and testing of your new SharePoint 2013 Farm.
  • Install but do not configure the latest version of DocRead for SharePoint 2013 onto your new Farm. (you will also need a license key by this stage).
  • Install but do not configure the latest version of the DocRead Scheduler onto your new Farm.
  • Attach and upgrade all of the content databases that DocRead was used on previously (please refer to the Technet guide).
  • If you are using SharePoint Global Audiences with DocRead it’s also necessary migrate your User Profile Service App and Metadata Service App which is detailed here.
  • Once this is complete, please test that your Farm is operational and specifically ensure that the Site Collections, Webs, Libraries / Lists, Groups, Audiences and Documents now exist with the same content as they had for SharePoint 2010.

Do a full back-up your SharePoint 2013 Farm.

  • Back-up your 2010 DocRead database and restore it to the SQL Server that you will be using for production and make a note of the Database name and Server Name.
  • Navigate to Central Admin > Collaboris Settings > Database Settings and enter the ‘SQL Server’ and ‘Database Name’ that you noted in the step above. Click ‘Ok’
  • Navigate to Central Admin > Collaboris Settings > Licensing  and enter your license key and click ‘Add’. Click ‘Ok’
  • Navigate to Central Admin > Collaboris Settings > Global Settings and add all of the Web Applications that contain sites where DocRead is activate. (Please note, even if they appear to look the same, it’s important to remove all and the re-add them as the internal ID’s will differ). Click ‘Ok’.

Disable the following DocRead timer jobs by going to Central Admin > Monitoring > Review Job Definitions :

  • DocRead audiences synchronisation job
  • DocRead readership processing job
  • DocRead SharePoint synchronisation job
  • DocRead Worker job
  • DocSurvey Stats Job (optional)
  • Migration Steps (Site Collection)
  • That’s all you need to do in Central Admin for now. The next phase is deactivate and uninstall the old 2010 Features and activate the new 2013 Features.
  • You can download the ‘upgrade Powershell script from here.
  • Once downloaded, open Powershell script with Notepad and edit the Datasource, Database (DocRead database) and user credential (if required).

Save the updates

  • Execute the Powershell script file (click right mouse button and select ‘Run with Powershell’.
  • IMPORTANT: The script only reactivates DocRead basic features. If any additional features were activated before you should reactivate them manually.
  • Post Migration Steps (Central Admin) :
  • Perform an IISReset on all of your machines in the production Farm.
  • Restart the SharePoint Timer job on all machines in the production Farm (see step 12 above for a list).
  • Perform a “Process Reading Tasks” in each DocRead enabled web and ensure that all the tasks are a present as before.
  • Configure the DocRead Scheduler as specified in the Installation Guide.
  • Scheduler a regular backup of the DocRead database.

SharePoint 2013 Hosting with ASPHostPortal :: Configures the Application Server and Web Server

The pre-requisites installation in one of my recent SharePoint 2013 farm installations was failing at the step where it configures the Application Server and Web Server role for the Server:



Further, the error logs had the following entry:

  • Request for install time of Application Server Role, Web Server (IIS) Role
  • Install process returned (0)
  • [In HRESULT format] (0)
  • “C:\Windows\system32\cscript.exe” “C:\Windows\system32\iisext.vbs” /enext “ASP.NET v4.5.30319″
  • Request for install time of Application Server Role, Web Server (IIS) Role – Install process returned (1)
  • [In HRESULT format] (-2147024895)
  • Error when enabling ASP.NET v4.5.30319 – Last return code

Since I did not find much community guidance around this, I thought I’ll do some research myself and post the solution for other’s benefit as well. A little bit of digging around revealed that the IISExt.vbs script file was indeed missing from the C:\Windows\System32 folder. Further research revealed that the script is part of the IIS 8.0 scripting tools. The solution therefore is as simple as enabling the IIS 8.0 Scripting Tools through the Server Roles and Features Wizard. The path to the IIS 8.0 Scripting Tools is shown in the following screen capture:


That’s it. Your pre-requisites installation should proceed as intended after you install these tools… Good Luck with your install! :D

SharePoint 2013 Hosting with ASPHostPortal :: Scenario pages for SharePoint 2013

SharePoint 2013 has many great ways to help you get things done. We want to highlight a few of these, so we have created scenario pages that explain a specific scenario and provide content to help you understand, implement, and use it easily.

Scenario pages allow you to view key resources based on selected stages of evaluation or adoption. These stages are represented by colored tiles. Click a single tile for a specific stage or Ctrl-click multiple tiles for multiple stages. As you click the tiles, the scenario page lists the resources for each selected stage.

Content and resources are drawn from many Microsoft Web properties: IT content from TechNet, developer content from MSDN, and Information Worker content from Office.com are all integrated into the scenario page experience. All of the resources you need are available in one place, whether you want to understand:

  • Which features must be configured to support the scenario and how to manage them
  • What namespaces and methods to use to develop customizations for the scenario (MSDN content) Or how to accomplish a specific task in the scenario (Office content)

The following scenario pages are now available:

  • eDiscovery in SharePoint Server 2013 and Exchange Server 2013 . eDiscovery allows you to place electronic holds on documents and email for a legal case or audit. eDiscovery is a great example of a solution that benefits from a scenario page because it provides links to key resources published for SharePoint 2013, Exchange Server 2013, and Lync Server 2013.
  • Personal sites (My Sites) in SharePoint Server 2013 . My Sites technology provides profile data, activity feeds, tagging capabilities, and search results for each SharePoint user in your organization.

When you deploy My Sites, each user gets a starting place in SharePoint that brings together the sites, documents, and other information that they care about and helps them share what they know.