Author Archives: Downey Neale


SharePoint 2013 Hosting :: Migrate to OneDrive on Office 365 from Google Drive

So you’ve finally decided to jump straight into the deep end and move over to OneDrive I’m sure you’ve had the idea in the back of your head for quite some time. Google Drive was fine for the time being but the OneDrive’s added functionalities probably ended up getting the best of you. Yet one question remains: how do I proceed? This article will walk you through this procedure:

  1. Set up your source folder.
  2. Connect to the destination
  3. Choose files you want to migrate
  4. Easily migrate your files to OneDrive
Even though we was primarily designed for SharePoint to SharePoint migrations, it also supports importing from network drives, file shares and file systems.

Where do you start your OneDrive Migration?

The first step is to have the source set up correctly. Most Google Drive users already have a ‘mapped Goggle folder’ on their PC. If it is not the case, here is how to set one up:

You can simply download it to your machine by clicking on Download Google Drive located in the settings menu or from the Install on your machine icon on the left, depending on the version of Google Drive you are using.

Once you have clicked on the download button, the installer will be downloaded to your machine. Once the process is completed, you can simply open it so the installation can begin.

After Google Drive has been installed, enter your credentials to synchronize it with your account.

At that point, the Drive is completely configured. In your case, you will be able to use it just as another folder in your C: Drive (or the selected drive during the installation)


Start your Migration to OneDrive with Sharegate

The Import is a breeze, and connect to the desired destination site. Then, select the destination library or the location where you want to copy the content.


Hand pick the content you want to migrate

Once the destination has been chosen, simply select the desired content to be imported while keeping the original authors and timestamps. Simply Awesome.


A migration so simple, a child could do it

As you can see, it is a very simple process. The great thing is that any end user can run this operation as long as he has full control over the destination library.

image_4Finally, do not worry about your PowerShell script. I will gladly review it before you start your migration. I hope this will help you on your journey to the cloud!


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 :: How to Use Microsoft SharePoint Workspace Mobile

ahp_freehostSHP(1)With SharePoint Workspace Mobile, you can open, edit, and save Microsoft Office documents that are on a SharePoint 2013 site or on SharePoint Online sites, which are available with Microsoft Office 365. Just go to the Office Hub to get started.


  • Unless your organization uses a Microsoft Forefront Unified Access Gateway (UAG) server, you can only access a SharePoint 2013 site if you’re in the office and connected to your organization’s Wi-Fi network. For more info, see Connect to a Wi-Fi network.
  • You can access documents that are on a SharePoint Online site at any time and from any location by using your phone’s cellular data connection or any Wi-Fi connection that lets you connect to the Internet.

To open a SharePoint site for the first time on your phone

  1. On Start, flick left to the App list, and then tap Office .
  2. Flick to Locations, and then tap SharePoint.

If you already signed in on your phone with an email account that you have as part of Microsoft Office 365 and your plan includes SharePoint Online, your SharePoint team site will already appear in Locations. Just tap the team site to open it.

  1. Next to https://, type the address for a SharePoint site, document library, list, or folder, and then tap Go .

If you have an Exchange email account set up on your phone, SharePoint will try to use that user name and password information to sign in to the SharePoint site. If you don’t have one set up on your phone, you’ll be prompted to enter your user name and password.

  1. If you’re prompted to sign in, do one of the following:
    • If the Microsoft Office 365 sign-in page appears, type your user ID in the corresponding box, type your password in the Password box, and then tap Sign in.
    • If the Site screen displays, tap the User name box, and type your user name. Type your password in the Password box, tap Domain, and then type the domain for your account. For example, if you log on as “domainName/user” at work, you’d type domainName. Tap Done.
  2. Tap More > Bookmark this link > OK in the Link added screen to bookmark the link for later.


To open another SharePoint site or location later on, flick to Locations in the Office Hub, and then tap New . On the Open URL screen, type the SharePoint site address, and then tap Go .

