I’ve had the error message “The SharePoint item being crawled returned an error when requesting data from the web service. (0x80042616)” when I tried to crawl a SharePoint WebApplication. The search crawler account had access to a site by a WebApplication policy. But somehow, that didn’t work.
After removing and re-adding the account policy on the WebApplication, the search crawled my content again.
Hopefully this post can help others as well.
Since SharePoint 2010 uses .NET 3.5, you can not use the fancy new functions from .NET 4 🙂
So if we need e.g. multi-threaded execution of code, we’ll need to write the code ourselves. But, as you can see, this really isn’t so hard. The basic idea behind this solution of executing code parallel in threads, is that you have an IEnumerable of some kind. This can be a List, or any other IEnumerable.
In 2008 I’ve released a Web Part, which enables your users to access files on your fileservers through SharePoint. Original post. This Web Part has been downloaded many times. With this new version, I’ve tried to deal with the most asked questions (like Kerberos), which will make the Web Part easier to use. Naturally new features have been implemented, to get you to upgrade to the new version.
With this release, the Web Part requires SharePoint Foundation / Server 2010.
I’ve made a small update to the My Alerts Webpart.
The update improves SharePoint 2010 support.
A long time ago, I posted a program which will hit all your sites. With parameters you can specify to hit all sites within a sitecollection.
This program has been updated. You can not omit a start Url, and specify “Farm” as parameter. This way, all sites in all sitecollections in all webapplications in all… 🙂 will be warmed up.
The warmup will use a HttpRequest to query all homepages.
One of the first things I used to tell guys new to SharePoint development is: Never ever name the folder of your feature “Feature1”. If you create a solution with WSPBuilder, or did some time ago with VS 2008, you have to rename the folders immediately!
This is how a typical SharePoint project looks like, if you create features. I guess most of us have used the mighty WSPBuilder ( http://wspbuilder.
To be able to use the ISE for SharePoint, you can configure it to load the SharePoint cmdlets automatically.
Scot Hillier wrote a great article about it. Read “Setting up PowerShell ISE for SharePoint 2010”.
If you only want to use the SharePoint cmdlets once, you can register them with this two lines:
If ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null ) { Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell }
“v5.master” is a simple HTML5 master page designed for SharePoint 2010. It makes good use of the amazing new features of both HTML5 and CSS3, including CSS3 media queries. The master page is extremely simplistic in nature, and is truly meant to serve as a framework for building your own SharePoint 2010 customizations.
Here comes some good news for SharePoint and HTML 5. If you want to build your masterpage for HTML 5, you can: http://kyleschaeffer.
Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): October 13, 2011
Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): October 13, 2011
Here is another “watch out” for using the SharePoint object model.
SPUrlUtility.CombineUrl(web.Url, string.Empty) The line above will throw an exception, as CombinUrl doesn’t like empty strings. 🙂
