SharePoint 2016 root site "/" "Sorry this site hasn't been shared with you" 

Scenario:
User get access denied or Sorry this site hasn't been shared with you when they try to browse SharePoint site e.g. https://Sarav.com without /pages/default.aspx.

Complete URL e.g. https://Sarav.com/pages/default.aspx works and the problem only happens when users hit a particular WFE. The problem is because of some of your IIS configurations for that particular web app gets corrupted.

Solution:

Run Powershell as admin on the WFE where the problem is type the following

$webApp = Get-SPWebApplication https://YourSharePointSiteURL.com/

$webApp.Provision()

This re-provisions the IIS site and fixes the issues, also works if you have accidentally deleted the IIS web site.

Hope it helps!

SharePoint Infopath Web Form : Multiple file attachments

Multi file attachment InfoPath

We can only store one file in one File Attachment on an InfoPath form; you cannot attach multiple files in the same File Attachment field.
To create a multi file attachment control in InfoPath, you can make use of a Repeating Table that has a File Attachment as one of its fields.
Perform the following steps to create a multi-file attachment in InfoPath:

1. Add a Repeating Table with 1 column to your InfoPath form template.
2. Go to the Data Source task pane and double-click the field under the repeating node for the Repeating Table.
3. Change the Data type to Picture or File Attachment (base 64) and click OK.
4. Right-click the field in the Repeating Table on the InfoPath form template, and select Change To, and then File Attachment from the context menu that appears.

Save and publish

Refresh Trusted Security Token Services Metadata feed - Failed (After deploying workflow manager)

After deploying workflow manager we have to run the Refresh Trusted Security Token Services Metadata feed job else the Workflows we start will cancel out.

If you get an error (The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.) after running the above job , please follow the steps below...

 Exporting Certificates to Client Machines (Workflow Manager 1.0)

If you want clients to be able to connect to a Workflow Manager management endpoint or Service Bus gateway to configure an auto generated SSL certificate, export the auto generated SSL certification authority (CA) and revocation list (CRL) to those clients. Use the following procedure:

1. On the machine where server is installed open the Workflow Manager PowerShell console and use Get-WFAutoGeneratedCA cmdlet to export the Certification Authority and Revocation list. If you do not provide file names, this cmdlet will export Certification Authority to AutoGeneratedCA.cer
2. Copy the file to the client machine.
3. On the client machine open an MMC window, and add the Certificates snap-in, pick the Computer Account and Local Computer options when asked.
4. In the MMC window, right click the Certificates\Trusted Root Certification Authorities, open All Tasks, and select Import. Select the AutoGeneratedCA.cer file and import it.

At this point you should be able to trust connections from that particular client. The CER format exports only the public key, not the private key.

Azure Pack Installation

Windows Azure Pack installation checklist

	Task	References
	Install Microsoft SQL Server for the management databases.	Microsoft SQL Server versions supported in a Windows Azure Pack deployment
	Install prerequisites for the Admin API on the AdminAPI machine.	Windows Azure Pack system requirements overview
	Install the Windows Azure Pack: Admin API on the WAPAdminAPI machine.	Install the Windows Azure Pack Service Management APIs
	Install prerequisites for Tenant API on the WAPTenantAPI machine.	Windows Azure Pack system requirements overview
	Install the Windows Azure Pack: Tenant API on the WAPTenantAPI machine.	Install the Windows Azure Pack Service Management APIs
	Install prerequisites for Tenant Public API on the WAPTenPubAPI machine.	Windows Azure Pack system requirements overview
	Install the Windows Azure Pack: Tenant Authentication Site on the WAPTenantAuth machine.	Install the Windows Azure Pack Service Management APIs
	Install prerequisites for the management portal for administrators on the WAPAdmin machine.	Windows Azure Pack system requirements overview
	Install the Windows Azure Pack: Admin Site on the WAPAdmin machine.	Install the Windows Azure Pack management portals
	Install prerequisites for the management portal for tenants on the WAPTenant machine.	Windows Azure Pack system requirements overview
	Install the Windows Azure Pack: Tenant Site on the WAPTenant machine.	Install the Windows Azure Pack management portals
	If you do not use Active Directory Federation Services (AD FS), follow the next two steps:
	SUBSTEP: Install prerequisites for Admin Authentication Site on the WAPAdminAuth machine.	Windows Azure Pack system requirements overview
	SUBSTEP: Install the Windows Azure Pack: Admin Authentication Site on the WAPAdminAuth machine.	Install the authentication sites
	If you use AD FS, configure the trust settings for AD FS and the management portals.	Configure Active Directory Federation Services for Windows Azure Pack
	If you want to add more cloud services, follow the steps below:
	Deploy Automation service.	Deploy Service Management Automation
	Deploy Windows Azure Pack: Web Services.	Deploy Windows Azure Pack: Web Sites
	Deploy Virtual Machine services.	Provision Virtual Machine Clouds
	Deploy Service Bus service.	Integrate Service Bus into Windows Azure Pack
	Add SQL and MySQL providers to Windows Azure Pack.	Using SQL Server or MySQL with Windows Azure Pack
	Validate the Windows Azure Pack deployment by using the Best Practices Analyzer for Windows Azure Pack.	Test your deployment
	Create plans.	Administer Plans and Add-ons

