I was facing a minor issue with an upgraded site from 2007 to 2010. Navigate Up button TOP level entry was pointing to a wrong entry. The screen shot below shows 2 masked entries. One entry was showing the right link, where the top level was pointing to the old 2007 site.
This is not the case, when you have issues with the whole Navigate Up button. For that you would remove “PlaceHolderTitleBreadcrumb” content place holder, this was much simpler than that.
To fix, Navigate to the Portal Site connection under Site Settings – Site Collection Administration (thanks to Samer – colleague who pointed me to the link). Change the settings on the page to “Do not connect to portal site”. That should take care of the issue. Simple step but handy solution.
Recently, I had to troubleshoot a custom .NET web application within SharePoint not loading as it was encountering the following error: ( the web site was deployed to a folder within _layouts)
Cannot create file when that file already exists. (Exception from HRESULT:0X800700B7)
It turns out the culprit was the entries in the web.config for the custom web application. There was some entries in the web.config that was conflicting with SharePoint web.config and the above error occurred.
Suggestion is to remove configsections and controls and try out. If you still encounter errors, try with minimal entries in the web.config such as customErrors, connection strings, app settings, and assemblies. That should fix the error.
My SharePoint 2010 Farm has 2 WFEs and 1 APP server. The APP server was hosting Service application and the index and crawl components split between web front ends.
I encountered the following error
catalog Main: failing to copy index files from crawl component 4 for <x> minutes. Access is denied
So, digging further did not result in finding any suitable fixes.
So, I created a new query component folder, mapped the new folder to the Query component and removed the old folder reference.
Navigate to Search Administration (Manage service applications – Select Search Service Application). Modify Topology – Pick the query component causing the issue and edit properties
Try the above approach and if still does not work, do an index reset (watch out… if you are indexing a lot of content… this may take a long time to index the content back again) along with a new folder mapping. I did not have to delete the Query component and re-create it.
Here is how to convert an existing web application configured with Classic Mode Authentication to Claims Based. This can be done using PowerShell.
Note: Once converted from classic to claims, you will not be able to revert the change.
Screen Shot showing web application in Classic Mode
Now, run the Powershell command:
You can see the web application is now converted to Claims Based Authentication:
I will be doing a session on FAST Search 2010 at Atlanta SharePoint Saturday event. Check it out:
My colleague David Pallmann has just released his book on Windows Azure – Volume I.
I was part of the review group for this book. Check it out.
Here is my webcast on SharePoint Application Lifecycle Management
Download the Recorded Webcast from Neudesic.com
Join me at Atlanta SharePoint UserGroup monthly meeting. The topic I will be presenting is SharePoint ALM (Application Lifecycle Management) Deep Dive.
More Information here.
See you there!
Join me on Feb 9th, 2011 at 1:00 pm for K2 Roadshow session on Tips & Tricks with SharePoint Deployment & Governance. I will be representing Neudesic.
Click here to register.
Update: 2/21/2011 — Thanks to the attendees for voting me to the Top 10 speakers list. I enjoyed the event as well.
SharePoint 2010 Application Lifecycle Management (ALM)
I am back at Philly for bi-annual SharePoint Saturday event on 2/5/2011 at Devry University, Fort Washington, PA. Over 325 people have registered and the registration will close at 400.
My topic will be on SharePoint 2010 ALM:
SharePoint 2010, VS 2010 & TFS 2010 ALM tools help developers to improve code quality and metrics. ALM stands for Application Lifecycle Management – It is management & co-ordination of all software development lifecycle activities like requirements gathering, requirements modeling, code development, build process, testing activities and implementation events. Developers now can use all the ALM features of TFS & VS to develop quality SharePoint solutions . ALM is no longer just confined to .NET developers but to the SharePoint development as well. This session will demo TFS integration with SharePoint & Visual Studio and how developers can utilize ALM tools to deliver better quality conscious products to customers.
See you at SharePoint Saturday!