Please visit our Knowledge Base for a detailed explanation of the current issue and proposed workaround.