Tuesday, August 26, 2014

Download ULS Viewer for SharePoint 2013

Microsoft released ULS Viewer for SharePoint 2013. It is a very good tool for developers to get very good debugging information. This version has some very good fixes.

Here is the download link for ULS Viewer.

Download LInk

Direct Download Link.

Also check out:

- How to Get Current Logged in User and Display Name using SharePoint 2013 REST API?

- SharePoint 2013 Best Practices

- Differebce between Sandboxed solution and Farm Solution in SharePoint

Sunday, August 17, 2014

Difference between SharePoint-hosted, auto-hosted and Provider-hosted apps in SharePoint 2013

In this post we will discuss about the different hosting option for apps in SharePoint 2013. There are 3 hosting options SharePoint hosting, provider hosting and azure auto hosting.

Also check out:

- Change local debugging URL in visual studio 2012 for SharePoint 2013

- Different authentication types supported in SharePoint 2013

- Create an Application Page in SharePoint 2013 using Visual Studio 2012

SharePoint hosted app:

This type of App lives inside SharePoint. There is not code running on the server. All code must run in the client. This will have .aspx page but lots of JavaScript code that will implement the logic via client side script and service calls.

Auto-hosted and Provider-hosted apps comes under cloud hosted app. These apps hosted outside of SharePoint server. Since its hosted outside of SharePoint server you have the freedom to develop an app using any language like PHP, Java or .Net. You can write server side code here which will communicate with SharePoint server. Here it will use OAuth protocol for authentication mechanism.

Provided hosted app enables developer to define its own infrastructure which may be a dedicated server or may be a cloud server provided by providers like Amazon.

Azure auto hosted app is available with Office 365. It contains a web project and a sql project. If you are a Office 365 customer and selected the azure autohosted deployment option, then it automatically wired up al the integration to Azure.

Tuesday, August 5, 2014

The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob id threw an exception

The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 50134f59-757c-4d0e-a4c2-74b2620ab047) threw an exception. More information is included below.

Unexpected exception in FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache.
Also you can check out:

- Create Apps using Office 365 development tools Napa

- Change local debugging URL in visual studio 2012 for SharePoint 2013

- Different authentication types supported in SharePoint 2013

As the exception message suggested the SPDistributedCache may be down.
So to verify this you need to (re)start AppFabric Caching Service. To start the service:
1) Open the Run prompt then services.msc
2) Select AppFabric Caching Service.
3) Double click the service.
4) Set start up type to Automatic and then click on Start.
5) Then apply and then OK

Now the exception should not come.r

Saturday, August 2, 2014

Get team site list and library templates in SharePoint 2013 publishing site

In SharePoint 2013, team site has lots of templates compared to publishing site. But you will be able to get the templates by activating a site collection feature.

Also you can check:

- What happen when you press F5 in Visual Studio in SharePoint 2013

- SharePoint: Custom Media Video Player using JQuery

- Hide search box in home page in SharePoint 2013

Team sites app templates like Form Library, Picture Library, Document Library, Announcements, and lists like Calendar, Contacts, Custom List, Custom List with DataSheet View, Promoted Links, Discussion Board, External List, Issue Tracking List, Links, Project List, Survey, Tasks etc are not by default come in publishing site.

All the above templates comes by activating "Team collaboration lists" site collection feature. To activate the feature, Click on the Settings Icon from the right top and click on "Site Settings". The click on "Manage site features" from the Site Actions section. Then in the list of features page, Search for Team Collaboration Lists and click on Activate as shown in the fig below:

Create SharePoint 2013 Publishing Site

Here we will discuss how to create a SharePoint 2013 publishing site. Web Content Management (WCM) in SharePoint Server 2013 consists of features and functionality that you use to configure, customize, optimize, and publish site collections, sites, and pages. When we talk about publishing sites in SharePoint Server 2013, we are referring to sites that use one or more of these features to author and deploy branded artifacts, content, and configuration files to Internet, intranet, and extranet sites.

Also check out:

- Cross-site publishing in SharePoint Server 2013

- Shredded Storage new feature in SharePoint 2013

- New Embed Code in SharePoint 2013

Below are the steps to create SharePoint 2013 publishing site collection:

Open SharePoint 2013 Central Administration, then From the Application Management click on Create site collections.

This will open the Create Site Collection Page. In this page select the web application for which you want to create the site collection, Give a Title, Description and choose the URL.

In SharePoint 2013, you can chose the version like 2013 or 2010 and the from the Template Select Publishing category and then select Publishing Portal.

Then chose a Primary Site Collection Administrator and Secondary Site Collection Administrator as shown in the fig below.

Then click on OK. The publishing site will got created.

Check out this article to know more about Difference between Team site and Publishing site in SharePoint 2010.

HTTP Error 503. The service is unavailable error in SharePoint 2013

Here we will resolve SharePoint 2013 error HTTP Error 503. The service is unavailable. Recently I got the error while opening SharePoint 2013 Central Administration.

Also check out:

- Security Features in SharePoint Online

- Timeline web part in SharePoint 2013

- Creating Global List/Library Web Parts in SharePoint Server 2010

The error comes because the SharePoint Central Administration Application pool has been stopped.

For this go to IIS (go to Run -> inetmgr) and then click on Application Pool from the left side, this will open the list of application pools. From the list of application pools, select the appropriate application pool right click and Start.

Now the error should not come.

Twitter Delicious Facebook Digg Favorites More