Note that, like the other 'new Error' cases, this won't actually get serialized back properly today and will show up in the UI as 'unknown internal error' or some such.  I think that's ok for now though -- the 'wrong' UI message isn't that far off the mark anyway.  Per my comment in #3179, I think we could tackle that as a later cleanup.