The dcmtk I am now using in debian Etch is version "dcmtk: findscu v3.5.4 2005-12-20", which I am problem with findscu.
I got this error message: "error: bad key format or dictionary name not found in dictionary: 0010,0020=004099999"
The command line I used is this:
findscu -S -k 0010,0020=004099999 -aet TESTAET -aec MYMSTERAEC 192.168.100.2 5000 ./CFindQuery.dcm
and I also tried this:
findscu -P -k PatientID=004099999 -aet TESTAET -aec MYMSTERAEC 192.168.100.2 5000 ./CFindQuery.dcm
would also give the same error.
Any help is much appreciated. Thanks
-Ken
Findscu not working in debian Etch
Moderator: Moderator Team
-
- DCMTK Developer
- Posts: 2051
- Joined: Fri, 2004-11-05, 13:47
- Location: Oldenburg, Germany
- Contact:
Hi,
this is an alltime favourite bug in 3.5.4. Please refer to FAQ #43, which also contains a link to a fixed version.
Regards,
Michael
this is an alltime favourite bug in 3.5.4. Please refer to FAQ #43, which also contains a link to a fixed version.
Regards,
Michael
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
There's also a Debian bug report.
I have already uploaded a fixed Debian package version to
ftp-master.
http://packages.qa.debian.org/d/dcmtk/n ... 3204Z.html
However, on s390 the package fails to build from source with an
internal compiler error while it builds successfully on a number
of other architectures:
http://buildd.debian.org/pkg.cgi?pkg=dcmtk
The full build log for s390 can be found at:
http://buildd.debian.org/fetch.cgi?pkg= ... 1185227212
This is most probably a bug in the toolchain on s390 which needs
to be resolved before the updated package can enter testing.
Best regards - Juergen
ftp-master.
http://packages.qa.debian.org/d/dcmtk/n ... 3204Z.html
However, on s390 the package fails to build from source with an
internal compiler error while it builds successfully on a number
of other architectures:
http://buildd.debian.org/pkg.cgi?pkg=dcmtk
The full build log for s390 can be found at:
http://buildd.debian.org/fetch.cgi?pkg= ... 1185227212
This is most probably a bug in the toolchain on s390 which needs
to be resolved before the updated package can enter testing.
Best regards - Juergen
Who is online
Users browsing this forum: Google [Bot], Majestic-12 [Bot] and 1 guest