Forwarding to eFilm 3.0

Doing a search, I've read where eFilm 3.0 has some issues with certain DICOM header values being empty, but not where eFilm 3.0 has a problem with forwarded studies ONLY. eFilm 2.0 does NOT have this problem, only 3.0.

I am sure it is an export setting I munged up in dicom.ini. Can someone take a look and point me in the right direction?

Here is the eFilm log entry:

(1720) 08-20 12:45:17.73 MC3  E: Error on Read_Transport call(1720) 08-20 12:45:17.73 MC3  E: Error on Read_PDU_Head call: Transport has shut down(1720) 08-20 12:45:17.73 MC3  E: Transport unexpectedly closed(1720) 08-20 12:45:17.73 MC3  I: DUL_read_pdvs error: UL Provider aborted the association(1720) 08-20 12:45:17.73 MC3  E: (0000,0000): Error during MC_Stream_To_Message:(1720) 08-20 12:45:17.73 MC3  E: |   Callback cannot comply(1720) 08-20 12:45:17.73 MC3  E: Network connection unexpectedly shutdown(1720) 08-20 12:45:17.73 CStoreRoot::SCPStore: An association(ID= 10080) is shut down or aborted!

Here is the Forwarding section of dicom.ini:

# Forwarding Rules
ForwardAssociationLevel = STUDY
ForwardAssociationCloseDelay = 5
ForwardAssociationRefreshDelay = 3600
ForwardCollectDelay = 120
ExportConverters = 2
ExportConverter0 = forward to READSTATION
ExportModality0 = *
ExportCalledAE0 = PACSSERVER
ExportCallingAE0 = OEC_9800
ExportConverter1 = forward to TESTBOX
ExportCallingAE1 = TESTSERVER

READSTATION - eFilm 3.0.1
PACSSERVER - Conquest 1.4.13
OEC_9800 - C-Arm

If I send from OEC-9800 to PACSSERVER, it forwards the study to READSTATION. The study appears to make it, but the eFilm queue shows FAILED, with a NETWORK UNEXPECTEDLY SHUTDOWN comment.
If I send the same study from the conquest UI, it works JUST FINE. I have done other tests as well: eFilm -> Conquest forward -> eFilm and it also gives that message.

In a nutshell, ANY study FORWARDED from conquest gives that failed message. Can anyone shed some light??? Thanks a bazillion. -Scott

That did the trick. Thanks.