Skip to main content
SharePoint

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Where are you uploading your solution? Is it on a On-Premise SP Environment or on Office 365? Commented Aug 6, 2012 at 18:37
  • Also, if you activate the features (with the event receiver attached) manually through the UI, do they get activated? Commented Aug 6, 2012 at 18:44
  • My solution is currently deployed to a local (on-premise) SharePoint instance for development purposes, but it'll be deployed to SharePoint Online in production. Also, the features with receivers all activate fine when activated individually via the UI -- the exception only occurrs when I try to activate them programmatically inside another feature receiver (i.e. I have one feature which activates a bunch of others, acting like a site definition). Commented Aug 7, 2012 at 3:21
  • Yes I have faced this same issue and could not manage to find a solution until now. I think this a limitation in Sandbox solutions. In my case, I had the features declared in a WebTemplate. And only the features who did not have event receivers would get activated when a site was created from that WebTemplate. Commented Aug 9, 2012 at 17:33