Critical Core System conversion error in 10.2.300

We have been having numerous issues with invoicing sine moving to 10.2.300. Many of these issues are due to the core system conversion 1250 failing with the following:

System.Data.SqlTypes.SqlTypeException: SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.
   at System.Data.SqlTypes.SqlDateTime.FromTimeSpan(TimeSpan value)
   at System.Data.SqlTypes.SqlDateTime.FromDateTime(DateTime value)
   at System.Data.SqlClient.MetaType.FromDateTime(DateTime dateTime, Byte cb)
   at System.Data.SqlClient.TdsParser.WriteUnterminatedValue(Object value, MetaType type, Byte scale, Int32 actualLength, Int32 encodingByteSize, Int32 offset, TdsParserStateObject stateObj, Int32 paramSize, Boolean isDataFeed)
   at System.Data.SqlClient.TdsParser.WriteBulkCopyValue(Object value, SqlMetaDataPriv metadata, TdsParserStateObject stateObj, Boolean isSqlType, Boolean isDataFeed, Boolean isNull)
   at System.Data.SqlClient.SqlBulkCopy.ReadWriteColumnValueAsync(Int32 col)
   at System.Data.SqlClient.SqlBulkCopy.CopyColumnsAsync(Int32 col, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyRowsAsync(Int32 rowsSoFar, Int32 totalRows, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table, DataRowState rowState)
   at Erp.Internal.PE.PELib.CreateRow(ErpContext Db, String tableName, DataTable dt, DataTable dt_UD, Boolean dumpDatatable) in C:\_projects\ERP\RL10.2.300.0\Source\Server\Internal\PE\PELib\PELib.cs:line 236
   at Erp.Internal.Conversion.XACreatePaySchedForTermsAndInvoices.UpdateData(String tableName, DataTable dtMainTable, DataTable dtMainTable_UD) in C:\_projects\ERP\RL10.2.300.0\Source\Server\Internal\Conversions\XACreatePaySchedForTermsAndInvoices\XACreatePaySchedForTermsAndInvoices.cs:line 297
   at Erp.Internal.Conversion.XACreatePaySchedForTermsAndInvoices.convertData() in C:\_projects\ERP\RL10.2.300.0\Source\Server\Internal\Conversions\XACreatePaySchedForTermsAndInvoices\XACreatePaySchedForTermsAndInvoices.cs:line 210
   at Erp.Internal.Conversion.XACreatePaySchedForTermsAndInvoices.RunConversion(Int64 InstanceTaskNum) in C:\_projects\ERP\RL10.2.300.0\Source\Server\Internal\Conversions\XACreatePaySchedForTermsAndInvoices\XACreatePaySchedForTermsAndInvoices.cs:line 77

Is anyone else running into this?

What version did you move from?
Just curious if this was a small step like from 10.1.600, or big one from 9.x …

10.1.400.16 to 10.2.300.2

We have made a similar move, 10.1.400.22 to 10.2.300.5 but have not seen (at least we are unware) of any invoicing issues.

@jgehling - what exactly is the “core system conversion 1250” ??

Something you’ve run once since upgrading? Or something that runs every time you do invocing?

It is an auto ran conversion as part of the upgrade process. Look at 1250 in the conversion workbench.

Anyway, it failed for us because people awhile ago fat fingered in ap/ar invoice dates like 01/20/0203 or 02/15/2125.

We manually fixed the dates on the invoices and these now complete successfully.

There should be an enhancement coming soon for this conversion so that it skips over bad invoices and completes everything, rather than a hard stop