tags:

views:

221

answers:

2

Our logs show hundreds of these errors after our deployment if users are on the site. Anyone know what this means and how to fix it?

Notes:

  • We are using msdeploy, IIS 6
  • I recently noticed that our web server's time is about 10 minutes behind the real time, I think that may have something to do with it.
  • If I log into our site, seems like any file that depends on a WebResource or ScriptResource type file doesn't look right.
  • Seems to fix itself after an IIS reset
+4  A: 

try running

for %i in (*.dll) do copy /b %i+,,

in the Bin directory of the application.

it means that the assembly was built in future according to the webserver, the command above will 'touch' them so they appear to be of current date

Axarydax
Yeah, I think the future date on the dlls was the issue.
Rob
What a complete PITA. Why in the world should .Net care what date an assembly was built on? BTW, +1 solved my issue.
Chris Lively