I ran into the same exact error. It was caused by a script I was using to deploy the application which replaced the Web.config with a previous version. The Web.config was specifying the wrong version of System.Web.Http. Removing that step solved the problem.