Step by Step: Connect SharePoint Libraries to Outlook

This post is applicable to SharePoint 2013, SharePoint 2016

In this step by step module, we are going to see how to connect a SharePoint library to Outlook. Yes to Outlook, so that you can have all your documents in your outlook to easily edit and update back or leave it without updating even. This will be very useful feature if we are working on too many documents and we are in a position to store it all in the project’s team site every now and then.

Step 1: Open the team site where you had your documents stored and traverse to the document library. Click on Library tab, and click on Connect to Outlook. There will be a popup to confirm if you want to open the application. Just click on launch application and it will open up the Outlook.


Step 2: In Outlook, there will be a popup to check if the SharePoint list can be added to your outlook.


If we click on Advanced, we can have some extra options to configure as below, can opt to have this document library in all the places where your email account is configured and on the update limit. Click ok and Click Yes on the above popup. The List will be synchronized in a jiffy.


Step 3: In your outlook, you can see a new entry as SharePoint lists and all the documents synchronized and available in your outlook. From here, the documents can be edited and saved and stored within outlook.


We will see on how to edit, and save it back to SharePoint in the next step by step post.

Posted in My Own Posts, SharePoint 2013, SharePoint 2016, Step by Step | Tagged , , | Leave a comment

May Patches for SharePoint 2013 released!

Every month (from 10th to 16th) a new patch (You can visit technet page to know more on the patches too) will be released which will have all the previous month’s patches included within. Let us see a bit about what May month patch releases contains and also on some tips to decide whether those patches are needed or not for your environment.

For SharePoint Server 2013:


This Cumulative update contains the below list of KBs.

This update can be patched all together or we can also choose which one is more needed and patch that particular update also. But it is always advisable to update all at one go to avoid any major issues.

  1. The servers must be restarted after the patches are applied.
  2. One month’s patch will take nearly 6 to 7 hours for a server. (This is purely from our experience for the past one year of patching)
  3. The prerequisite of this update is SP1 of SharePoint 2013.
  4. It is always good to wait for service packs if the released monthly fixes are not applicable or not needed for your environment.
  5. Security fixes are always prioritized but not all might be suitable for your environment.

The details for each and every update is as below:


Fixes the following issues:

  • Property demotion doesn’t work for Word documents that contain ink objects. This update also fixes property demotion that corrupts data of Office Mix add-in for PowerPoint.
  • If forms authentication is enabled in a nondefault (extended) zone, users can’t get permissions to edit Office Web Apps Server (WAC) documents that are granted through a group membership.
  • When you spell check an incorrect word that’s split across multiple formatting tags, you may receive a generic error message about this word, or the content format is changed.
  • When you press the Tab key on the Add Task page, the visual focus appears in the Task Name text box instead of moving to the first new form field of the %Complete text box.
  • A screen reader doesn’t announce specific column headers in the Tables mode.
  • A screen reader doesn’t announce check boxes in the Tables mode.
  • A screen reader doesn’t read app name for the ellipsis on the Site Contents page.
  • Some elements on the Add an App page aren’t marked up for accessibility.
  • When you focus a check box in the grid on the Resource Center page, nothing is read by the screen reader because the column doesn’t have a header.
  • You can’t use keyboard to expand or collapse groupings in the grid on the Resource Center page.
  • If the Notes field of a task contains special characters in a project detail page, the project detail page isn’t displayed but keeps loading.

If the above mentioned issues are not there in your environment, then this fix is “Not Needed”. But at the same time, Not needed does not mean it should not be applied. It can be always applied as the updates will affect only if those components are installed and used in your servers.


Fixes the following issues:

  • Translates the following error message in Norwegian to make sure that the meaning is accurate:

Sorry, this site hasn’t been shared with you.

The above talks about Norwegian language component and if you do not use this, again this fix is also “Not Needed”.
  • Updates the Danish proofing tools.
  • Improves taxonomy change tracking performance, and the term store won’t be offline even if many changes are made.
  • Translates the SharePoint Server 2016 hybrid search and changes user experience in multiple languages to make sure that the meaning is accurate.
  • Fixes the following issues:
    • When you use Managed Metadata Navigation and filtering, you experience the following two issues:
      • The halo around the active item in the menu is truncated.
      • The separator of the navigation bar is displayed with inconsistent width if you resize or refresh the window.
    • A screen reader detects tabs in the Term Store Management Tool as a single H3 header incorrectly.
    • The Content Query Web Part doesn’t load the correct entries when a user field is queried with a not-equal-to filter.
    • When you create a list item with a taxonomy field while using JAWS, the suggestions for the taxonomy field are not accessible.
    • When you spell check an incorrect word that’s split across multiple formatting tags, you may receive a generic error message about this word or the content format is changed.
    • Custom managed property that contains special characters (such as an apostrophe) isn’t highlighted when it’s searched.
    • Index component crashes randomly.
    • When you try to insert links from SharePoint to upload files to sites, unexpected error occurs if the site names have non-ASCII characters.
    • When you drop RTF email messages from Outlook clients to a document library, the email bodies aren’t indexed and nor searchable. This update improves the extraction of RTF email body text from .msg files.
    • You can’t change the regional settings and receive the following error message:
      Server Error in ‘/’ Application.

      This issue occurs after you install February 9, 2016, update for SharePoint Server 2013 (KB3114719).

    • Assume that you use a querystring URL parameter to pass values at the query time. When a user selects a specific taxonomy term, using the term GUID to search, the search doesn’t work.

