Share Technology Points

Hi Guys, I was facing a very strange issue since two three days. I just wasted lot of my time while solving it. After experiencing SharePoint 2013 service architecture, I was under the impression that MS have modified SharePoint this time that one will never face any issue while configuring the service applications. But I was wrong, I am talking about the Search service application here. If you are lucky then it may be the case that you will not see this issue but I wasn't actually explored the reason behind the issue. Issue Description: “Unable to retrieve topology component health states. This may be because the admin component is not up and running.” The default content source “Local SharePoint Sites” is inconsistent. It doesn’t always appear after creation of Search, sometimes with start addresses of existing web apps listed already, other times not. Starting a full crawl results in stuck in ‘starting’.                        Tried Solutions:  Installed all hotfixes by ...

Hi Guys, Before starting let me clear that, when part or all of your data center exists physically on your campus(es), then you have an on-premises (not “on premise”) solution. Maintaining a SharePoint farm on-premises is startlingly complex and expensive. SharePoint is a Windows Server-based, multi-tier ASP.NET Web application that uses SQL Server for its data tier and relies heavily upon Web standards and the .NET Framework. When you add in other, related Microsoft servers such as Exchange and Lync, then between physical hardware, electricity, licensing, and support costs, you are facing a huge investment of time, money, and effort. Microsoft gives us SharePoint Online and Office 365 as a cloud-based alternative to deploying and maintaining an on-premises farm. Specifically, the Office 365 product is a particular type of cloud computing known as software as a service, or SaaS. SharePoint online is one of product included in MS online service solutions and is part of Office 365. Micro...

Hi, Developing Metadata fields is always a complicated case of the developers. My previous posts( Add Metadata Taxonomy Custom Field using Visual Studio ) I explained how we can create metadata site columns. In this  post, I will target Office 365/SP online users who can only use sandbox solutions to update/create metadata fields. Reason why treditional solutions does not with Office 365 In practical scenario, Metadata service details like SSPID, Default term store etc keep on changing. I notice that the name of Metadata service of SharePoint Online keeps on updating after some updates. We all know that code  in sandboxed solutions is being deprecated by Microsoft. But even if we were happy to use sandboxed code - in Office 365/SharePoint Online, we cannot use the  Microsoft.SharePoint.Taxonomy  namespace in server-side code anyway – the net result is that we are unable to “finish the job” in this way to ensure the field is correctly bound to the Term Store. This is a problem! Even wor...

Hi, In my previous blog( Add Metadata Taxonomy Custom Field using Visual Studio ), I have explained how we can add custom metadata taxonomy custom field. In the feature code we have to write code to bind the field with the taxonomy term set. It can be one business requirement to get the taxonomy session for the current site. We all know there is a dll provided by Microsoft named "Microsoft.SharePoint.Taxonomy" found under ISAP folder. Using this Dll we can get access to current metadata service and default metadata term store by using the following code: var session = new TaxonomySession(<object of SPSite>); var termStore = session.DefaultSiteCollectionTermStore; I just used this code but unfortunately this object returns me null :). Then after spending few hours I found that there is a configuration which allow us to behave term store as default term store. Follow the below steps to resolve this: 1) Navigate to "Central Administrator > Application Management...

Hi, Custom Taxonomy Field creation is very common requirement while working with the different clients. In this post I will explain how we can create a custom metadata type column. Once metadata field is added as site column, it can easily be added as custom list column or field to any of the content type. Step 1: Create a fresh project of type "SharePoint 2013 Project". After providing basic properties of project like Farm/Sandbox solution and SharePoint site Url project is ready to add field into the site. Step 2:  Now its optional to create new folder "Site Columns" as per the project coding standards. But in case you are adding multiple custom columns then I recommend to add a new folder as I did. Step 3 : Next, Just hit right click on the project/folder and say "Add > New Item" from the menu options. Then select "Site Column" from the item list. Give any relevant name to your column. Step 4 : After you hit "Add", a new module...

Hi Guys, Recently, got chance to look out of SharePoint server versions towards SharePoint Online with office 365. I should say our Microsoft developers brothers are thinking a lot to save our time. What else a developer want if he come to know that he just need to open a browser and develop code there like w3school. Wooaa... !! I just found a app called "NAPA" sounds similar to like "NASA" but really works like boon for app developers. While working on SP server, you might have noticed one site template "Developer Site", Well I never noticed that it such a fool. But this site allows you to create the online apps using the "NAPA" tool. In order to install "NAPA" first followed this blog but could not worked for me :-( . Then I did google and found another way to make it work. Basically, we have to activate  the "Developer Feature" which is a site collection level feature and does have option to activate it from UI. If you are ...

Hi Guys, I was doing the migration from SP 2010 to SP 2013. The purpose of this post is to discuss how we can easily create classic mode web application in SP 2013. You must be knowing that we are having option to select the authentication mode "Claims based" or "Classic Mode". But unfortunately in SP 2013 this option is removed. You can only configure claims-based authentication when you manage Web applications in the Central Administration page. This is because claims-based authentication is the default and preferred method of user authentication, and is required to take advantage of server-to-server authentication and app authentication. If you would like to create a Web application with classic mode authentication, you can do this using Windows PowerShell cmdlets. The use of classic mode authentication, also known as Windows classic authentication, is discouraged in SharePoint 2013 and you can only create or configure web applications for classic mode authentic...