TIFF file throws CorruptOrDamagedFileException

We receive fax files in a TIFF format (compression CCITT T.4). If I want to convert the file into another format, it throws a “GroupDocs.Conversion.Exceptions.CorruptOrDamagedFileException” (Cannot convert. The file is corrupt or damaged. Image loading failed).
The TIFF file can be opened with any other drawing software, even with the Bitmap class in .NET. It is not corrupt.

The line, where the exception is thrown, looks like this:

 var converter = new GroupDocs.Conversion.Converter(tiffFile);
-->  converter.Convert(convertedFile, GetConvertOptions());

@adrian.schriber

Please share following details and we’ll look into this issue:

  • GroupDocs.Conversion API version that you are using
  • Development environment details (e.g. OS, .NET version)
  • Problematic file
  • Output file format type

Yes, of course:

  • GroupDocs.Conversion API version: 23.8.0
  • Development environment:
    – Win 11 Enterprise (10.0.22 Build 22000)
    – Visual Studio 2022
    – .NET 6.0 (C#)
  • Output file format type: PDF. But as I understand it, the format type of the target file doesn’t matter, because the loading of the TIFF file causes the problem
  • Problematic file: I added a ZIP file named “L232_20230920113909_033414.zip”
    L232_20230920113909_033414.zip (24,8 KB)

Thanks for your help :smiley:

1 Like

@adrian.schriber
You are welcome.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CONVERSIONNET-6384

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Great! Thanks again :+1:

@adrian.schriber

You are welcome.

The issues you have found earlier (filed as CONVERSIONNET-6384) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov

Great! I can confirm that it works now.
Thanks for fixing it!

1 Like

@adrian.schriber

You are welcome.