OWA – Sorry, there was a problem and we can’t open this document


While viewing office document got following error message, and it was working till last time.

The error message I get for WORD, PDF and Excel files is:



to solved the problem disconnect SharePoint farm from Office Web Apps using the command
‘Remove-SPWOPIBinding –All:$true’

then reconnected the Farm to Office Web Apps by running the command
New-SPWOPIBinding -ServerName <OWA URL> -AllowHTTP

Once this was done, Office Web Apps started working.



Application error when access /_layouts/15/Workflow.aspx

While trying to view workflow detail page getting following error message:

Application error when access /_layouts/15/Workflow.aspx, Error=The pipe endpoint ‘net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc’ could not be found on your local machine.

Make sure the Net.Pipe Listener Adapter windows service is running, if not run net start NetPipeActivator or use windows services GUI. I hope this helps.

PowerPivot Gallery – Error Could not load type ‘Microsoft.AnalysisServices.SPAddin.DataRefresh.ViewDataRefreshHistory’.

You have PowerPivot all installed and configured.You’re very excited to go add a new PowerPivot application to the library when you click on the link and are greeted with a lovely error message (shown above) that reads Could not load type ‘Microsoft.AnalysisServices.SharePoint.Integration.ReportGalleryView’.   How do we fix this and why is it happening?


Here is what you need to do:

  1. Go to SharePoint Central Admin
  2. Go to the System Settings section
  3. Click on Manage Farm Solutions under the Farm Management section
  4. Click on powerpivotwebapplicationsolution.wsp
  5. Click Deploy Solution at the top of the screen
  6. In the Deploy To section select your web application from the drop down list
  7. Click OK

farm solution


Make sure that the website urls don’t have port numbers. You will probably have to retract your solution and then re-deploy it.

SharePoint web application Creation error – Internet Explorer cannot display the webpage

We can get this error due to slow response from the server either because of availability of low RAM. While creating a new web application, SharePoint reset IIS. Application pool will have 90 sec to close all the connections before force down. Sometimes 90 sec is not sufficient to close the connection. We have to improve the limit manually.

To increase the time we have to follow the steps below.

go to IIS manager > Application pools > SharePoint Central Administration v4 and click Advanced properties

In the opened window under Process model find the following settings:

  • Ping Maximum Response Time
  • Shutdown Time Limit (seconds)
  • Startup Time Limit (seconds)


Reset IIS.

Now we can create the webapplication without issues.

Hands-on session on SharePoint Administration

Event details are:
Date: Wednesday 19th March, 2014
Time: 03:00 pm till 7:00pm
Venue: Microsoft Innovation Center Karachi 1st Floor Media Science Building,
Bahria University, 13 National Stadium Road, Karsaz, Karachi.

Event Agenda:
• Overview of SharePoint 2013 Architecture
• Hardware and Software Requirements
• Installing SharePoint 2013
• Topology and Farm Configuration
• Working with Central Administration
• Configuring Security and Authentication
• Configuring Web Applications
• Managing Site Collections
• Backup, and Restore

1521623_606617859431438_1907313647_n WP_20140319_002 WP_20140319_006 WP_20140319_007 WP_20140319_008 WP_20140319_009 WP_20140319_010 WP_20140319_011

Request Manager in SharePoint 2013

What is Request Management?

Allows SharePoint to understand more about, and control the handling of, incoming HTTP requests. Having knowledge of the nature of incoming requests allows SharePoint to customize the response to each request

Architectural Overview

  • Request Manager is the first code that runs in response to HTTP requests
  • Request Manager runs in process on the web server
  • Request Management Service Instance should run on the web server
  • No Central Administration
  • 100% Windows PowerShell

Capacity Management

  • Request Management can send multiple or single requests to web servers that are designated to handle them.
  • Request Management can send requests to logical groups of servers based upon request characteristics

Deployment Modes

  • Integrated Mode : Request Management Service runs on the web servers in a farm
  • Dedicated Mode : A dedicated SharePoint farm which manages requests exclusively, and routes request to other farms

At a high level, the goals of RM are this:

  • RM can route to WFEs with better health, keeping low-health WFEs alive
  • RM can identify harmful requests and deny them immediately
  • RM can prioritize requests by throttling lower-priority ones (bots) to serve higher-priority ones (end-users)
  • RM can send all requests of specific type, like search for example, to specific machines
  • Isolated traffic can help troubleshoot errors on one machine
  • RM can send heavy requests to more powerful WFEs

 Routing and throttling rules are implemented like this:

  • Routing rules route requests and are associated with MachinePools
  • MachinePools contain servers
  • Servers use weights for routing – static weights and health weights
  • Static weights are constant for WFEs; health weights change dynamically based on health scores

Let’s walk through an example now:

#Get a reference to the SPWebApplication
$w = Get-SPWebApplication -identity http://foo

#Get a reference to the request management settings for the web application
$rmset = $w | Get-SPRequestManagementSettings

#Create one or more criteria
$criteria = New-SPRequestManagementRuleCriteria -Property Url -Value “.*\.docx” -MatchType Regex

#Get a reference to a machine pool, or create a new one if needed
$mp = Add-SPRoutingMachinePool -RequestManagementSettings $rmset -Name MyRulePool -MachineTargets ($rmset | Get-SPRoutingMachineInfo -Name WFE1)

