Enable notifications for Tasks list in SharePoint 2013

Hi SharePoint Folks,

In SharePoint 2013 you will find that the option to enable email notification for Tasks list is no longer there. It used to be under List Settings > Advanced Settings > Send e-mail when ownership is assigned? (Yes/No). It is still there for Issues list in SharePoint 2013 however. now you need to enable email notification from Power Shell through this script.

Add-PSSnapin Microsoft.SharePoint.Powershell
$web = Get-SPWeb "http://myServer/myWeb"
$list = $web.Lists.TryGetList("Tasks")
$list.EnableAssignToEmail = $true

Once email notification is enabled for the Tasks then create new task and assign to any user. after that user will receive the email regarding new task which assigned to him or her.

Note: Before you run this code, make sure that you have configured outgoing mail.

Happy SharePointing 😉


Administration Content Database in Suspect Mode


Go to your SQL Server and ensure either your Central Admin Content Database or Config Database, if it is in Suspect mode,  see snapshot below:



Central Admin Content database or a Config database can abruptly go into the suspect mode without any apparent logical reason. In my case, SharePoint Central Admin Content Database went into the Suspect mode.

To resolve the issue, follow steps in the following order as mentioned:

Go to your MSSQLData files that reside under: C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLDATA




. Identify your Central Admin Content Database name in my case it got screwed up and was in the suspect: mode: so this is my content database name SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c

Please take a backup of the corrupted .mdf and .ldf files, before following other steps.


Open your SQL Server Management Studio ->, New Query and it opens up your SQL Query editor, copy and paste the query below and change the highlighted to your database name:

Use master

–Verify whether Database has any issues
EXEC sp_resetstatus “SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c.mdf”

—Alter database and put it on Emergency Mode
ALTER DATABASE “SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c” SET EMERGENCY
DBCC checkdb(‘SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c’)

–Set the database in the Single User mode
ALTER DATABASE “SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c” SET SINGLE_USER WITH ROLLBACK IMMEDIATE

–Repair the database and allow data loss
DBCC CheckDB(‘SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c’,REPAIR_ALLOW_DATA_LOSS)

–Set the database back to Multi-User mode
ALTER DATABASE “SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c” SET MULTI_USER

–Ensure Database is reset
EXEC sp_resetstatus ‘SharePoint_AdminContent_38c5cc2d-aeec-4dc2-b7a5-65457250ae2c’


Execute all the commands in your SQL Query Editor and there you go, Go back to your SQL Management Studio and you can see that the (Suspect) mode issue against the Content/Config database is fixed and the database got fully repaired and restored.

To verify , hit your Central Administration and it starts working just fine…


Happy SharePointing 😉

Crazy Distributed Cache (AppFabrikCache) SharePoint Server 2013

SharePoint geeks,

well i can not tell you how many time i have repaired this service and it takes my patience exam in every end of week. And i have done many battles with this service. i still couldn’t find the reason why it stop often, if anyone knows that Please let me know. so i thought  should share my experience with other geeks.  just few steps to repair this service.

What Is Distributed Cache Service?

Distributed Cache Service is a customized version of Windows App Fabric deployed in SharePoint 2013.
The Distributed Cache service provides caching functionality to features in SharePoint Server 2013. The Distributed Cache service is either required by or improves performance of the following features:

  • Authentication
  • Newsfeeds
  • OneNote client access
  • Security Trimming
  • Page load performance

There is no GUI for AppFabric so make sure  following 10 named cache containers should be there through this cmd.

Run SharePoint Management Shell and use below cmd this command should return the list of these containers.

  •  Get-Cahce
  1. DistributedDefaultCache
  2. DistributedAccessCache
  3. DistributedActivityFeedCache
  4. DistributedBouncerCache
  5. DistributedLogonTokenCache
  6. DistributedServerToAppServerAccessTokenCache
  7. DistributedSearchCache
  8. DistributedSecurityTrimmingCache
  9. DistributedActivityFeedLMTCache
  10. DistributedViewStateCache

Allocate Memory on Distributed Cache Service

