This is likely caused by insufficient local filesystem permissions for the Application Pool Identity account in IIS. If you're running your own server, you should be able to resolve this through Windows by granting the App Pool Identity account full access to the c:\windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files folder, otherwise you'll have to get your hosting provider involved to solve it.
Jamie