We have seen this too, but have been unable to replicate it here. The current releases of the applications have specific code to trap this occurrence, and no one has contacted us about seeing the message.