I have never been able to reproduce this issue locally, but I know it has happened before. I was hoping to never see it again 
We will figure out a way to repro it here and track down the Null object reference (I wish C# would just tell me which object was Null!!)