Random 404 using IIS

What would cause IIS to return a 404, only sometimes? If I hit a 404 on a page, I can simply hit refresh and it will come up. It’s reproducible. I’ve used fiddler to see what’s going on and I don’t see anything off. I’ve setup IIS tracing but again, I don’t see what exactly the issue would be, the file exists and the 404 only occurs sometimes. By sometimes I mean if I navigated to a page and got a 404 I could refresh and it would come up but other times I could navigate to that page and it would not 404. It isn’t limited to any one page or condition.

How do I handle null nested objects in RDLC report that is bound to custom assembly object datasource?

I have an RDLC report that I am rendering directly to the Response Stream as PDF (rather than using the ReportViewer). In the code that renders the report, it’s DataSource is bound to a List(Of ClassA) objects defined in a custom assembly. This seems to work for the most part. My problem is that I can’t seem to handle the situation where a nested object is null. For example, given ClassA and ClassB (the nested object) defined as follows: