New Post: Mysterious Script Compile Failure after period of long running successful compile/execution

Unfortunately, even after adding all of the information exposed by JavascriptException to our logs, we get no information (all properties are null/empty).

We finally had this error show up on one of our "older" application servers, in one of our "older" apps that had never experienced this problem before.

I'm still trying to figure out what exactly was changed, but I do know for sure that one of the significant changes was enablement of IIS Advanced Logging on that server. IIS Advanced Logging has always been enabled on the "newer" app servers that have always had this problem.

I think we may have our root cause here, but we're still working on digging into what this might be the case.