When SharePoint Server 2013 is installed, 10% of the total physical memory is allocated. The Distributed Cache service use 50% of this memory as storage and the other to manage the memory.

This cache size can be increased when:

  • You add more memory on the Server
    • Be aware,  when you add memory to the server, the Distributed Cache isn’t updating by himself. You need to reconfigure the Cache Size.
  • If you have a dedicated caching server
    • You should calculate it so :
  • Determine the total sum of physical memory. Let’s take the example that your server has 16GB of memory.
  • You have to book 2 GB of memory for other processes. So this means 16GB – 2GB = 14GB

Now we have to take the half of this amount and that size is our AppFabric Cache Size : 14GB / 2 = 7GB

Change the Memory allocation

Use this procedure to reconfigure the memory allocation of Cache Size

Get-APCacheHostConfiguration –ComputerName –CachePort  22233

you can also update from Central Administration

Graceful shutdown of the Distributed Cache Service

use SharePoint Management Shell to run these commands

  • Stop-SPDistributedCacheServiceInstance – Graceful
  • Remove-SPDistributedCacheServiceInstance

make sure your Distributed Cache service using Farm Account  if not so you first need to change its service account. below are the commands through which you can change Distributed Cache service account.

  • $farm = Get-SPFarm
  • $cacheService = $farm.Services | where {$_.Name –eq “AppFabricCachingService”}
  • $account = Get-SPManagedAccount –Identity  domainnameUSER_NAME
  • $cacheService.ProcessIdentity.CurrentIdentityType = “USER”
  • $cacheService.ProcessIdentity.ManagedAccount = $account
  • $cacheService.ProcessIdentity.Update()
  • $CacheService.ProcessIdentity.Deploy()

Add new Service Instance 


after restart Cahce Cluster just run IISRESET cmd.

That’s it you done.

Happy SharePointing 😉

SharePoint 2013 Integration with Office 365 and Yammer

Hi Folks,

Microsoft recently released Service pack 1 for SharePoint 2013. service pack 1 contain some new features like Office 365 and Yammer integration with SharePoint 2013 Server.

You can now configure Yammer and OneDrive for Business on Office 365 with SharePoint On-Premises integration. This can be done via Central Administration:




OneDrive now replaces SkyDrive in the top link bar. Included with this is Yammer, if you activate the Yammer feature on-premises via Central Administration.




When you click on the Yammer link, you’ll be redirected to /_layouts/15/Yammer.aspx and be asked to log in.



Once Yammer is activated, the SharePoint  newsfeed will now display this message when you visit your MySite.


