2025 Dec 08 8:32 PM - edited 2025 Dec 08 8:35 PM
I’m getting the following error when running a report that is populated through a C# DataSet.
EXCEPTION: Ln 1 Col 65533: irregular bytes 'í' and '¨' of a 3-byte sequence
at CrystalDecisions.ReportAppServer.ClientDoc.ISCDReportClientDocument.Open(Object& DocumentPath, Int32 Options)The issue occurs only occasionally, and if I run the same report again with the exact same parameters, it usually works and returns the correct data. Under normal circumstances this wouldn’t be a major problem, since retrying would solve it — but the real issue is that once the error happens, the report becomes locked and cannot be executed again.
Other reports continue to work normally. However, this specific report can only be executed again after restarting the RAS (Report Application Server), which is far from ideal in a production environment.
Has anyone experienced something similar or knows what might cause the report to lock itself after an exception? Any guidance would be greatly appreciated.
Request clarification before answering.
This is likely an encoding issue with the font(s) used in the report. Check that the fonts used in the report are Unicode and that the text is rendered as UTF-8
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 8 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.