The sandboxed code execution request was refused because the Sandboxed Code host Service was too busy to handle the request

That's quite the error right?  In just about every farm I have setup so far, I am getting this error: "The sandboxed code execution request was refused because the Sandboxed Code host Service was too busy to handle the request"

I haven't quite figured out exactly what the problem is, the ULS logs don't help much, they simply give a IPC error.  I have double checked everything.  Not sure what happened in RTM that changed from BETA.

I have seen the ACL fix, but that's for a domain controller.  Even applying the fix, it still won't go 🙁

Chris

SharePoint 2010 Generic Solution Validator

Sandboxed Solutions are not a very practical way of  testing solutions in production.  It opens up a world of bad things to happen.  That being said, there are still some good things that can come from them. 

The blocking solution provided in Central Administration is a complete joke, it won't help you for governing sandboxed solution deployment AT ALL.  However, I have built a tool that will solve many of the deployment issues with Sandboxed Solutions.  I call it the Generic Solution Validator.  It is scoped to a Site Collection level and allows you to ALLOW or BLOCK solutions based on various properties.  Properties much more valuable than the SCA provides.

I have posted the Generic Solution Validator to codeplex. 

http://bit.ly/4V8Yv7

Enjoy,
Chris

Solution Validators – Sandboxed Solutions

So you read my last post and decided that maybe SandBoxed Solutions isn't that great of an idea.  You decided to implement a Solution Validator to limit what your ole developers are doing.

You got the validator created and you installed it, but then realized, its not quite right.  So, you undeploy it right?  Oh, wait, every object that goes in the Object hierarchy table has to have a "public" contructor for deserialization (ie, pulled out of the ConfigDB and turned into memory). Otherwise you get a nice error in Visual Studio and/or Central Admin and you won't be able to retract the solution.

Exception in RefreshCache. Exception message : "MySolutionValidator.MySolutionValidator cannot be deserialized because it does not have a public default constructor."

K, if you followed the little article up there, then you'll notice that particular piece is missing!  Now your stuck…how do you get it out?  Well, you gotta run a command against the config database: NOTE:  This is a highly dangerous operation, if you mess it up, your Farm gets deleted!

delete from Objects
where properties like '%MySolutionValidator%' –or to be more safe, the full assembly name

You could also run the following stsadm command provided you do the query to find the id in the Config database:

select id, properties from Objects
where properties like '%MySolutionValidator%'

STSADM -o deleteconfigurationobject -id “id retrieved from object table”

This will clear the object and the retract will succeed.  This will be the case for ANYTHING that goes into the object hierarchy table.

Chris

 

Sandboxed Solutions – SharePoint 2010

So you have probably heard about this new "Sandboxed" solution "feature" of SharePoint 2010.  Sounds cools right?  Well, let's just wait till your developers get ahold of it and start to screw with your users in production!

So reservations I have include:

  • Point system is too high (300 points/day).  Really?  For each unhandled exception I get 1/50th of a point.  That means it would take  15,000 unhandled exceptions!  

Let me put that into perspective for you.

  • What if you create an event receiver that has an unhandled exception on PURPOSE?
  • Deploy that event receiver to your site for a specific list (let's say only the most important one on the site)
  • Well, your end users will have the joy of trying to add/update an item 15,000 times while getting a nasty modal error popup before you hit 300 points and it is disabled
  • Oh, did I mention they would need to do that every morning?

Sounds fun right? No….

  • How about the fact that the resource points aren't updated but every 15 minutes?  Hmmm, guess that means I can do as many bad things as I want in 15 minutes and go over 300 points!
  • Oh, wait what if the Timer service is NOT running?  No points will be updated…doh!

Not too sure about this whole Sandboxed Solution thang…how about you?

CJG

Follow me on twitter!