Kashif Nizam Qureshi

Leave a comment

Ports that are required for communication between servers – SharePoint

Following shows ports that are required for communication between servers (App, WFE & DB) for SharePoint.


Protocol Port Usage Comment Server Source IP(s) Destination IP(s)
TCP 80 HTTP Client to SharePoint web server traffic(SharePoint – Office Web Apps communication) SharePoint/Project Server (Web Front End)  


Client Machines





TCP 13737 HTTP Client to SharePoint web server traffic(SharePoint – Office Web Apps communication) SharePoint/Project Server (Web Front End)  

Client Machines





TCP 443 HTTPS/SSL Encrypted client to SharePoint web server traffic(Encrypted SharePoint – Office Web Apps communication) SharePoint/Project Server (Web Front End)  

Client machines





TCP 25 SMTP for e-mail integration Cannot be configured SMTP Server App (SMTP)
TCP 1433, 445 SQL Server using named pipes (445), SQL Server default communication port (1433). Client to Database server Database Server App DB

Leave a comment

Rename Custom Field name on PDP

Add the following script in Content Editor web part and place that web part in the end of the page (so main custom field is rendered before we can run our script).

<script type="text/javascript">
var ttnA = document.getElementsByTagName("div");

for (var j=0; j < ttnA.length; j++)


var orig = ttnA[j].innerHTML;

var stripped = orig.replace(/^\s*/, “”).replace(/\s*$/, “”);

if (stripped == “Owner”)


ttnA[j].innerHTML=”Project Manager”




Leave a comment

Uninstalling Workflow Manager 1.0

I followed the below step in order to delete Workflow Manager.

  • Leave the farm
    • Launch the Workflow Manager Configuration Wizard as administrator. Only this one option will be listed.
    • Copy the current configuration for later reference.
  • Uninstall Software
    • Workflow Manager 1.0
    • Workflow Manager 1.0 Client
    • Windows Fabric
    • Service Bus 1.0
  • Remove Databases
    • SbMessageContainer01
    • SbGateway
    • SbManagement
    • WFInstanceManagement
    • WFManagement
    • WFResourceManagement
  • Remove Service Application
    • Workflow Service Application Proxy
  • Remove application folder
    • Delete folder C:\Program Data\Windows Fabric
    • Delete folder C:\Program Files\Service Bus
    • Delete folder C:\Program Files\WIndows Fabric
    • Delete folder C:\Program Files\Workflow Manager

Note: If you’re recovering your workflow environment, your existing workflow won’t be deleted as they reside in content db. Once you setup Workflow Manager, check if you can see “SharePoint 2013 Workflow” and “Project Server 2013 Workflow” options in SharePoint Designer (I had to connect Workflow Application Service with the Web Application). Only then your existing workflow will show up under workflows in SPD.


Leave a comment

Error occurred in deployment step Activate Features

If deploying WSP using Visual Studio, you’ll end up with the following error.

Error occurred in deployment step ‘Activate Features’: Feature with Id ‘8a442317-1158-4994-b265-26499b2def57’ is not installed in this farm, and cannot be added to this scope.


Just manually created package and deploy


1 Comment

Manually Package SharePoint WSP using VS 2013

Package a WSP

Right click your project in the right column. Then click “Publish”.

A dialog will open, where you will get to choose where to place the resulting .wsp file. After clicking “Publish” your project will be build and then packaged in the selected location.

Make sure to have the Solution configuration set to Release when building for production.

Install the resulting WSP

Copy the .wsp to the server
Open an elevated SharePoint Management shell
Run Add-SPSolution -literalpath “C:\Linktowsp\wspname.wsp”
Run Install-SPSolution -identity “wspname.wsp” (here you might need to add -gacdeployment and -webapplication (or -allwebapplications) parameters depending on the content of your solution)


Get every new post delivered to your Inbox.