During an encounter with a custom list template I got stumped by the continuous appearance of a COMException conveniently just called 0x80004005. I hate those guys.
Now, I have done a few custom SharePoint ListTemplate deployments before, in fact I often write these more or less bottom up in a shorter amount of time than it takes to copy an existing list template and make it behave as I want. The problem today, however, is that I am a bit exhausted, and thus seems to overlook simple things. So, after spending an hour or so writing a fairly simple document library: Boom.
One thing is writing the damn thing while tired, a completely different matter is debugging SharePoint solutions or features while tired. Suddenly the list template that took an hour to make takes an hour to debug.
After reading the logfiles, and of course this was a project for a Norwegian customer, so Googling error messages
The culprit? Lack of BaseType. Yeah, I know. Adding BaseType="1" to the ListTemplate element resolved the whole thing. The devil is in the details. And I am a fool.
My advice: Keep your copy of the SDK documentation open. I know people say the documentation are bad, but if nothing else you can get some helpful hints when it comes to the required and optional attributes.
Found this article valuable? Want to show your appreciation? Here are some options:
a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.
b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.
c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!