Thanks for the update. I just restarted my server and can confirm that I am no longer receiving this error.