It has been nearly a week since this issue was reported, and at that time the expectation was set that it was possibly going to be resolved the day it was reported.  Still, this error persists, and the reason for the error is not apparent.  Can we please get an update on what is happening with this, and when we can expect it to be resolved? 

Thanks very much.

Mike