The option for the SharePoint 2013 Workflow platform is not available in sharepoint designer - After installing workflow manager 1.0 correctly

After installing workflow manager 1.0 correctly- if you still see the error in SharePoint designer saying the option is not available before doing anything check the service connection...

Whenever a new workflow service application proxy is created (for that matter any new service application) in SP2013, by default it will not be associated (service connection) with any web application. Go to Central admin site->Manage web applications page -> Select the web app which was registered earlier during configuration and check " workflow service application proxy" and click OK

Hope it helps to someone banging his head to make workflow manager work in SharePoint 2013

SharePoint 2013 Ports

List of ports used by SharePoint 2013 and its related services.

Protocol	Port	Usage	Comment
TCP	80	http	Client to SharePoint web server traffic (SharePoint – Office Web Apps communication)
TCP	443	https/ssl	Encrypted client to SharePoint web server traffic (Encrypted SharePoint – Office Web Apps communication)
TCP	1433	SQL Server default communication port.	May be configured to use custom port for increased security
UDP	1434	SQL Server default port used to establish connection	May be configured to use custom port for increased security
TCP	445	SQL Server using named pipes	When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP port 445
TCP	25	SMTP for e-mail integration	Cannot be configured
TCP	16500-16519	Ports used by the search index component	Intra-farm only Inbound rule Added to Windows firewall by SharePoint
TCP	22233-22236	Ports required for the AppFabric Caching Service	Distributed Cache…
TCP	808	Windows Communication Foundation communication	WCF
TCP	32843	Communication between Web servers and service applications	http (default) To use custom port, see references section Inbound rule Added to Windows firewall by SharePoint
TCP	32844	Communication between Web servers and service applications	https Inbound rule Added to Windows firewall by SharePoint
TCP	32845	net.tcp binding: TCP 32845 (only if a third party has implemented this option for a service application)	Custom Service Applications Inbound rule Added to Windows firewall by SharePoint
TCP	32846	Microsoft SharePoint Foundation User Code Service (for sandbox solutions)	Inbound on all Web Servers Inbound rule Added to Windows firewall by SharePoint Outbound on all Web and App servers with service enabled.
TCP	5725	User Profile Synchronization Service(FIM)	Synchronizing profiles between SharePoint 2013 and Active Directory Domain Services (AD DS) on the server that runs the Forefront Identity Management agent
TCP + UDP	389	User Profile Synchronization Service(FIM)	LDAP Service
TCP + UDP	88	User Profile Synchronization Service(FIM)	Kerberos
TCP + UDP	53	User Profile Synchronization Service(FIM)	DNS
UDP	464	User Profile Service(FIM)	Kerberos change password
TCP	809	Office Web Apps	Intra-farm Office Web Apps communication.