The following issue does not have specific, related error messages in the Application Log, but it has been observed and some workarounds are provided: