why the same Storescu command sometime work but sometime doesn't - DICOM

This is a discussion on why the same Storescu command sometime work but sometime doesn't - DICOM ; below is a screen shot. I run the same storescu command three times, why it succeeds one time, but fails for the other two times ??? dials03-245: ls CR.1.2.392.200036.9125.4.0.1003465.3769217024.2026 910913 CR.1.2.392.200036.9125.4.0.1006025.3963203584.2026 910913 CR.1.2.392.200036.9125.4.0.1003721.3781931008.2026 910913 CR.1.2.392.200036.9125.4.0.1006281.3995185152.2026 910913 CR.1.2.392.200036.9125.4.0.1003977.3801722880.2026 910913 CR.1.2.392.200036.9125.4.0.1006537.4024020992.2026 910913 ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: why the same Storescu command sometime work but sometime doesn't

  1. why the same Storescu command sometime work but sometime doesn't

    below is a screen shot. I run the same storescu command three times,
    why it succeeds one time, but fails for the other two times ???

    dials03-245: ls
    CR.1.2.392.200036.9125.4.0.1003465.3769217024.2026 910913
    CR.1.2.392.200036.9125.4.0.1006025.3963203584.2026 910913
    CR.1.2.392.200036.9125.4.0.1003721.3781931008.2026 910913
    CR.1.2.392.200036.9125.4.0.1006281.3995185152.2026 910913
    CR.1.2.392.200036.9125.4.0.1003977.3801722880.2026 910913
    CR.1.2.392.200036.9125.4.0.1006537.4024020992.2026 910913
    CR.1.2.392.200036.9125.4.0.1005001.3883773952.2026 910913
    CR.1.2.392.200036.9125.4.0.1007305.4027297792.2026 910913
    CR.1.2.392.200036.9125.4.0.1005257.3904090112.2026 910913
    CR.1.2.392.200036.9125.4.0.251709715.2868904128.75 5371895
    CR.1.2.392.200036.9125.4.0.1005769.3910316032.2026 910913
    CR.1.2.392.200036.9125.4.0.2709913802.292728832.20 26910913

    dials03-247: storescu -aet DIALPIPE -aec LongRaw dialdbserver 4441 *
    storescu: Store Failed, file:
    CR.1.2.392.200036.9125.4.0.1003465.3769217024.2026 910913:
    0006:020e DIMSE Failed to send message
    0006:031d TCP I/O Error (Broken pipe) occurred in routine: writeDataPDU
    storescu: SCU Failed:
    0006:020e DIMSE Failed to send message
    0006:031d TCP I/O Error (Broken pipe) occurred in routine: writeDataPDU
    storescu: Association Abort Failed:
    0006:031d TCP I/O Error (Broken pipe) occurred in routine: sendAbortTCP

    dials03-248: storescu -aet DIALPIPE -aec LongRaw dialdbserver 4441 *

    dials03-249: storescu -aet DIALPIPE -aec LongRaw dialdbserver 4441 *
    storescu: Store Failed, file:
    CR.1.2.392.200036.9125.4.0.1003721.3781931008.2026 910913:
    0006:020e DIMSE Failed to send message
    0006:031d TCP I/O Error (Broken pipe) occurred in routine: writeDataPDU
    storescu: SCU Failed:
    0006:020e DIMSE Failed to send message
    0006:031d TCP I/O Error (Broken pipe) occurred in routine: writeDataPDU
    storescu: Association Abort Failed:
    0006:031d TCP I/O Error (Broken pipe) occurred in routine: sendAbortTCP


  2. Re: why the same Storescu command sometime work but sometime doesn't

    jiehuang001@hotmail.com wrote:
    > below is a screen shot. I run the same storescu command three times,
    > why it succeeds one time, but fails for the other two times ???


    The error message
    > 0006:020e DIMSE Failed to send message
    > 0006:031d TCP I/O Error (Broken pipe) occurred in routine: writeDataPDU


    seems to indicate that the receiving side (the Storage SCP) has just
    unexpectedly closed the transport connection or has possibly crashed.

    Regards,
    Marco Eichelberg
    OFFIS

  3. Re: why the same Storescu command sometime work but sometime doesn't

    I am facing the same problem while using the "storescu" command. Is there a reason for the receiving box to unexpectedly halt the transfer? Is there a fix / workaround for this?

    Thanks,
    -Kenny

+ Reply to Thread