Hi all,
I have a problem with one client. I get message "The DICOM data set contains multiple values with the same name." during the file receive from server (version 1.4.16). It worked properly with older server (version 1.4.15).
I tried to found where the problem may be. I found than the newer server stored the TransferSyntaxUIUD (0002,0010 = LittleEndianImplicit) value to the file on MAG0. I use "FileNameSyntax = 3" in the dicom.ini. When I list the DICOM items from stored file by the DCMDUMP I get this:
------------------------------------------------------------------------------------------------------------------------------------------------------
W: DcmMetaInfo: No Group Length available in Meta Information Header
# Dicom-File-Format
# Dicom-Meta-Information-Header
# Used TransferSyntax: Little Endian Implicit
(0002,0010) UI =LittleEndianImplicit # 18, 1 TransferSyntaxUID
# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0008,0008) CS [ORIGINAL\PRIMARY\STATIC\EMISSION] # 32, 4 ImageType
(0008,0016) UI =NuclearMedicineImageStorage # 26, 1 SOPClassUID
(0008,0018) UI [1.3.6.1.4.1.12842.1.1.2.2.20120529.143510.750.3086666318] # 56, 1 SOPInstanceUID
...
------------------------------------------------------------------------------------------------------------------------------------------------------
And when I export same image from the server to the file through STORESCP I get this:
------------------------------------------------------------------------------------------------------------------------------------------------------
# Dicom-File-Format
# Dicom-Meta-Information-Header
# Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 218 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =NuclearMedicineImageStorage # 26, 1 MediaStorageSOPClassUID
(0002,0003) UI [1.3.6.1.4.1.12842.1.1.2.2.20120529.143510.750.3086666318] # 56, 1 MediaStorageSOPInstanceUID
(0002,0010) UI =LittleEndianImplicit # 18, 1 TransferSyntaxUID
(0002,0012) UI [1.2.276.0.7230010.3.0.3.6.0] # 28, 1 ImplementationClassUID
(0002,0013) SH [OFFIS_DCMTK_360] # 16, 1 ImplementationVersionName
(0002,0016) AE [ONM_DCMSRV2] # 12, 1 SourceApplicationEntityTitle
# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0002,0010) UI =LittleEndianImplicit # 18, 1 TransferSyntaxUID
(0008,0008) CS [ORIGINAL\PRIMARY\STATIC\EMISSION] # 32, 4 ImageType
(0008,0016) UI =NuclearMedicineImageStorage # 26, 1 SOPClassUID
(0008,0018) UI [1.3.6.1.4.1.12842.1.1.2.2.20120529.143510.750.3086666318] # 56, 1 SOPInstanceUID
...
------------------------------------------------------------------------------------------------------------------------------------------------------
As you can see the TransferSyntaxUID is duplicate. When I try to open stored file directly by the client I get same error as like during the receiving from server. When I delete the TransferSyntaxUID from file the client open it correctly.
The last server version (1.4.15) was not store the TransferSyntaxUID in to file on MAG0.
The list of DICOM items from the file which was stored by 1.4.15 version:
------------------------------------------------------------------------------------------------------------------------------------------------------
# Dicom-File-Format
# Dicom-Meta-Information-Header
# Used TransferSyntax: Unknown Transfer Syntax
# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0008,0008) CS [ORIGINAL\PRIMARY\WHOLE BODY\EMISSION] # 36, 4 ImageType
(0008,0016) UI =NuclearMedicineImageStorage # 26, 1 SOPClassUID
(0008,0018) UI [1.3.6.1.4.1.12842.1.1.2.2.20120612.090709.687.1220491601] # 56, 1 SOPInstanceUID
...
------------------------------------------------------------------------------------------------------------------------------------------------------
I do not know exactly if the problem is on the server side or bug is in the client which is not able to process it.
My question is if I can correct the server behavior so that it will be as like in the last version.
Please can you hlep me?
Thank you very much.
Milan