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
$list.Update()

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 😉

Advertisements

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

Use-CacheCluster
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 

Add-SPDistributedCacheServiceInstance
Restart-CacheCluster

after restart Cahce Cluster just run IISRESET cmd.

That’s it you done.

Happy SharePointing 😉

Configure SSL for SharePoint 2013

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

Steps:

  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

1

Click on Create Self-Signed Certificate… on Actions pane

Specify a name like “SharePointSelfSignedCert” and click Ok

1

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

1

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

1

And Click Save.

Now try to brows your site with HTTPS URL

1

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

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

Security

  • Windows Authentication
  • Request Filtering

Management Tools

  • IIS Management Console

The following options are recommended but not required:

Performance

  • 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

Security

  • 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:

Performance

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

  • Ink Support
Ink and Handwriting Services

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

Component

Minimum requirement

Processor Intel Xeon Processor E7 (16 core).
RAM
  • 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.

Name

Password

Description

Policy

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

Untitled

Untitled

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

Untitled

Untitled

 Office Web App Server CU Installation

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

Untitled

Untitled

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

Untitled

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

Untitled

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 😉

How to remove orphaned features

Hey Good Day,

Few days back my test server was crashed and was unable to access every thing. then i have decided to rebuild my farm and restore my old content databases. after rebuil the farm then i have to deployed my all custom solutions WSP’s and infopath forms  so when i was trying to deploy my solution so central admin through the error while deploying the solutions. because its corrupted

System.InvalidOperationException: A feature with ID 15/71973039-401b-4257-9d01-565a5f908131 has already been installed in this farm.  Use the force attribute to explicitly re-install the feature.

if you try to uninstall the feature from PowerShell through these cmds then it will through the exception


Uninstall-SPFeature -Identity "59ad6e04-ffe4-46da-acbf-927d4eb5e3ba"

install-spfeature "C:formsPulishFormyouform.xsn" -Force

Uninstall-SPFeature : Cannot find a Feature object with Path or Id: a4d208a3-b4fa-4bca-bb34-be4d30156b63 in scope Local farm. At line:1 char:1 + Uninstall-SPFeature a4d208a3-b4fa-4bca-bb34-be4d30156b63 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (Microsoft.Share…ninstallFeature:SPCmdletUninstallFeature) [Uninstall-SPF eature], SPCmdletPipeBindException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletUninstallFeature

 

The workaround is to use the DisplayName to get the spfeature (actually SPFeatureDefinition) and then delete it.

Get-SPFeature | ? { $_.Scope -eq $null }



EgQWa

$feature = Get-SPFeature | ? { $_.DisplayName -eq "My_Orphane_Feature" }
$feature.Delete()

I have tested this code and it has worked for me.

You can even use this code to clean all the orphaned features:

Get-SPFeature | ? { !$_.Scope } | % { $_.Delete() }

This line of code gets all the orphaned features and removes them.

Thanks

Happy SharePointing 😉

 

Where is “Sign in as Different User” in SharePoint 2013

Hi all,

well this time i am going to discuss the missing option in SharePoint 2013. There is an option in SharePoint 2010 which allows you to log in as an another user.  With SharePoint 2013 this option is missing.

To get this feature back follow the following steps :

 

  1. Locate and then open the following file in a text editor:  C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15TEMPLATECONTROLTEMPLATESWelcome.ascx
  2. Add the following element before the existing “ID_RequestAccess” element:

    <SharePoint:MenuItemTemplate runat=”server” ID=”ID_LoginAsDifferentUser” Text=”<%$Resources:wss,personalactions_loginasdifferentuser%>” Description=”<%$Resources:wss,personalactions_loginasdifferentuserdescription%>” MenuGroupId=”100″ Sequence=”100″ UseShortId=”true” />

  3. Save the file.

Microsoft has published a KB article on the same : http://support.microsoft.com/kb/2752600.

Hope this information was helpful.

Happy SharePointing 🙂