To browse a SharePoint site

  1. In the Office Hub, flick to Locations.
  2. Tap the SharePoint site, document library, list, or folder that you want to browse.
  3. Tap Up to go up one level in the SharePoint site.
  4. To open the SharePoint site in your phone’s web browser, tap More > Open in browser.

To search the SharePoint site for a document

  1. In the Office Hub, flick to Locations.
  2. Tap the SharePoint site, document library, list, or folder that you want to search.
  3. To search the current view for a document, tap Search . In the Search box, start typing the document name, and then tap the document when you see it.
  4. If no matches are found in the current view, tap Search for documents on to search for the document on the SharePoint site.
  5. Tap the document to open it on your phone.

To open, edit, and save changes to an Office document on a SharePoint site

From your phone, you can open and edit any Office file stored on a SharePoint site.

  1. In the Office Hub, flick to Locations.
  2. Tap the SharePoint site, document library, list, or folder that has the document that you want to open and edit.
  3. Tap the document that you want to open.

A copy is downloaded to your phone.

  1. Make and save your changes as you normally would.

The changes you make will be saved on the SharePoint site. Other people in your company or organization can then open the same version of the document that you modified.

  1. Press the Back button to return to SharePoint Workspace Mobile.

To connect to a SharePoint 2013 site from outside your company’s network

If your organization uses a UAG server, you can connect to a SharePoint 2013 site when you’re away from the office by using either Wi-Fi or your phone’s cellular data connection. To do this, you’ll first need to configure the UAG server settings on your phone.

  1. On Start, flick left to the App list, tap Settings > Applications > Office.
  2. Tap UAG server.
  3. On the UAG server screen, do the following, and then tap Done:
    • In the UAG server address box, type the server address, beginning with https://.
    • In the User name box, type your domain and user name. For example, if you log on to your computer using domainName\user, you would type domainName\user in the box.
    • In the Password box, type your password.

To resolve a conflict

A conflict can occur if you’re editing a document from your phone, make some changes, and then try to save your changes to the SharePoint site after someone else has also made changes to the same document. When this occurs, you need to resolve the conflict before you can save the document back to the SharePoint site.

  1. If the Can’t upload message box is still displayed, tap OK.
  2. In the Office Hub, flick to Locations, tap the SharePoint site, tap and hold the document that has the upload error underneath it, and then tap View status.
  3. Tap Resolve on the Upload status screen.
  4. On the Conflict resolution screen, do one of the following, depending on what you want to do:
    • To update the document on your phone with the latest copy from the SharePoint site, tap Replace item on phone, and then tap Refresh copy. Warning: The changes you made to the document on your phone will be lost.
    • To save a copy of the document that’s on your phone to the SharePoint site, tap Replace item on server, and then tap Refresh copy. Your copy will be saved to the SharePoint site and will overwrite the current version that’s on it.
    • To keep both versions of the document, rename your copy of the document on your phone. Tap Save as, type a file name in the File name box, and then tap Save. Sync your phone with the server so that you also have the newer version of the document from the server, and you’ll have both copies to compare on your phone.

To keep an offline copy of a document on your phone

You can make sure a copy of a document always remains on your phone by keeping it offline. When you do this, a partnership is set up between the copy on the SharePoint site and the one on your phone. If the copy on the SharePoint site is updated and you open the copy of the document that’s on your phone, you’ll be notified and can open the newer version on your phone. Likewise, you can make changes to the document on your phone and save them back to the SharePoint site.

  1. In the Office Hub, flick to Locations.
  2. Tap the SharePoint site, document library, list, or folder that contains the document that you want to keep offline on your phone.
  3. Tap and hold the document, and then tap Always keep offline.

To email a link to a SharePoint site

  1. In the Office Hub, flick to Locations.
  2. Tap and hold the SharePoint site, and then tap Send link.
  3. Tap an email account name.
  4. Add the recipient and any other information to your email, and then tap Send .


You can also tap and hold on a document library, list, folder, or document, and then tap Send link to send a link to one of these items.

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 :: How to Access SharePoint Data from Provider-Hosted Apps Use the Right Context

