ERROR: Exception from HRESULT: 0x81070201

By -
When using STSDEV to create a custom list as a feature, I had my solution deploying and my feature activating without a problem, but then when I created the list I got the error:

ERROR: Exception from HRESULT: 0x81070201

I looked through the log files and found that the Schema.xml file was not included in my feature manifest as an <ElementFile> element. Once I added this it fixed this error

Comments

Anonymous said…
Thanks for this Post! Saved me a lot of time :-)

Regards, Simon
September 5, 2008 at 2:56:00 AM PDT
Thiwanka Manamendra said…
Thanks bro. This true. It works.
November 23, 2008 at 7:33:00 PM PST
Anonymous said…
In feature.xml, I have defined ElementManifest Location="ListTemplate\SearchFile.xml" />
ElementManifests


But where do I declare schema.xml in ElementFile in element
December 24, 2008 at 5:21:00 PM PST
Anonymous said…
Thank Man. Your my Hero. I followed your instruction and got what I wanted Thank You once again
January 26, 2009 at 3:03:00 PM PST
Unknown said…
The <ElementFile> element is not required when you use a folder that contains the 'schema.xml' file and the folder has the same name as the <ListTemplate> element's name attribute. But that requires a seperate folder for each list template.
July 15, 2009 at 5:27:00 AM PDT
Unknown said…
The <ElementFile> element is not required when you use a folder that contains the 'schema.xml' file and the folder has the same name as the <ListTemplate> element's name attribute. But that requires a seperate folder for each list template.
July 15, 2009 at 5:28:00 AM PDT
WYLIESHADOW said…
quick fix for me too. thx!
December 9, 2009 at 12:21:00 PM PST
Russell said…
Thanks for taking the time to post this.
April 9, 2010 at 6:47:00 AM PDT
Post a Comment

Popular posts from this blog

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu...
Read more

Microsoft Virtualilzation Headaches

By -
As a SharePoint consultant, I am constantly moving from client to client and the best way to develop and test the code, designs and configurations for each client while maintaining complete separation is to virtualize. Since I work for a Microsoft partner, we try to use Microsoft tools and technologies as much as possible, which can be quite frustrating, as you will find out below. I recently started working for a large client with a global presence whose IT policies are well-established, difficult to change and not always up-to-date. In that vein, enter the corporate VPN: it's a web-based signin with a host checker that doesn't support any x64 OS. This prompted me, running Win 7 x64, to try to get a co-worker's Hyper-V Win2k3 x86 MOSS VM and run it in Windows Virtual PC . Seems like a logical thing to do, right? I mean, a Microsoft VHD should work, and be able to be imported by other Microsoft tools, right? Wrong. After spending quite a bit of time trying to attach the VHD...
Read more

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just...
Read more