Sounds like you may need to have your ISP restart your app pool. You can manually force this by downloading and re-uploading your Web.config file.

Arron:

That worked, thanks.

Did you make any changes to the site over the weekend? Typically when these error occur it happens a result of a site change that the ASP.NET compiler did not respond properly to.

I figured that would be the case. Unfortunately I don't have a solution for you. The problem stems from how ASP.NET dynamically compiles the website at runtime (unlike the other code in BV which is pre-compiled into assemblies/DLLs). In your case it sounds like something did not compile correctly or the compiled files, which are stored in a temporary folder, were corrupted. In our experience it's rare to see these errors after the code has compiled successfully; usually we only see these errors immediately after making a change on the site and before the ASP.NET compiler updates the files (e.g. if you get an error immediately after making a change you may need to refresh the page a few times until the error goes away--i.e. you've given the compiler enough time to notice the change and recompile the necessary files).

Edited by user Monday, July 15, 2013 10:45:34 PM(UTC)  | Reason: Not specified

You'll need to talk with your hosting company about this as this is a server-related issue, not a BV Commerce issue. You may need to have them adjust the frequency that the app pool is being recycled.

I would just tell them the problem that you're having and see what they recommend. Most likely if they do make any changes to the app pool recycling frequency they would make it more frequent. Honestly, though, I'm not sure that's the problem. Typically the only time that we see this error is when updating site files (e.g. uploading updated files to the server).

Applied Innovations is a partner so you may want to send them a link to this thread.