DICOM Move Error:Remote DICOM error

Hi,

your scanner probably does not accept the C-MOVE. You may not be correctly known to the MRI or you may be using an unsupported query. You could selecting a studyroot query from the sropdown list in the query page.

Marcel

I am having the same problem when trying to send studies from Conquest to a Philips MR System Archiva Release 2.5.3.0 2007-09-28.

C-Move from Philips to Conquest works fine. However when going the other way we get a C-Move error.

If anyone uses Philips MR with Conquest can they give some input as to specifics Philips might need.

Thank You

Louis

Hi
We have this problem betweeen Conquest and a Vitrea WS.
We changes AE titles IPs etc. it still isnt working either way..very strange....
Toshiba techs have no idea, Vital Images tech says ist a Conquest problem and he doenst really care - althour every other WS with different software works fine with CQ.
very annoying I have to admitt

Hi!
i have a similar problem when trying to retrieve studies from GE Centricity. I have configured the Conquest node correctly in Centricity. query works fine, but when trying to copy to destination I get DICOM Move Error:Remote DICOM error. Sending from Centricity to my Conquest node works perfectly. with another application (EFilm) configured identically as the Conquest instance (AET, port number, IP) retrieving works perfectly as well.

i used a DICOM sniffer and found this error: MOVE_REQUEST_IMPROPERLY_FORMATED.

does anybody know what is the problem and how can i fix it?

thanks!

Hi,

try double click on the series number label of the query/move page. This switches to a non-hierachical query mode based on UIDs. This may solve the problem.

Marcel

yes it did. double clicking on Series number enables query by Study/Series UID. first i needed to query by patient ID (or name); a list of studies appeared, with associated Study UIDs. then i copied the Study UID from the left window in the Study UID query field and the pressed the Copy button.

thanks a lot.

Hello Marcel,
Can I move studies from the command line in linux version. I am trying to migrate all the data base and images from this version to another dicom server. Can you tell me waht the command would look like. I can do this with the windows version but often get failures in data transfer. We have a lacie NAS with 1.3 Tb used out of 2 Tb. Almost all the studies are MRI.
Thanks
GH

Hi,

you sure can, these are the dgate options to use (version 1.4.14):

DICOM move options:
--movepatient:source,dest,patid Move patient, source e.g. (local)
--movestudy:source,dest,patid:studyuid Move study, patid: optional
--movestudies:source,dest,date(range) Move studies on date
--moveseries:source,dest,patid:seruid Move series patid: optional

Marcel

Hello Marcel,
Thank you. This has been most helpful. I have found an interesting problem whilst copying images across to the new server which has far more appropriate configuration. I found a recurring memory problem where D-gate attempts to use memory which is not allocated to it. have you encountered this before?
King regards
GH

Hi,

As far as I know there is only one reported crash bug in 1.4.14:

14) Crash because BindField(1,....) is never called in UpdateOrAddToTable in dbsql.cpp. Thanks Tego! Fixed in next release 1.4.14a.

If you use linux, please try this fix:

http://www.image-systems.biz/f…ilit=crash&start=15#p5167

Marcel

Hi Here is the error message whilst copying 74 cases from on server to the other (19740 MRI slices),
Sending file : /mnt/dicomdata/43373-/1.3.46.670589.11.8511.7.1374131600000066740801_0801_000009_11833638030f73.v2
Image Loaded from Read Ahead Thread, returning TRUE
***VR:ReAlloc out of memory allocating -536805378 bytes

MyPatientRootRetrieveGeneric :: RetrieveOn
***A fatal error occurred (out of memory) - closing server

Thanks for the info
I will try it out.
Georges

Hi,

is it reproducible? This looks like a corrupted DICOM file to me.

Marcel

Hi Marcel,
I think you are correct. The problem has been reproducible. I suspect there are likely to be a number of corrupted Dicom files. Is there any way the the server can skip though a corrupted file or better still isolate that file in an exception list and transfer the remain files instead of crashing? The file can then be managed separately.
Just a though.

Again Thanks for all the help.

Georges

Hi,

You can set IgnoreOutOfMemoryErrors = 1 to get you through the currupted files.

Marcel

Hi Marcel,
Where do I set the command for it to ignore out of memory errors?
Source code?
Dicom ini file ?
command parameter?

Thanks
Georges

In dicom.ini, at the end.

Marcel

Hi!
i also have a problem when trying to retrieve studies from GE Centricity. Query and copy of all data from a patient works fine, but when trying to copy for example only a serie or a single image to destination I get DICOM Move Error:Remote DICOM error.
The tip double "click on the series number label of the query/move page" did'nt help. And how to do the following? There is no Study UID query field in Conquest 1.4.1.4 or 1.4.1.5alpha.
Thanks for any help.
Hubert

Quote from mpetruc

yes it did. double clicking on Series number enables query by Study/Series UID. first i needed to query by patient ID (or name); a list of studies appeared, with associated Study UIDs. then i copied the Study UID from the left window in the Study UID query field and the pressed the Copy button.

thanks a lot.

Hi,

if you double click on the label, query switches to UID mode. Do you see that?

Marcel