Open Bordasludovic opened 11 months ago
Got the same problem approx a year ago. The recompiling dcmtk storescp and getdcmtags with libiconv lib solves this.
I think it's because of the following characters that are contained in several DICOM tags in the two files stuck in the incoming folder: { and }
We're also experiencing this issue. Have you discovered anything about its cause? Could you share how to resolve it?
Thanks!
Check my last post here: https://github.com/mercure-imaging/mercure/issues/52
Hi - I'm running 0.2.0-beta4. Everything's been going fine for a long while, but similarly all of a sudden this started showing up all the time: ERROR: Unable to perform character set conversion! ERROR: Incoming charset is ISO 2022 IR 6
I looked briefly at all the dicom tags and did not see any funky characters that I wouldn't expect.
Is the recommended fix to follow "getdcmtags compilation guide"?
Thanks very much, Rich
Hello,
I have this error message in a loop on one of my DICOM routers.
I'm under the impression that a facility has recently been sending us DICOM images with tags whose characters are non-convertible.
oct. 27 10:14:11 tlg-dcomr11 receiver.sh[742888]: ERROR: Unable to perform character set conversion! oct. 27 10:14:11 tlg-dcomr11 receiver.sh[742888]: ERROR: Incoming charset is ISO 2022 IR 100
Have you an idea to fix that ?