How are you producing the deployment package?
Have you tested the package on your local machine before deployment to production?
If it works locally I would try deploying the files again as that may make it flush out the temporary asp.net files that are apparently currently in a hosed state of some kind.
If you got an error like that on your local machine you could stop the IIS site and delete the temporary asp.net files manually but you can't really do that in a hosted environment so I think redeployment is the only way to try to make it regenerate the temporary files.