I came across this exception this morning while playing with RavenDB. A quick search shows several people have seen this exception but not a lot of solutions.
I’m not sure why, but this exception in my case was related to IntelliTrace. I turned IntelliTrace off and the exception went away. Weird.
BTW - this isn’t related to RavenDB. According to this post, the issue is a bug in IntelliTrace.
No comments:
Post a Comment