Michael Pertek and I have written a professional article Hart am Datenlimit - Externe Speicherung grosser Datenmengen in SharePoint 2007 for a German database magazine called database pro (sorry no English translation available). This article is based on a white paper I have written with Michael in September 2008. The first link includes the white paper and the last two links contain the English translation. [More]

This problem was another result because of a snapshot taken at the virtualized SQL Server. After stepping back to a state in the past using the snapshot I got the error The object SPPersistedFile Name=SOLUTIONNAME-SOMEGUID.bak Parent=SPSolutionLanguagePack Name=0 has been deleted by another user since it was last fetched and after that the COM exception. [More]

Using SharePoint 2007 in a virtualized environment can bring up new or different problems compared to a physical machine. With Hyper-V or VMware ESX you can take a snapshots of your SharePoint 2007 environment including SQL Server. Jumping back to a state in the past can be helpful if something is corrupted. Jumping back can also corrupt your SharePoint farm. In this case a snapshot of the SQL Server was taken and after some time used to go back to a state in the past resulting in the error. [More]

Sometimes things don’t work from one moment to the other if you do MOSS 2007 / WCMS development. Usually it’s due to a mistake I made and usually finding it is difficult since some error message aren’t really useful: This time I got a “List does not exist” error together with a COMException. [More]

Here we go again: Playing around with SharePoint 2007 xml to create site definitions, site columns or content types isn’t always easy and fun. You have to be careful because forgetting something will result in an error message which may be unhelpful. In this case I got a helpful error message after forgetting an attribute in my module. [More]

Writing tons of xml in order to create SharePoint 2007 site columns and getting and error “The given key was not present in the dictionary.” after deployment isn’t the thing I want to get at the end of the day. After doing some review I found the error which can easily be missed. [More]