Recently I have focused on building apps that access, manipulate, and interact with data stored in SharePoint Online with Office 365. If you have done any development using the client-side object model (CSOM) for SharePoint, you understand the importance of instantiating the proper ClientContext object to access data in a particular SharePoint site. The ClientContext constructor takes as an argument the URL of a SharePoint site and allows you to access data stored in the Lists collection of the Web associated with it. In this post, I will discuss the various context objects you should use in your provider-hosted app depending on where the data your app needs to access resides and if the user’s permissions need to be considered. If you have been developing apps for SharePoint for awhile now (and even if you haven’t), I strongly encourage you to use Visual Studio 2013 and the Office Developer Tools for Visual Studio 2013

Host webs and app webs

When dealing with apps for SharePoint, you will become familiar with host webs and app webs:

  • Host web – the SharePoint site to which an app is installed
  • App web – the special isolated site (a unique app web is provisioned for each installation of the app) where the app for SharePoint’s internal components and content, such as lists, content types, workflows, and pages, are deployed

Note that a provider-hosted app is not required to have an app web, and in fact may not need one depending on your business requirements.

Your app will always have Full Control permissions to its app web. However, your app will need to request (and be granted) permissions by the user installing your app in order to access data in the host web. This is handled through the app manifest.
If your app needs to access data in the SharePoint site where it is being installed, you will be working with a host web context of some sort. As you will see, there are actually two different host web context objects, depending on the app authorization policy you choose.
Life made easy, thanks to SharePointContext.cs

When you create a new provider-hosted app in Visual Studio 2013, you have the option to create a new ASP.NET Web Forms or MVC application to serve as your app’s remote web application. If you are using the Office Developer Tools for Visual Studio 2013, you also have the option to convert an existing ASP.NET web application to an app for SharePoint project (really cool!) In either case, you will notice that SharePointContext.cs is added to the remote web application project. This file contains class definitions forSharePointAcsContext and SharePointHighTrustContext, which allow you to create host web and app web context objects based on whether your trust broker is ACS (which it is with Office 365) .
Accessing data in the app web
To access data in the SharePoint app web from your app, use the following pattern:


var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);using (var clientContext = spContext.CreateUserClientContextForSPAppWeb()){Web web = clientContext.Web;



ListCollection lists = web.Lists;





var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);HttpWebRequest listRequest = (HttpWebRequest)HttpWebRequest.Create(spContext.SPAppWebUrl + “/_api/web/lists”);listRequest.Method = “GET”;listRequest.Accept = “application/atom+xml”;

listRequest.ContentType = “application/atom+xml;type=entry”;

listRequest.Headers.Add(“Authorization”, “Bearer ” + spContext.UserAccessTokenForSPAppWeb);


var appweburl = decodeURIComponent(getQueryStringParameter(“SPAppWebUrl”));var clientContext = new SP.ClientContext(appweburl);var appWeb = clientContext.get_web();var appWebListColl = appWeb.get_lists();


clientContext.executeQueryAsync(onAppWebGetListSuccess, onError);

Accessing data in the host web

To access data in the SharePoint host web (the SharePoint site where your app is installed) from your app, use the following pattern:


var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);using (var clientContext = spContext.CreateUserClientContextForSPHost()){Web web = clientContext.Web;



ListCollection lists = web.Lists;





var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);HttpWebRequest listRequest = (HttpWebRequest)HttpWebRequest.Create(spContext.SPAppWebUrl + “/_api/web/lists”);listRequest.Method = “GET”;listRequest.Accept = “application/atom+xml”;

listRequest.ContentType = “application/atom+xml;type=entry”;

listRequest.Headers.Add(“Authorization”, “Bearer ” + spContext.UserAccessTokenForSPHost);


var appweburl = decodeURIComponent(getQueryStringParameter(“SPAppWebUrl”));var hostweburl = decodeURIComponent(getQueryStringParameter(“SPHostUrl”));var clientContext = new SP.ClientContext(appweburl);var factory = new SP.ProxyWebRequestExecutorFactory(appweburl);


