And this issue has now been identified and resolved! Thanks again for your help in tracking this down.