My client has a problem when printing certain SO Acknowledgements;
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask:
System.Data.SqlTypes.SqlTypeException: SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.
Strange thing is that we had an issue a few days ago and nothing has happened to the SO but it now prints the absolutely fine.
I’ve checked all the date fields in SQL in OrderHed, Dtl and Rel and all seem to be populated in the yyyy-MM-dd format as you’d expect.
Anyone else had a similar problem. This is ongoing and only started to happen a few weeks ago.
This can happen when a date is entered incorrectly. It may/may not be part of the order you are looking at, but that’s a good place to start. You can do a BAQ on the Head, Detail and Release tables to look for dates that are entered wrong. The most common I’ve come across lately is MM/DD/0222…
What version is are you on? We had this error back in August where a user manully entered at 2 digit year instead of selecting from the Calendar and Epicor did not translate to the 4 digit year. At the time we were in the middle of upgrading to 2022.1 so our Prod environment was still on 2021.2 when the 2 digit date was entered. I tried to replicate the issue but the timing was such that our environments had since been upgraded to 2022.1 and when I typed the 2 digit year of 22 it was translated to 2022 and we haven’t had this issue since. I could only assume this was fixed in the 2022.1 release.
This ended up being caused an updatable dashboard where excel had formatted dates to 01/01/0001.