var appContextSite = new SP.AppContextSite(clientContext, hostweburl);

var hostWeb = appContextSite.get_web();

hostWebListColl = hostWeb.get_lists();


clientContext.executeQueryAsync(onHostWebGetListSuccess, onJSOMError);

Note that using JSOM, we still need to construct a ClientContext for the app web before we generate an AppContextSite for the host web, made possible through theSP.ProxyWebRequestExecutorFactory.

A note about the app-only authorization policy

By default, authorization checks in the host web succeed only if both the current user and the app have sufficient permissions to perform the action in question, such as reading from or writing to a list. We are reminded that the user’s permissions are taken into account based on the names of the context and access token objects we use in these scenarios: for instance, CreateUserClientContextForSPHost and UserAccessTokenForSPHost. However, your app has the ability to do something akin to running with elevated privileges using the app-only policyfor authorization. Also controlled through the app manifest, the app-only policy is useful when an app doesn’t need or want to consider the permissions of the current user. In Visual Studio 2013, you can specify that your app would like to have the ability to use the app-only policy by checking this box in the AppManifest.xml editor.
That being said, just because your app is granted this permission does not mean that you can use the same host web context or access token as before to automatically leverage it. To access data from the SharePoint host web (taking only your app’s permissions into account and ignoring the current user’s permissions) from your app, use the following pattern:


var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);using (var clientContext = spContext.CreateAppOnlyClientContextForSPHost()){Web web = clientContext.Web;



ListCollection lists = web.Lists;





var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);HttpWebRequest listRequest = (HttpWebRequest)HttpWebRequest.Create(spContext.SPAppWebUrl + “/_api/web/lists”);listRequest.Method = “GET”;listRequest.Accept = “application/atom+xml”;

listRequest.ContentType = “application/atom+xml;type=entry”;

listRequest.Headers.Add(“Authorization”, “Bearer ” + spContext.AppOnlyAccessTokenForSPHost);

Remember that in order to use the app-only policy, your app must request and be granted this permission by the site owner who installs your app. Also note that there is no JSOM example using the app-only policy because apps that do not make OAuth authenticated calls (such as apps that are only JavaScript running in the app web) cannot use the app-only policy.
As you can see, the code you write in each of the above scenarios (accessing data in the app web, host web, or using the app-only authorization policy) is identical except for the method or property you use from the SharePointContext class to get the appropriate context or access token. Understanding these subtle differences is vitally important when making sure your app has the ability to access and manipulate the SharePoint data it needs.

SharePoint 2013 Hosting With :: Tips How to Creating a SharePoint development environment

SharePoint 2013 Development Environment

ahp_freehostSHP(1)Creating a SharePoint development environment is a task that can be challenging because the aim is to produce a usable environment, often on resource-constrained hardware. Keep in mind that no amount of tweaking will yield a satisfactory result unless your machine meets the minimum requirements for SharePoint 2013. Here are some tips to keep your dev box humming along nicely:

  • Memory – use as much of it as you can. 8 GB is the absolute minimum and even this amount may cause you some problems. If SQL Server starts paging to disk you’ll get no work done.
  • When using a hypervisor such as Hyper-V make sure you allocate more than 1 CPU core to your SharePoint VM.
  • Set a maximum server memory limit in SQL Server.
  • Don’t create a search service application unless you need one. Those noderunner.exe processes will gobble up lots of memory. You can limit the memory usage by editing the noderunner.exe.config file located in C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0. Look for the memoryLimitMegabytes attribute.
  • If you have a search service application disable continuous crawling and don’t set any crawl schedules. Crawl your content when you need to.
  • Use Set-SPEnterpriseSearchService -PerformanceLevel Reduced to reduce the CPU impact the search service has on your dev environment.
  • Pause the search service application if you’re not using it.
  • Keep the number of web applications to a minimum. Lots of IIS application pools means increased memory usage.
  • Configure an agressive diagnostic log storage limit. You probably won’t need days or weeks of trace log history at your fingertips.
  • Set the recovery model of your SharePoint databases to Simple. This will eliminate the need for a SQL maintenance plan. Many developers overlook SQL log file rotation until their dev machine runs out of storage.
  • Disable usage data collection (unless you need it).
  • Don’t use your regular domain account to run SharePoint services and don’t make it a local administrator of your development box. Develop and test using different user accounts.
  • Keep in mind that these tips are designed to make your personal development environment responsive and easy to work with. A production SharePoint environment would not need these changes as it should be properly resourced and managed.

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 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.

