yeah, seems to be all fixed now... haven't gotten the error in a long while