I know that a few years after your question was posted, but I had this error and fixed it. This seems to be a problem with a damaged application pool. Restarting the server did not fix it, but created a new application pool for the site.
source
share