SharePoint Excellence

Problem : I am starting to debug SharePoint Solution on a server but found below error "An error occurred while trying to load some required components. Please ensure that the following prerequisite components are installed: Microsoft Web Developer Tools Microsoft Exchange Web Services." I have installed Visual Studio Professional 2012 on my server. Resolution Please follow the below steps to resolve this issue 1.       Go to Control Panel > Uninstall a program 2.       Select Microsoft Office Developer Tools for Visual Studio 2012 - Preview 2 - ENU 3.       Click on Change to uninstall it. The setup program should launch. 4.       Click on Uninstall to remove the Office Developer Tools. 5.       Download the Office Developer Tools using Web Platform Installer link. This Web Platform Installer should install the Of...

Now a day I am working on SharePoint 2013 Search and found a common issue reported by many of users i.e. Result count is inconsistent, see screenshot       The result count is different on each page while use pagination on search result page. Solution: SharePoint 2013 introduces a new technique for presenting search results: Display Templates . Search result is coming via “ Display template ”; this is a property of Search Result web part. In 2013 the new rendering techniques have several distinct advantages. Display templates are HTML and JavaScript rather than XSL Display templates are configured for the Site and Site Collection rather than for a Web part Display templates are applied with rules and logic Display templates are applied to individual result items, not the entire result set Display Templates are used for Results of all kinds, search results, content by search results...

When creating a new web application in SharePoint, you choose the physical location of where the IIS website will be created. Once the application is born, however, there is no longer an option to change this path in Central Administration. You can very easily change it in IIS (by going to your website’s Properties -> Home Directory -> Local Path), but once this is done, you will start running into trouble, as solution deployments will point to the web.config file at the old location. Three quick steps need taken to successfully move the web application: Copy the current directory’s contents into your new directory Make the change to the website’s local path in IIS (as described above) Update the SharePoint web application to point to the new path Note: If you have multiple servers in your farm, steps 1 and 2 will need made on each web server, but step 3 will only need done once. The third step can be done without having to extend the site. Here are a couple options....

Issue: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component ‘GUID′ in search application ‘Search Service Application’ is in a good state and try again. Cause: search admin timer job was disabled Analysis : Execute below PS command in SharePoint Management Shell to verification of cause of this issue Get-SPTimerJob job-application-server-admin-service | fl It will return IsDisabled : True (See below screen)   Solution : Execute below PS command in SharePoint Management Shell to fix this issue Enable-SPTimerJob job-application-server-admin-service Now it will return IsDisables: False To verify it execute command Get-SPTimerJob job-application-server-admin-service | fl Restart SharePoint Timer Service IISRESET My TechNet article    

Now a days, I am working on migration from SharePoint 2007 to SharePoint 2013. We have choose the content db approach to migrate our portal, firstly we have to migrate our content from SharePoint 2007 to SharePoint 2010 and then SharePoint 2010 to SharePoint 2013. Right now I am working on migrate my site from SharePoint 2007 to SharePoint 2010, I'll share the migration steps of SharePoint My Site 2010 to SharePoint My Site 2013 migration in next few days.  I am sharing the steps that need to perform for my site migration 1.     Take a backup of the MOSS 2007 SSP and the My Site databases through SQL Server. 2.     Restore the SSP database as ‘Profile DB’ and the My Site Content database as ‘WSS_Content_MySites’ in the SharePoint 2010 -SQL Server instance. 3.     Create a Web Application through SharePoint 2010 Central Administration to host My Site. 4.     Attach and upgrade the restored 2007 My Sites data...

In our recent project we were facing an issue with page layouts, so we need to check our WSP solution on server. In the Central Administration screen, a link is not available for you to download the WSP solution. We can extract the WSP from farm with custom code but I have used below 3 lines of PowerShell code to achieve my goal $spfarm = Get-SPFarm $wspfile = $spfarm.Solutions.Item("wspfilename.wsp").SolutionFile $wspfile.SaveAs("d:\extract\wspfilename.wsp") Make sure, you would be a member of Farm Administrators group and have permission to the configuration database.

What is it? Microsoft has re-invented how third-party / custom-developed software can plug into SharePoint. Web part still remains; however Microsoft is pushing the new SharePoint App Model instead of web part. Apps are self-contained pieces of functionality that extends the capabilities of a SharePoint website. Apps will be executed outside the SharePoint Server, either in the on-premise server or in the Cloud based server.  This makes Apps easier for installation & clean-up.  A farm solution in SharePoint requires full trust whereas sandbox solutions are very restricted. In order to bridge this gap Microsoft has come up with this App model. Sandboxed Solutions are deprecated and new custom solutions should be provided through Apps. A new concept of App Store and App catalogue has been introduced for global and local app hosting respectively. Microsoft’s Motivation behind App Model SharePoint 2007 and SharePoint 2010 have gained large-scale adoption worldwi...