“Your search encountered an error. If the problem persists, contact the portal site administrator.” Great. That would be me 🙂 I wanted to manage some properties within the User Profile Service Application. But an error message kept me from doing so. A quick look for the running SharePoint services from the Central Administration looked ok. The UPS services is up and running. Then it hit me. Even if SharePoint tells you everything is OK, it might not be the case.

With pleasure I read multiple feeds about the availability of SharePoint 2013 via MSDN 🙂 I am anxious to install that version, and see what has changed compared to the Preview. René

One of the reasons I choose Feedburner for my feed was a non-changing URL for my readers. Unfortunately Google is closing Feedburner services as posted on https://developers.google.com/feedburner/ So you’ll have to change the RSS-feed URL from http://feeds.feedburner.com/ReneHezser to http://www.hezser.dehttp://www.hezser.de/blog/files/rss.xml

A while ago, I wrote an article about performing operations parallel with SharePoint 2010 (.NET 3.5). –> Execute code in multiple threads (even with SharePoint) Since I am not the only guy with this kind of “problems”, others are writing about SharePoint and .NET. Especially .NET 4.5 and SharePoint 2013. Stephane Eyskens hat posted a nice 6-post series about .NET within SharePoint 2013. Tuples Lazy Loading Sorted Sets Parallel.ForEach .

SharePoint has a new logo. Looks good 🙂 Source: http://sharepoint.microsoft.com

This is one of the posts which shall remind me about something. And may help others as well. Coding against the User “Profile Service Application requires Connection Permissions for the executing user account! From the beginning. I wrote a console application which leverages the User Profile Store. Every time I created a new instance of the UserProfileConfigManager class, an exception was thrown: Object reference not set to an instance of an object

SharePoint 2013 immediately redirects you to an application page start.aspx when you call a website. If you’ve ever wondered why, keep on reading… The pictures will also look familiar to you. So what happened? Why the start.aspx? The start.aspx inherits Microsoft.SharePoint.ApplicationPages.MDSStartPage. That page simply looks, if the SPContext.Current.Site.CompatibilityLevel is above 14. If not, it’ll redirect to web.Url. That is the behavior, we know from previous versions of SharePoint. Additionally it adds some caching information to the Response, and loads a JavaScript called… start.

If you have installed SharePoint on your workstation, you might want to start the services only in case of active development. Otherwise the services consume memory and other resources. The PowerShell script in this post will allow you to easily start and stop all required services for a local SharePoint Installation. It will detect if you’ve installed SharePoint 2007/WSS, SharePoint 2010 or SharePoint 2013. Just copy the code below to a file, name it StartStopSharePoint.

Soeben ist ein neues Community-Portal online gegangen. Auf diesem Portal bin auch ich als Autor für Artikel vertreten. Mehr Werbung möchte ich jetzt erst einmal nicht machen 🙂 Schaut es euch einfach mal an. www.brandmysharepoint.de Was erwartet Euch auf diesem Portal? Wir starten zunächst mit zwei Rubriken: Artikel und Shots. Die Artikel befassen sich mit allen möglichen Themen rund um das Design. Dabei werden nicht nur die klassischen (Web-)Designer angesprochen, sondern auch Entwickler, IT-Pros oder einfach nur „SharePoint-Interessierte“.

I won’t go into the arguments for using a caching mechanism or not. This post is simply an example for an easy way to cache data. So if you want to store some object in the cache, you can do so very easy. var localizedString = Caching.EnsureObject(resourceName, () => GetOperation(parameter)); As you can see, it really doesn’t matter what type of object the cache will store. class Caching { private static readonly TimeSpan Duration = new TimeSpan(1, , ); /// <summary> /// return cached value, or add and return from cache /// </summary> /// <typeparam name="