This issue was resolved at the time it was reported, but it was not closed in our system. We are closing this issue at this time. Thanks for reporting this issue.