SharePoint 2013 Hosting – :: Binding SAP UI 5 aka Open UI 5 Table with List data from SharePoint 2013 REST API

Binding SAP UI 5 aka Open UI 5 Table with List data from SharePoint 2013 REST API


SAP UI 5 aka Open UI 5 is a new development framework available for SAP developers to expose and consume SAP data as JSON objects via REST API calls. Since it is a JavaScript UI library like jQuery UI, this can be used with any client side application that can make use of JSON

To be frank, this is the biggest client side library I have used so far. When extracted, the runtime files alone comes to 55 MB and the total number of files counts to 4K +
This is huge and bit complex and I am using it for quite some time for one of my SharePoint Project as it is heavily dependent on SAP data and UX design.
This article provides details on how to use SAP UI 5 in a SharePoint Application


  1. Download Open UI 5 runtime from
  2. Extract the content and move it to a new folder named sap-ui5 in layouts folder of 15 hive ( In a typical installation the folder path would be C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS)
  3. jQuery library to perform REST calls

For this demo, I have directly placed all the files under layouts folder.
Packaging and deploying it through a WSP solution or uploading it to Style Library or any other doc lib directly are also other alternative approaches.
I have also created a new list named “Employees” with columns Title and Location

Note: This article on developing SAP UI 5 applications in Visual Studio provides more details on how to create a basic Open UI 5 application with Visual Studio


  1. Create a new SharePoint Page
  2. Add a Script Editor Web part to the page
  3. Copy and paste the below code in Script Editor
 	$.getJSON("/_vti_bin/listdata.svc/Employees", function (data) {
 		var sTable = new sap.ui.table.Table({
 			width: "500px",
 			visibleRowCount: 5
 		sTable.setTitle("Employee Details");
 		sTable.addColumn(new sap.ui.table.Column({
 			label: new sap.ui.commons.Label({ text: "Employee Name" }),
 			template: new sap.ui.commons.TextView().bindProperty("text", "Title"),
 		sTable.addColumn(new sap.ui.table.Column({
 			label: new sap.ui.commons.Label({ text: "Location" }),
 			template: new sap.ui.commons.TextView().bindProperty("text", "Location"),
 		var oModel = new sap.ui.model.json.JSONModel();
 		oModel.setData({ modelData: data.d.results });
 	}, function () { alert('failed'); })
 <div id='Emp'></div>

Note : If you have placed the libraries in a different location, change the URL before pasting it in the script editor

image.axdEverything is in place you would be able to view a grid similar to the one displayed above

SharePoint 2013 Hosting with – How To Migrate Content Database From SharePoint 2010 To SharePoint 2013

Migrate Content Database From SharePoint 2010 To SharePoint 2013

In this article, we will take you through the database migration process from SharePoint 2010 to SharePoint 2013. An overview of the SharePoint database migration process to a new server is available on the ShareGate website.


Step-by-step to migrate content database

  • Step 1 : Make two servers available for the process. Both the servers need to run on the same environment. For instance, Server 1 should run on Windows 2008, SQL server 2008 and include SharePoint 2010. Server 2 should run on Windows 2008, SQL server 2008 and include SharePoint 2013.
  • Step 2 : You must begin with backing up the data from Server 1. To do this,

a) While on SharePoint 2010, pick the database of the port you want to back-up. Right click and from the options that appear, click Tasks → Back Up.
b) In the subsequent window that opens, click ‘Add
c) Copy the location available under the ‘Destination’ field and save it a notepad for later use.

  • Step 3 : On server 2, launch SharePoint 2013 and create a new web application under any port. If you are not sure, pick port 88.
  • Step 4 : Once a new application has been created, perform the following steps:

a) Under Central Administration, select Application Management Manage Content Databases
b) Under the newly created web application, select ‘Remove content database checkbox’. Click OK and SAVE
c) Under the Content Database section, you should now see a message that reads, “There are no items to show in this view’

  • Step 5 : The next step is to restore the database from SharePoint 2010 to the new server. To accomplish this, copy the WSS_Content.bak file from Server 1 on to the desktop or any convenient location on the computer handling Server 2.
  • Step 6 : In SharePoint 2013, launch SQL Server 2008 and right click on the node titled Database and from the options, choose ‘Restore Database’.
  • Step 7 : A new ‘Restore Database’ window now opens. Here, select the ‘From Device’ radio button and browse through your system folders to select the WSS_Content.bak file that we had earlier copied in Step 5. Click OK
  • Step 8 : Next, under the ‘Options’ tab of the Restore Database window, check the box that reads, “Overwrite the existing database (WITH REPLACE)”. Press OK to continue. A message box appears that confirms the operation. Press OK to close this box.
  • Step 9 : Open SharePoint 2013 and navigate to Central Administration → Application Management → Manage Content Databases. You should now see the WSS_Content.bak file displayed here.
  • Step 10 : On the top of the window, you will see a message. Click on the ‘Start Now‘ link to continue.
  • Step 11 : In the subsequent window, click on the ‘Upgrade the site collection’ option. You will be shown a message box. Click ‘I’m Ready‘ to continue.
  • Step 12 : The upgradation process will now begin. This typically takes a few minutes. Once you are done, you will be shown a message that reads, “Upgrade Completed Successfully”

This completes the process. Your content database migration from SharePoint 2010 to SharePoint 2013 has been completed successfully.

SharePoint 2013 Hosting – :: Event ID 6398 AppFabric Distributed Cache Error

Sharepoint 2013 Event ID 6398 AppFabric Distributed Cache Error

ahp_freehostSHPBefore, I started seeing repeated errors with Event ID 6398 and description of:

The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 581fc80e-f7fb-4b3b-99cd-7affa208f57b) threw an exception. More information is included below. Unexpected exception in FeedCacheService.BulkLMTUpdate: Unable to create a DataCache. SPDistributedCache is probably down

This error occurs every 5 minutes as the User Profile Service – Feed Cache Repopulation Job ran and it also prevented anything from populating the My Sites Newsfeeds section. The Newsfeeds page would only return “We’re still collection the latest news. You may see more if you try again a little later.” I tried to follow a multitude of blog posts, forum posts and articles on repairing the AppFabric Distributed Cache Service and was unable to correct the error.

My next step was to try to get the AppFabric service back to the initial setup.

  • Remove the AppFabric setup from Add/Remove Programs.
  • More information on this process in this MSDN article and also follow the link from there to Clean up any remaining AppFabric settings either manually or using the Cleanup Tool they provide.
  • After rebooting, I downloaded the AppFabric 1.1 Installer from here.

However, do not install it manually, instead use the SharePoint 2013 setup disc to use the prerequisite installer to install and configure AppFabric using the following command:

prerequisiteinstaller.exe /appFabric:C:\pathto\WindowsServerAppFabricSetup_x64.exe

Now you can continue on with the initial configuration of the AppFabric service. I ran the following command from the SharePoint 2013 PowerShell as Administrator

$instanceName ="SPDistributedCacheService Name=AppFabricCachingService"

$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($ -eq $env:computername}

  • Then run


You should see the Distributed Cache service running in Manage Services on Server in Central Administration and also see the AppFabric Caching Service running in Services. If you don’t then try Remove-DistributedCacheServiceInstance and Add again. After completing this process, I was able to go back to MySites and see the Newsfeed as it should be and also no more errors in the Event Log.

NewsFeed Working

I would love to know why this occurred since I was not working on anything with the Caching service prior to the errors; however, I hope this helps someone else caught up in this problem.