For OneDrive for Business on Office 365 integration, again in Central Administration -> Office 365 -> Configure OneDrive and Sites Link, you’ll simply input your OneDrive host in Office 365 (https://-my.sharepoint.com) and the top link bar will redirect you there when you click on OneDrive.




Happy SharePointing 😉





SharePoint 2013 Support for Windows Server 2012 R2

Hi Folks!

well since morning i have been working on demo Virtual Machine and i have faced lots of issues while  installing  SharePoint 2013 on WindowsServer 2012 R2. but finally after 2 hours i have installed the SharePoint 2013 Server on WindowsServer 2012 R2 and configured most of the services but when i have configured Workflow service and try to register my Test site with Workflow Farm it was refusing and PowerShell was throwing errors like Register-SPWorkflowService : The remote server returned an error: (404) Not Found. Then i tried to create new scope with            –ScopeName  but it was also not working. Unfortunately i have wasted whole day to figure out the issue but couldn’t find . then i dug more in Google and Bing search and i found the article which says that  currently SharePoint2013 is not supported for installation on computer running WindowsServer 2012 R2. Here is the link you can find more information TechNet. Please comment on this blog If anyone has information regarding this issue i would appreciate.

“Currently, Microsoft SharePoint Server 2013 is not supported for installation on computers running the Windows Server 2012 R2 operating system.   Installing SharePoint Server 2013 on a computer that is running Windows Server 2012 R2 could lead to unexpected behavior, therefore, Microsoft does not support SharePoint Server 2013 in Windows Server 2012 R2.  SharePoint Server 2013 with Service Pack 1 and SharePoint Foundation 2013 with Service Pack 1 will offer support for Windows Server 2012 R2. The release date for Service Pack 1 for SharePoint Server 2013 and SharePoint Foundation 2013 is to be determined. This article will be updated as more information becomes available.”

Happy SharePointing 🙂

Geolocation field in SharePoint 2013

In this article I’ll show what this field does, a sample of creating and using the field, getting and setting the Bing Maps keys to make sure our maps are properly working and displaying.

What are the location and map features in SharePoint 2013?

SharePoint 2013 introduces a new field type named Geolocation that enables you to annotate SharePoint lists with location information. In columns of type Geolocation, you can enter location information as a pair of latitude and longitude coordinates in decimal degrees or retrieve the coordinates of the user’s current location from the browser if it implements the W3C Geolocation API. In the list, SharePoint 2013 displays the location on a map powered by Bing Maps.
Create a plan list called Location

The same list, with the Geolocation field added to it

When we’ve added the Geolocation field to support our Bing Maps, you can see that a new column is displayed in the list view and you can interact with it. In my sample here I’ve filled in the coordinates for the four office locations  I’ve listed in my list.


Pressing the small globe icon will bring up a nice hover card kind of dialog with the actual map.
Viewing an actual list item looks like this, with the map fully integrated by default into the display form
when edit the item it looks like this. in this you have to mention location. you need to specify you location by longitude and latitude. and also you can use “use my location”  option but your browser should supports the usage and tracking of your location.

now enter your longitude and latitude.


Adding a Geolocation Field to your list

let’s move on to the actually adding the field to our list.  you can definitely add it using code and scripts, which is my preferred way to add stuff anyway.

Adding a Geolocation field using PowerShell

Add-PSSnapin Microsoft.SharePoint.PowerShell
$web = Get-SPWeb "http://url.com"
$list = $web.Lists["Stores Location"]
$list.Fields.AddFieldAsXml("<Field Type='Geolocation' DisplayName='Office Location'/>",$true,

Adding a Geolocation field using the .NET Client Object Model

function AddGeolocationFieldSample()
var clientContext = new SP.ClientContext();
var targetList = clientContext.get_web().get_lists().getByTitle('Scandinavian Microsoft Offices');
fields = targetList.get_fields();
fields.addFieldAsXml("<Field Type='Geolocation' DisplayName='Office Location'/>",true,SP.AddFieldOptions.addToDefaultContentType)
clientContext.executeQueryAsync(Function.createDelegate(this, this.onContextQuerySuccess), Function.createDelegate(this, this.onContextQueryFailure));

Using Server Object Model:
SPWeb web = site.RootWeb;
SPList list = web.Lists.TryGetList("Stores Location");
if(list != null)
{list.Fields.AddFieldAsXml("<Field Type='Geolocation' DisplayName='Office Location'/>",true,SPAddFieldOptions.AddFieldToDefaultView);}

Bing Maps – getting and setting the credentials in SharePoint.

after field creation you need to set bing maps credential other wise you will face issue on your map. as you can see the issue in picture.

Get your Bing Maps keys

If you don’t have any credentials for Bing Maps, you can easily fetch them by going to the specified Url (http://www.bingmapsportal.com) and follow these few simple steps.
you will have to enter some information to create a new key and then click ‘Submit’
After you’ve clicked ‘Submit’ you’ll be presented with a list of your keys, looking something like this.
Great you have done now. Now we need to let SharePoint know about this as well!
we have a Property Bag on the SPWeb object called “BING_MAPS_KEY” which allows us to configure our key.

Setting the BING MAPS KEY using PowerShell on the Farm

Set-SPBingMapsKey -BingKey "FFDDuWzmanbiqeF7Ftke68y4K8vtU1vDYFEWg1J5J4o2x4LEKqJzjDajZ0XQKpFG"

Setting the BING MAPS KEY using PowerShell on a specific Web

Add-PSSnapin Microsoft.SharePoint.PowerShell
$web = Get-SPWeb "http://url"
$web.AllProperties["BING_MAPS_KEY"] = "FFDDuWzmanbiqeF7Ftke68y4K8vtU1vDYFEWg1J5J4o2x4LEKqJzjDajZ0XQKpFG"
Also you can create MAP View from create views.  And now browse your list and add new item as a location……
Hope this Help 🙂 😉
Happy SharePointing

Convert VHDX to VHD format in Hyper-V

Hi guys,

i was importing windows 8.1 Virtual Machines in Windows server 2008 r2 Hyper-V environment so i have faced many issues in importing the VMs, so i experienced that you can not directly import windows 8.1 or windows server 2012 Virtual Machine into windows server 2008 r2. you have to convert the VHDX into VHD then you will be able to import in windows server2008 r2, i was wondering to write a blog  post on this topic. Please follow these steps to convert it into VHD.

Open your Hyper Server


Right click on the virtual machine which you want to export and click on setting option


Click on  hard drive option on your left and then click on edit button.


once located and selected click on next

you will new be prompt with 3 options

1). Compact

2). Convert

3). Expand