#Add the rule
$rmset | Add-SPRoutingRule -Name “Word Doc Rule” -Criteria $criteria -MachinePool $mp

Let’s look at that routing rule now:
$rr = $rmset | Get-SPRoutingRule -Name “Word Doc Rule”

#see the criteria

#change the expiration date and time of the routing rule
$rr.Expiration = “12/25/2013 5:00:00 PM”

There you go – now you have a routing rule.  Creating a throttling rule is very similar:

#Add a new criteria rule that looks for OneNote requests.  It can do this by examining the UserAgent in the request and looking for the header that OneNote uses.
$criteria = New-SPRequestManagementRuleCriteria -Property UserAgent -Value “.*Microsoft Office OneNote 2010*” -MatchType Regex

#Add a throttling rule that uses the criteria rule when the server health reaches a score of 8.
#Note that throttle rules apply to the entire web application, #not to individual machines so you don’t
#use a machine pool with it.
$rmset | Add-SPThrottlingRule -Name “OneNote Throttle Rule” -Criteria $criteria -Threshold 8

#now view all routing rules for the web application

#View all of the throttling rules

Let’s look a little deeper at working with Machine Pools now:

#Get all routing machines that are available
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Availability Available

#Get every machine in a specific pool
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachinePool -Name yourPoolName | % { $_.MachineTargets} | Format-Table

#Add machine WFE1 to every machine pool for a particular web application; a million thanks to Tyler who helped me with this one – I ain’t a PowerShell guy really
$a = Get-SPWebApplication -Identity http://contoso
$b = $a | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Name WFE1
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachinePool | % { $_ | Set-SPRoutingMachinePool -machinetargets ($_.machinetargets + $b) }

#Add machine WFE1 to a specific pool
$a = Get-SPWebApplication -Identity http://contoso
$b = $a | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Name WFE1
$pool = $a | Get-SPRequestManagementSettings | Get-SPRoutingMachinePool -Name yourPoolName
$pool | Set-SPRoutingMachinePool -MachineTargets ($pool.MachineTargets + $b)

#Remove WFE1 from every machine pool
Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo -Name WFE1 | Remove-SPRoutingMachineInfo



For more details : Configure Request Manager in SharePoint Server 2013

Event : TechTalk on SharePoint

Event : TechTalk on SharePoint

The event details are as follows:-

Date: Tuesday 11th February, 2014
Time: 05:00 PM till 07:00 PM

Microsoft Innovation Center,
1st Floor, Media Studies Department, Bahria University,
13 National Stadium Road, Karsaz, Karachi.

Event Agenda:

• What is SharePoint?
• Document Management System
• Internet Sites
• Search Engine
• Business Process Automation / Workflow
• Business Intelligence
• Build Apps on SharePoint
• Get Social using SharePoint
• SharePoint Integration
• Q & A

1896894_591812170912007_2127532743_n1920111_591812114245346_554359626_n 1901232_591812134245344_672241917_n 1901129_591812080912016_1589669891_n1797482_591812160912008_876568074_n 1655842_591812030912021_1389812939_n 1012272_591812104245347_1022690266_n 7791_591812037578687_39122268_n 1640_591812044245353_947476994_n

Branding Opportunities in SharePoint 2013

SharePoint 2013 offers several different ways to brand SharePoint 2013 site. The options for branding are yet again more versatile than in the previous versions. These options range from the relatively simple menu option Change the look and using Composed Looks to the more complex solution of generating custom master pages through Visual Studio or SharePoint Designer.

Branding Opportunities:

  • Composed Looks
  • Design Manager
  • Custom Branding Packages
  • Brand SharePoint Apps

Composed Looks
Composed looks are similar to themes in the way they change the look of a SharePoint site, they can be applied on a site by site basis and dissimilar to themes, they actually rock! A possible definition of the word “Composed” could be: “To make or create by putting together parts or elements”. I believe this fits with our use of this feature. A Composed Look is made up of:

  • Master Pages
  • CSS
  • Color palettes
  • Font palettes
  • Background image


What is Design Manager?

Design Manager is a new feature in SharePoint 2013 that puts some structure around management of branding and styling SharePoint sites and pages. This tool’s purpose is to give users a new and easy way to brand SharePoint. The goal was to allow designers to create the look and feel for a SharePoint site using the tools they are most comfortable with like Dreamweaver or Visual Studio.

If you’re starting from a publishing site, it’s pretty easy to access. You can just click the Settings menu item and the Design Manager is available.

Design Manager


Some useful links for branding options:

Creating A New Master Page In SharePoint 2013
Build and brand your website with this step-by-step guide to SharePoint web content management
SharePoint 2013 Real World Branding Part 4 – Creating, Selecting and testing the design

Best of luck!!!

Windows PowerShell Command Builder for SharePoint


The Windows PowerShell for SharePoint Command Builder enables IT pros and power users to visually assemble commands in the browser and then take those commands to their respective products.

The Windows PowerShell Command Builder for Microsoft SharePoint 2010, Microsoft SharePoint 2013, SharePoint Online, and Microsoft Office 365 is an HTML5 application that is designed to help IT professionals and power users learn how to use Windows PowerShell for administrative tasks.

Windows PowerShell Command Builder for SharePoint





For Details Click here…..

For additional information, see the Getting Started Guide.