It looks like this was an ongoing issue last week and I am still getting the same error message. Any suggestions???
