This issue has now been resolved via direct message. The database connection was set up for SQL Server 2005 and was using datetime fields instead of datetime2 fields. A database migration will be included in the next version to update these fields as necessary.