David McDermit 

This is a System.NullReferenceException. In simple terms, it means that you tried to use something (e.g., call a method, access a property) on an object that hasn't been initialized (it's null).  Reading the stack further the error seems to be coming from here "Sdl.Verification.TermVerifier.TermVerifierProcessing.HasTargetEntry(ITermRecognitionHit sourceHit)".  So it seems that the method HasTargetEntry of the TermVerifierProcessing class in the Sdl.Verification.TermVerifier namespace attempts to reference an object that isn't there.

I don't know exactly why, but perhaps try first of all disabling the termbase verification and see if that helps?

David McDermit 

This is a System.NullReferenceException. In simple terms, it means that you tried to use something (e.g., call a method, access a property) on an object that hasn't been initialized (it's null).  Reading the stack further the error seems to be coming from here "Sdl.Verification.TermVerifier.TermVerifierProcessing.HasTargetEntry(ITermRecognitionHit sourceHit)".  So it seems that the method HasTargetEntry of the TermVerifierProcessing class in the Sdl.Verification.TermVerifier namespace attempts to reference an object that isn't there.

I don't know exactly why, but perhaps try first of all disabling the termbase verification and see if that helps?

Paul 

Will give this a try.  One question--where/how disable the termbase verification?

David McDermit 

Paul 

It worked.

Any idea why it would happen with this one job?   She had a lot of other jobs brought in and worked on at same time without this error?

Thank you

David