These days most of the fixes are about language tools. The above is also updating some Danish proofing tools. But it also contains some of the basic components updates like Content Query web part which is quite commonly used. This fixes might be needed if you are facing the issue mentioned, or even without any issues, if the updates are going to help the components which we are using to work much better, no harm updating this. So I would term this as “Needed” but not a “Must”

There is one more fix for Feb update and if you had updated your servers to Feb patch, it is good to have this patch to rectify the other issues.


Fixes the following issue:

After you switch views in an InfoPath form in Internet Explorer 11, the People Picker control displays the following error message:

Still using InfoPath forms, then this might be “Needed” or please put it under “Not Needed”.

Fixes the following issue:

If the conditional formatting rule is set to Show Icon Only and users have Excel Services Viewers permissions, Excel Services doesn’t display conditional formatting icons.
Not a show stopper issue though but no harm updating this patch as it does solve something in Excel services. Again if you are using Excel Services in your environment, this is “Needed”, else I would push this to “Not Needed” set.

Fixes the following issues:

  • Updates the Danish proofing tools.

Again Danish proofing tools, I would mark it as “Not Needed” as we do not use this language tool in our environment.

On an overall analysis, I would say this month’s release is not a must to patch. We should be able to wait for the next patch to be released as most of the parts that this CU contains are not used or not needed.

For SharePoint Foundation 2013:


Usually this CU will have some of the same updates that belongs to SharePoint server. If we patch the other release, we can ignore Foundation patches, but if your environment is only Foundation, then download and patch this set if you have decided to patch for this month.

Happy Patching up!

Posted in My Own Posts, Patches, SharePoint 2013 | Leave a comment

Step by Step – Creating a Web Application in SharePoint 2013

There are numerous requests on how to do things around in SharePoint from beginners. So wanted to start off with how to create a web application.

The hierarchy in SharePoint always goes like this:

Diagram of a site collection

(Image Credits to technet)

Web Application is the parent, Site Collection is the child, Sites are grand children. Lets see how to create a Web Application in SharePoint 2013.

  1. In the SharePoint installed server, Open the Central admin in administrator mode. Preferably in IE. 1
  2. Click on Application Management link on the left and on the opening page on the right, click on Manage web applications2
  3. And in the page that opens, click New on the top left menu. This will trigger to create a new Web Application.A popup window will be opened asking for the relevant information.3
  4. Once you click on the New, you will see a popup on the screen, which will ask for information on the Application. Change the port number and the name will auto change to fix in to the port. Then scroll down to update the content db’s name so that it is easily identifiable. It will go like WSS_Content, change it to WSS_Content_<portnumber> for example.45.png
  5. Scroll to the bottom and click OK. No need to change anything else if this is just for a testing process. We will see one by one, in this pop up in my future posts to understand it more. Once the process is initiated by clicking OK button, we will be able to see the below and after few minutes, the Web Application will be created and a success message with a “Create Site Collection” link will confirm on that part as well. 67
  6. The next step is to Create a Site Collection which will be shared in the next post.
Posted in My Own Posts, SharePoint 2013, Step by Step | Leave a comment

PowerShell Script to create Search Service Application

I have uploaded a detailed script with comments on how to create a Search Service Application (SSA) here. This script has variables hard coded, so please change it according to how your farm requires and use the script to create SSA effectively.

Hope this helps…

Posted in My Own Posts | Leave a comment

Experience as a Conference Speaker

Recently I got a wonderful opportunity to present in a PowerShell Conference Asia in Singapore. I would say it was my first time presenting outside of my organization and it was my best. The organizers were so supportive and the opportunity was given by Ravikanth Chaganthi, one of the world famous PowerShell MVP from India. He is a very good friend of mine and I have been following him for a long long time. I will always cherish the memories I gathered and experiences I gained through this conference and looking forward for many more to come.

My interview after the conference for PowerShell Magazine:

My Presentation files from the conference is here.

Posted in My Own Posts | Leave a comment

A failure was reported when trying to invoke a service application: EndpointFailure – Solution Step by Step

This is from my friend and posting it with his permission in my blog. He helped to solve this issue.. 🙂

Problem: We noticed this error messages in the web front end servers and identified that it was trying to reach some end point which was no longer available. And this error was mainly to search service.


Findings: We google’d and searched all over and found this link which confuses us more. They ask us to restart the services but some say it still did not make it work.

Solution Steps:

1. Go to event viewer on your server. Open this error message in a separate window and click on the link provided in the error message next to the wordings Affected Endpoint.

2. When the site is open, you should get an 503 error code as the service is unavailable. This means that this service is not created in IIS as a service application. What we can derive from this is, there was some search service application created and removed leaving behind traces of its id for the load balancer and that’s why it comes around searching for it.

3. To make this work, we need to go to IIS now. Open IIS and if you notice in the last on the list there will be an entry for SharePoint Web Services.


6. Click it open. Right click on it to create a new Application. We are now in the process of creating an end point.



7. For this, you need to copy the full id that you got in the url. Open the IE page again and copy the id that you have and keepsake it in a notepad.  It usually has a long word with numbers and letters. Add that id in the Alias area in the resulting window.


8. Physical path should be pointing to the Service.svc file in the system. It usually resides in the below folder. Just browse to it and for the Application pools, choose the one which is existing and used for search service.

“C:\Program Files\Microsoft Office Servers\15.0\WebServices\SearchService”

9. After entering all the information, click on Test Settings to check if the Authentication and Authorization is established. There should be two green tick marks. Click the close button.


10. The errors will not be there anymore and also you can check the URL which you checked earlier. It might look like this… meaning the endpoint is already established. And the problem is solved.




Posted in My Own Posts, SharePoint 2013, Step by Step | Tagged , , | 2 Comments