I spent over 2 hours talking to three different people from the custom support and none of them seem to be aware of such issue, which surprised me given this thread was post a week ago and followed by so many of us also experienced the same error.
Now I am really just hoping they are working on resolving this issue for us.
