Same error this year. Thought it was a bug first or that something was mis-entered, but thanks to this thread, I just zeroed it.
