UPDATE: We believe that we have traced the cause of this problem down to having Work.com enabled in your org. In our testing so far, if Work.com is enabled, then this issue occurs whenever you have a Model that either is on the User object, or contains Fields that are Lookups to the User object. Root cause of the issue: we are getting Salesforce “Internal Server Errors” whenever we try to access metadata related to Work.com objects, which unfortunately occurs whenever you are building pages against the User object as well because there are “Child Relationships” to Work.com objects — e.g. Thanks Givers, Badge Givers, etc. — all of these fields are lookups to the User object, and Skuid, in its effort to allow you to display in your pages any Child Relationships of the User object, is hitting this problem. Temporarily, a possible solution is to disable Work.com. Steps Skuid is taking to resolve: 1. We are isolating the issue and will report it to Salesforce.com internal support. 2. We are investigating possible code changes we can make to temporarily stop Skuid from trying to load in any metadata for Work.com objects or Child Relationships of the User object which point to Work.com objects, until Salesforce can fix their Internal Server Error, but this would of course be only a temporary fix. We will try to keep you updated as much as we can as we receive further information about this problem.
