Usually when I have seen these errors in the past, it is because you have not correctly set the expected SQLmodes during installation and configuration. See the last part of this section:
You will especially want to make sure that you are not using the NO_ZERO_IN _DATE mode, as that is what I suspect is happening here. We have instructions on how you can check and update your SQL modes here:
In the short term, a simple workaround that might work: add full start and end dates in the controlled values. So for example, if the dates you entered were 1934 - 1936, enter these in the Start and End date fields as 1934-01-01 and 1936-12-31 respectively. This avoids the error, and as a bonus, will actually give your end users better date range search results. \
Let us know if that helps!