CSTORE - A tag was encoded in the stream not in ascending order

423 views
Skip to first unread message

Mike

unread,
Apr 22, 2013, 3:36:30 PM4/22/13
to fo-d...@googlegroups.com
Hello,

I am using the fo-dicom library to send images to a Merge FUSION PACS. With some MR images I am receiving a rejection with the following message in the fusion logs, however a ClearCanvas ImageServer can send these images to fusion without issue. I am testing with the example code:

var client = new DicomClient();
client.AddRequest(new DicomCStoreRequest(@"test.dcm"));
client.Send("127.0.0.1", 12345, false, "SCU", "ANY-SCP");

FUSION Log:

1296 [01:06:57.271 ERROR]:MC3  E: Tags not in ascending order: (0029,4000) found after (0029,5003)
1296 [01:06:57.271 ERROR]:MC3  E: (0029,4000): Error during MC_Stream_To_Message:
1296 [01:06:57.271 ERROR]:MC3  E: |   A tag was encoded in the stream not in ascending order
1296 [01:06:57.271 ERROR]ReadMessageToTag:MC3  E: Message received encoded improperly A tag was encoded in the stream not in ascending order
1296 [01:06:57.271 ERROR]\Association.cpp(1277):[CAssociation ReadMessage()] Invalid message received.


If I use the DICOM Dump utility this tag is indeed out of order, I was wondering if there is a way to send these images using fo-dicom.

Thanks in advance.

Anders Gustafsson Cureos AB

unread,
Apr 24, 2013, 4:00:15 AM4/24/13
to fo-d...@googlegroups.com
Are you explicitly (creating or) modifying these images in any way using fo-dicom, or are you only using fo-dicom to read and transfer the images? How are the tags ordered in the images before you read them into fo-dicom?

Mike

unread,
Apr 24, 2013, 9:54:42 AM4/24/13
to fo-d...@googlegroups.com
Currently I am only using fo-dicom to read and transfer the images, I did a dicom dump on the images and confirmed what the log is saying is true, 0029,4000 is below 0029,5003 - is there a way to order the tags before sending? 

Colby Dillion

unread,
Apr 28, 2013, 10:07:54 PM4/28/13
to fo-d...@googlegroups.com
Do you have a sample image?

Colby Dillion

unread,
Apr 28, 2013, 11:04:00 PM4/28/13
to fo-d...@googlegroups.com
This should be fixed in the latest code.

Colby

Mike

unread,
Apr 28, 2013, 11:08:48 PM4/28/13
to fo-d...@googlegroups.com
Thanks, I'm running 1.0.31 - i'll try the latest code and let you know.

Mike

unread,
Apr 30, 2013, 11:06:56 AM4/30/13
to fo-d...@googlegroups.com
Thanks Colby,

The error is gone in the 1.0.33 code.
Reply all
Reply to author
Forward
0 new messages