A workaround provided by Avid support was
posted by a customer earlier in this thread, and subsequently
added to the Knowledge Base. The issue was also
logged here (and linked from the first post in this thread) which you can
Follow to be notified of changes.