Further to my previous 0x81070215 post, I've since discovered this error code also crops up when specifying an invalid ListTemplate value for the Name attribute.
In my case I was attempting to supply the value from a .resx file something like Name="$Resources:List_Name;". While resources are successfully resolved on other ListTemplate and List attributes, this doesn't seem to be the case with Name and its value must be specified explicitly; incidentally, the Name must match the name of the folder containing the list definition. The OOB 12-hive examples I've cross-checked also specify a literal value.
While this error code was presented in the UI, the SharePoint log files revealed how SharePoint was parsing the attribute value:
Cannot open "schema.xml": no such file or folder.
Failed to retrieve the list schema for feature {1B3FC94C-2FC6-4528-B968-4E91843C2005}, list template 13133; expected to find it at: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\TeMCorporateBannerListFeature\$Resources:List_Name;".
Unknown SPRequest error occurred. More information: 0x81070215
No biggie since DisplayName does handle resources for localisation however in this case I'm attempting to use resource files for consistency and to simplify maintenance across my list definition.
For reference, 0x81070201 seems to mean about the same thing (a similar error message I received after reverting the Name value to a literal with a typo).
are you using SPSource at all to generate list schemas?
ReplyDelete@JT: Not with any frequency (yet) as I usually start from the CustomList schema.xml. Out of habit I turn to the VSeWSS solution generator and AC's Custom Commands for STSADM as required to dump list definitions and site columns/content types respectively.
ReplyDeleteI've been thinking about giving SPSource another spin as of late but I'll echo Corey Roth's review comment about how nice it would be to be able to pass in a list URL without having to run through the full 12-hive structure and feature setup.
I've added an issue and actually added this functionality to run without feature structure ;-)
ReplyDeleteDear Author blog.mediawhole.com !
ReplyDeleteThe word of honour.