Hi,
this does not help much, because the crash is not in the server but in a windows DLL. It could be related to your database configuration. MyODBC is known to cause trouble.... What do you use?
Marcel
Hi,
this does not help much, because the crash is not in the server but in a windows DLL. It could be related to your database configuration. MyODBC is known to cause trouble.... What do you use?
Marcel
Hi,
can you find a crash address somewhere? (drwatson or so).
Marcel
Hi,
the server should not write .V2 files when jpeg compression is used. It should use a .DCM extension. Do you know how the image was loaded in the dicom server?
Marcel
Hi,
this could be a mysql specific issue. You can try to enable debug logging (debug log ON, arrows 5 times up) in the (windows) GUI and use:
dgate --selectlruforarchival:100000,0
This will start the selection task (for 100000 kb = 100 MB). The log will show all queries that are executed and could tell us what goes wrong.
To undo and try again first run:
dgate --restoremagflags:
To finally move the data you should use:
dgate --movedatatodevice:MAG1,MAG0.Archiving
Marcel
Ah,
you will have to create your own web page (you can use web scripting to override an existing viewer page) to do that. Now already the web viewer (html source page) provides links to dicom slices. If you enter those links in your web browser yu are asked to save them. But that would be file by file.
Marcel
Hi,
same as on the intranet. You need to put a conquest server with web access on a public web server.
Marcel
Hi,
What happens if you try to retrieve from STENTOR_SCU?
Marcel
Hi
the problem is in a single dicom file. The allocation is -536805378 bytes (note the minus). This indicates a corrupt DICOM object. Can you inspect the file 1.2.840.113619.2.135.3596.6865778.23395.1180409341.65_0004_000025_1223818786021d.v2? How big is it?
Marcel
Entry for dicom.ini from the manual (page 49):
Allowtruncate: Comma separated list of database fields without spaces that may be entered
truncated into the database giving a warning not an error
Marcel
Hi,
Error: anything that shows up with *** in the log. Only database field truncation errors are customizable.
Marcel
Hi
MailHost = name of mail server
MailSignon = mail server login name
MailFromName = stated email adress of sender
MailRcptName1 = email address of recipient 1
MailRcptName2 = email address of recipient 2
etc
MailCollectTime = minimal time in minutes to collect error messages (e.g., 1 means first error mail send one minute after error)
MailWaitTime = mail at most once every so many minutes (e.g., 1)
Mailing works from the GUI. I.e., a service will not mail when the GUI is not up.
Marcel
Hi,
I suspect it is an IQ-view database issue. There is no reason why dbaseIII would ever slow down and a conquest-conquest transfer is identical to a conquest-iqview transfer as far as conquest is concerned. Did you try to view with another IQ-view workstation?
You could also try to inspect task manager during the delays and see which process is having a large CPU load during transfer.
Marcel
Hi,
if you put both AE's into acrnema.map, you should be able to test query and transfer from the system from the query/move page. VirtualServer as is does not allow using different AE titles.
A silly question: does the PET system have conquest configured?
Marcel
Hi,
you can only view from the local server browsers (List local patients/studies), and not from the remote browser (Find patient/study/series on server). This is also true if you use this option to browse the local server.
Marcel
Hi,
the database only stores configured items in dicom.sql. You can extend it to add as much as you want, as long as you do not change the first and last field of each database, and regenerate after editing.
HOWEVER, this is only required if you want to QUERY on that data. The headers on disk are not touched and will store ALL data.
Marcel
Hi,
maybe you can try to send from that conquest to another one and see if the problem persists. What database are you using?
Marcel
Hi,
maybe you can (temporarily if you want) upgrade to the dgate.exe of 1.4.14 - or if you are using 1.4.14 switch one debug logging. This gives some more info in case of a rejected association. There may be a transfer syntax issue as well.
Marcel
Hi Mark,
I believe that the behavior is more or less correct: --imagelister should not be used to query filenames of a remote server through DICOM (this would be non-standard behavior). It can be used to query pat:sop using a format string like ":%s:%s". To get the filenames only 'local' as server is correct.
Marcel
Hi,
images have to be registered in the database to be visible. So to enter new images you can send them over a dicom connection or use windows drag and drop on the user interface panel: this will copy the images and update the database.
Marcel