I got the same error and never heard of it until today. Curious what we find out and how to fix it within application. My guess is that is a programming error in application.