Select convert


now select what version you want to convert in my case i wan to export in VHD. click next


when you initially created the virtual machine if you accidentally dynamic instead of fixed here id one way to change that. if you want to keep it the same in this case dynamically available just click next


Select the path where you want to save this VHD


now click on finish to start the process


now wait for a while it will save your VHD in your given path. after complete this process you can import this VHD in Windows server 2008 R2.

Thanks and Regards

Configure SSL for SharePoint 2013

In this post i will show you how to configure SSL for your SharePoint2013 site.


  1. Create Self Signed Certificate on IIS 8
  2. Import Self Signed Certificate to SharePoint Certificate store
  3. Add Self Signed Certificate to trust management in Central Administration
  4. Configure IIS Binding
  5. Configure AAM

Note: Make sure to perform these steps with admin privileges.

Step 1: Create Self Signed Certificate on IIS 8

Open IIS Manager and then go to Server name and choose IIS Section “Server Certificates


Click on Create Self-Signed Certificate… on Actions pane

Specify a name like “SharePointSelfSignedCert” and click Ok


Double click on this created Certificate and go to details Tab and click copy to File…

Click Next (Welcome…),

Select No, do not export the private key and click Next ,

Select DER encoded binary and click Next,

Specify the location for the certificate and Click Next and then finish (Imported).

Step 2: Import Self Signed Certificate to SharePoint Certificate store

Open Manage Compute Certificate on Windows Server 2012 and go to SharePoint node and then right click All tasks >> import

Click Next and then specify the location of exported certificate in previous step and then Click Next,

Make sure Certificate store is SharePoint and Click Next and then finish (Exported)

Step 3: Add Self Signed Certificate to trust management in Central Administration

Go to Central Administration >> Security >> Manage Trust (to inform SharePoint to trust this certificate also).

And Click New

And a name and specify the location for the certificate and Click Ok.

Step 4: Configure IIS Binding

Go to IIS Manager and choose your web application and then click on Binding in Actions pane


Click Add..

Type: Https

SSL Certificate: SharePointSlefSignedCert (which created previously).

Click Ok.

Step 5: Configure AAM

Go Central Administration >> Alternate Access Mapping and Choose your web application

And click on Edit Public URLs and then add HTTPS URL


And Click Save.

Now try to brows your site with HTTPS URL


Thanks and Happy SharePointing 😉

Office WebApp Server2013 Installation and Configuration

Office Web Apps Server supports two primary installation scenarios: a single-server Office Web Apps Server farm, and a multi-server, load-balanced Office Web Apps Server farm. You can use physical servers or virtual machine instances to run Office Web Apps Server, but you can’t install other server applications, such as SharePoint 2013 or SQL Server, on those servers. In environments that contain actual user data.

Supported Operating Systems for Office Web App server 2013

        You can run Office Web AppServer on the following operating systems

  •  The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter with KB2592525 installed
  • The 64-bit edition of Windows Server 2012 Standard or Datacenter

 server roles, and features that are required for Office Web Apps Server

