1

Resolved

Error occurred in deployment step 'Activate Features': Failed provision list content types on list instance 'MyList'.

description

Error occurred in deployment step 'Activate Features': Failed provision list content types on list instance 'MyList'. The content type '0x0100CE2E5959AA85468F8BE838B190E90AF2' failed to provision on /sites/forum/Lists/MyList. The content type name '$Resources:MyResource,ContentType_MyContentType_Name;' cannot contain: \ / : * ? " # % < > { } | ~ & , two consecutive periods (..), or special characters such as a tab.
 
To reproduce this error:
1) Create content type with name "$Resources:MyResourceFile,MyResourceKey;"
2) Create list instance with this CT.
3) Deploy from VS2010 (SharePoint project)
4) Change in MyResourceFile value of MyResourceKey
5) Deploy from VS2010 : fails.

comments

tore7506 wrote Mar 27, 2011 at 6:44 PM

Most likely is that the resource key can not be found when the content type is provisioned. Sharepoint fails to resolve the resource syntax and interpret it as a simple text string, which then fails because it has illegal characters in it. I will investigate this further and try to reporduce your steps. Status will change to "Active".

tore7506 wrote Mar 27, 2011 at 7:15 PM

I was not able to reproduce this with the steps described. However I noticed that in your step 4, you wrote "MyResourceFile" but in the declaration of the content type you have "MyResource,....", coudl this be the failing point?

I have created lite and a content type wich gets its name from i resource file and it all works ok here.

If you havent resolved this problem yet, could you please post the source code?

Regards,
Tony

robertovich wrote Mar 28, 2011 at 10:12 AM

Sorry it was my misspelling in post: resources in real project are Ok.
The problem is not consistent and happens only when I deploy via Visual Studio.
If I'll able to reproduce it, I'll notify you.
Thanks.

tore7506 wrote Mar 30, 2011 at 9:04 AM

I will set this to 'fixed' for now. We can re-open this if the problem should still exist.

wrote Feb 14, 2013 at 2:13 AM

wrote May 16, 2013 at 7:49 AM

wrote May 16, 2013 at 7:49 AM

wrote Jun 14, 2013 at 6:55 AM