Problem Transfering Images

[santosh]

Hi,

We are transferring the dicom images from the Philips MR modality, model name (Achieva). I am running the storescp server in one of the XP machine (Professional edition with service pack 2). The problem is i am unable to receive the MR images(MR Enhanced Image Storage) though the image transfer from CT modality works fine.
Here is my command line,

storescp.exe -v -d -aet RadServer --filename-extension .dcm 5001 > storescplog.log

as i am quite familiar with the storescp.exe i have tried all the different options with no use,i also used the --promiscuous mode that to didnt work.

Association Received
Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name:
Calling Application Name:
Called Application Name:
Responding Application Name:
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
called AE:
calling AE:
Association Rejected: bad application context name:
0006:0303 DUL Finite State Machine Error: No action defined, state 1 event 7
Association Received
Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name:
Calling Application Name:
Called Application Name:
Responding Application Name:
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
called AE:
calling AE:
Association Rejected: bad application context name:
0006:0303 DUL Finite State Machine Error: No action defined, state 1 event 7
Association Received
Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name:
Calling Application Name:
Called Application Name:
Responding Application Name:
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
called AE:
calling AE:
Association Rejected: bad application context name:
0006:0303 DUL Finite State Machine Error: No action defined, state 1 event 7

I also tried with the dicom eye server and efilm server they are also not receiving the images.

these are the logs from dicomeye

***** Connection wanted 14:27:21
** Association Received Monday, March 02, 2009 at 14h27mn21s
** Association Rejected: bad application context name

DUL Finite State Machine Error, State: 1 Event 7
ASC Network layer error
$$ CONDITIONS Remaining
***** Connection closed 14:27:21

***** Connection wanted 14:27:24
** Association Received Monday, March 02, 2009 at 14h27mn24s
** Association Rejected: bad application context name

DUL Finite State Machine Error, State: 1 Event 7
ASC Network layer error
$$ CONDITIONS Remaining
***** Connection closed 14:27:24

***** Connection wanted 14:27:30
** Association Received Monday, March 02, 2009 at 14h27mn30s
** Association Rejected: bad application context name

DUL Finite State Machine Error, State: 1 Event 7
ASC Network layer error
$$ CONDITIONS Remaining
***** Connection closed 14:27:30


Please let me know the reason for the same.

Thanks
Santosh S.B

[Jörg Riesmeier]

The error message "Association Rejected: bad application context name:" means that the Storage SCU apparently did not use the well-known UID "1.2.840.10008.3.1.1.1" to specify the communication protocol to be used (i.e. DICOM). In fact, from the log you've provided it seems that the Application Context UID as well as the Application Entity Titles are empty! You should definitely check the configuration on the client side ...