Download, Server Role, or Feature Windows Server 2008 R2 Windows Server 2012
Download: Office Web Apps Server Microsoft Download Center Microsoft Download Center
Download: .NET Framework 4.5 .NET Framework 4.5 Already installed
Download: KB2592525 KB2592525 Already installed
Download: Windows PowerShell 3.0 Windows PowerShell 3.0 Already installed
Server role: Web Server (IIS) The following list describes the minimum role services that are required for the Web Server (IIS) server role.Common HTTP Features

  • Static Content
  • Default Document

Application Development

  • .NET Extensibility
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes


  • Windows Authentication
  • Request Filtering

Management Tools

  • IIS Management Console

The following options are recommended but not required:


  • Static Content Compression
  • Dynamic Content Compression
The following list describes the minimum role services that are required for the Web Server (IIS) server role.Management Tools

  • IIS Management Console

Web Server

  • Common HTTP Features
  • Default Document
  • Static Content


  • Request Filtering
  • Windows Authentication

Application Development

  • .NET Extensibility 4.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes

The following services are recommended but not required:


  • Static Content Compression
  • Dynamic Content Compression
Feature: Ink and Handwriting Services Ink and Handwriting Services

  • Ink Support
Ink and Handwriting Services

You don’t have to install Ink Support. You can just install Ink and Handwriting Services

 Hardware Requirement – Application Server

The requirements in the following table apply both to installations on a single server with a built-in database and to servers running Office Web App Server 2013 in a multiple server farm installation.


Minimum requirement

Processor Intel Xeon Processor E7 (16 core).
  • 12 GB for developer
  • 64 GB for production use in a single server or multiple server farm


Hard disk 500 GBYou must have sufficient space for the base installation and sufficient space for diagnostics such

as logging, debugging, creating memory dumps, and so on. For production use, you also need

additional free disk space for day-to-day operations. Maintain twice as much free space as you

have RAM for production environments. For more information, see Capacity management and  sizing for SharePoint Server 2013.


 Prepare the servers

In this phase, you get your servers ready to host the product. This includes the supporting servers and

the servers that will have Office web app Server installed. The following servers must be configured to

support and host a farm:

  • Domain Controller
  • Application Server of Office web app

 Required Permission

The following table describes the accounts that are used to install and configure Office WebApp Server 2013.





domain-OfficeWebApp This account would responsible to run Office webapp server and services Logon locally in office web app server and administrative rights, Run Office web app server2013

 prepare a server that runs Windows Server 2012

  1. Open the Windows PowerShell prompt as an administrator and run the following command examples to install the required roles and services.

For Windows Server 2012

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices



If you are prompted, restart the server when the command finishes.

  Install Office Web Apps Server

Mount Office Web Apps 2013 Install on the OWA2013 server and run the Install



 Office Web App Server CU Installation

Download and install the Office Web Apps Server 2013 update KB2810007.



Office Web App Server Configuration

 Create OWA Farm and Configure to use HTTP and Support Editing

  • Login on to OWA2013 Server with Office Web App Service Account
  • From an elevated PowerShell command prompt run below command


Test by accessing from outside your server http://owa2013/hosting/discovery


Office Web App Server Binding and Configuration with SharePoint Server 2013

  •  Login to SP2013WFE with SpAdmin Account
  • From an elevated SharePoint PowerShell command prompt run below command

Now you should see a long list application extension registration with the WOPIZone

To confirm type and test below command to verify that the new zone is internal-http

Change the AllowOAuthOverHttp setting in SharePoint 2013 to True. Run below command

That means we will need to allow SharePoint to allow OAuth over HTTP by running below commands

Now check one more time the status of OAuth over http

Now once again check the WOPI Zone and as you can see it is still se to internal-https

For this installation test since I had used internal and http, I am going to set the WOPI Zone accordingly as below.

Test Office Web Apps with SP 2013

Browse to SharePoint site as user and not as system account (OWA does not work for system account)

Thanks Happy SharePointing 😉