AI OnAI Off
This issue was solved by running a SQL insert command on the tblPropertyDefinitionType table to enter a supporting property type for PropertyDate.
It's still a mystery as to why this wasn't discovered during local development and made it's way all the way to production and seemed to go down during a weekend when there was no usage of the not live yet site.
This error showed up on a production (not yet live) server.
It's troubling because the build was showing no issues for a week prior but there has been an extensive content entry on the Catalog and CMS side.
It appears it could be something related to the data entry that is creating corrupted data and resulting issue. I say this because I’ve ran an old release against the production dbs and get the same issue in my local environment.
If anyone has had experience with this or solved an issue like this your comments are greatly appreciated.
Thanks,
Ben