System.OverflowException: Failed to convert parameter value from Int64 to Int32 during file archiving in ESM/DL (4381344)

You may observe one or more of the following:

• Certain files (often with large metadata or large identifiers) fail to archive successfully.

• Files move to the Error folder instead of the database.

• Logs show System.OverflowException referencing Int64 → Int32 conversion failure.

• The DataLoader (DL) service continues receiving files, but only specific files repeatedly fail.

• Reprocessing the files reproduces the same failure.

This condition prevents affected files from being inserted into the database through the standard ESM/DL pipeline.

The error occurs when the ESM Business Layer attempts to insert message data using a parameter defined as Int32, but the source value is an Int64 that exceeds the range supported by Int32.

Root cause details:

1. Certain database table fields or stored procedure parameters were originally defined as INT (32-bit) while incoming metadata uses BIGINT (64-bit).

2. The original Quest.AM.BusinessLayer.dll enforces Int32 conversions for these fields.

3. When a file contains values larger than 2,147,483,647 (Int32 max), the conversion fails.

4. SQL Server rejects the value, causing the DataLoader to push the file to the Error folder.

This is a schema mismatch issue between the Business Layer, database table, and stored procedure definitions.

1. Stop ESM and DL service.

2. Take a backup of Quest.AM.BusinessLayer.dll and replace it with the DLL provided in the attachments.

3. Open the scripts ModifyingMessageTable.sql and ModifyingMessageInsertProcedure.sql in SSMS and execute them respectively.

4. Cut and paste all .xml files from the Error folder into the Export folder.

5. Restart the DL service and verify whether the files are now being stored in the database and are not returning to the Error folder.

6. Restart the ESM service.