Skip to main content

Posts

Host Named Site Collection

A host-named site collection allows you to address a site collection with a unique DNS name, such as “ http://collection1.com ” .  Typically you will create a SharePoint web application, and it contains many path-based site collections that share the same host name (DNS name).  For example, collection1 has a site collection at “ http://mywebapp.com/sites/collection1 ” , and collection2 has a site collection at “ http:// mywebapp.com/sites/collection2 ”.  These are referred to as path-based site collections, and is the recommendation for most corporate scenarios.  Host named site collections enable you to assign a unique DNS name to site collections.  For example, you can address them as http://collection1 .com and http://collection2 .com , which enables hosters to scale to many customers. SharePoint makes the decision on how to map the host name to the site collection when the SPSite object is constructed.  It internally uses the SPWebApplication ob...

Host Named Web Application

Normally when you create a web application in SharePoint its Url is: “ http://<Server Name>:Port” or “ https://<Server Name>:Port ”. We can also create a web application that contains a URL that is not of the above format, instead it could be “ http://mywebapp.sharepoint.com ” or “ https://mywebapp.sharepoint.com ”. In order to create, host named web application following steps is needed to be followed. 1.       We need to create a host name in the DNS. The host name will be the url, the site. In my case my host name will be “mywebapp” . 2.       You need to login to your Active Directory server to create new host entry in DNS. 3.       Create DNS entries 4.       Let’s go to the DNS server and create a new A Host with the   “mywebapp.sharepoint.com” FQDN and pointing to the web front end.   5.     ...

SharePoint Server not redirecting to default page (Needs Full url to open site)

Our SharePoint 2013 Enterprise server all of a sudden stopped redirecting to the actual .aspx pages of the site when we have navigated to just the server name or folder names. When I go to “ http: //myservername: port/sitepages/home.aspx” the page appears. If I go to “ http: //myservername: port/ ” the page does not redirect, and instead shows a 404 error in Internet Explorer and shows a blank page in FireFox and Chrome. Some googling led me to this answer , which worked for me, but I realized there really wasn’t good documentation that could help me in solving this. Finally, I found a solution that worked for me. There are some deals that are added to IIS few of those are related to SharePoint and few related to.Net. I am not sure about the reason why SharePoint DLL’s are removed from there but adding those DLL’s back resolves this issue. Following are the steps that are to be followed to resolve the issue: 1.         ...

SharePoint Content Deployment Step by Step

Step 1: Create a source site collection First you will need a site to serve as the source for the content deployment job. So let’s create the source site collection first. 1. On the SharePoint Central Administration Web site, in the Application Management section, click Create site collections. Step 2: Create a new Web application   As I have explained in my previous post that you cannot copy your source site into a destination site, which resides in the same content database as source, you must first either create a new Web application to hold the destination site or create a new content database in the current web application. To create a new web application see the steps below. 1. On the Central Administration Web site, in the Application Management section, click Manage web applications. 2. On the Web Applications Management page, click New. 3. In the IIS Web Site section, in the Port box, type 8888. 4. In the Application Pool section, in the Application po...

SPGridView control Example

We normally use asp.net gridview control as substitute to SharePoint gridview Control. Compare to asp.net gridview control SharePoint gridview provides rich functionality. Below two are the reasons that I feel to use SPGridView control instead of asp.net gridview control. 1.        SPGridView is inherit from GridView, so it will have features of GridView and also some special features that suite for SharePoint environment, so for a SharePoint web part, I suggest to use SPGridView. 2.        Also SPGridview control supports built-in SharePoint cascading style sheets, menus, sorting in SharePoint manner. In this blog I will try to show, 1.        Create SPGridView. 2.        Bind data source to SPGridView. 3.        Apply paging to SPGridView. 4.        Allow Filtering. ...