See FileNameSyntax in the manual.
Marcel
See FileNameSyntax in the manual.
Marcel
Thanks to blub:)
it is a mysql/windows issue: mysql uses temporary ports that are not released quickly enough. Mysql dies after several thousand connects/disconnects because all temporary ports are allocated. With the debug log, the server is slightly slower and the problem does not happen.
See:
http://support.microsoft.com/kb/q196271/
http://bugs.mysql.com/bug.php?id=6580
http://bugs.mysql.com/bug.php?id=10498
The error can be fixed by changing the following TCPIP parameters of windows by saving this snippet as as .reg file and double clicking it.
P.S. 1) Fix relates both to native and ODBC use of MySQL
2) There is a bug in native MySQL that affects queries of empty fields: these are not read correctly and show "ghost" data of other records. Will be fixed in next release.
Hi,
I can email a dgate.exe that gives some extra error messages if you send me a private message with your email. That may also help solve the problem.
Marcel
Hi,
the error 12 is not relevant: it is just the GUI detecting server problems. Maybe indeed the Mysql log could help find the problem.
Marcel
Hi,
This is all ysing the native mysql interface I assume? Could somebody try and compare with MyODBC? Apperently I use up a certain resource, but a simple code reread showed no obvious problems.
Marcel
Hi,
dicom.ini does not set a limit. It is just the edit box in the GUI that has four places. However, this means that the GUI does not read its port correctly from dicom.ini and some or all internal functions do not work - like the 'running' check. However, the server itself and the query.move page just work. Maybe ok for an intermediate solution.
Marcel
Hi,
Not seen this problem before. What version are you running. Maybe I can lookup the error address in the map file to get a clue. The machine did not go into standby or hibernation inbetween?
Marcel
Hi,
There is a fix in this option in version 1.4.12c. Maybe you can try the dgate.exe from that version?
Marcel
Hi,
It is sometimes hard to get to the core of the question... You have to use another filenamesyntax (e.g., 9) to save the files in DCM format. Then a transfersyntax is created in the header. V2 files no longer carry a transfersyntax. To add a transfer syntax to V2 files, indeed copy or drag and drop into another server that is set to DCM format.
Marcel
Hi,
retries should not happen when the images are not accepted. So apparently the images are accepted and then fail to process giving an error that conquest thinks is retryable. There is currently no way to stop the retries, except deleting the retry file. The GUI asks to do this when the server app is restarted. Could you maybe give me an excerpt of a full debug log of the retrying transmission? Then I can try to fix the error in later versions.
Marcel
Hi,
Probably you are not running 1.4.13alpha.
Marcel
Fairly recently we started stripping group 2 in certain circumstances. See the update history in the documentation. The syntax in the header should appear when saving to DCM.
Marcel
You can't. Multiprocess has been disabled and untested for ages - it is always multithreading. If you want to do multiprocess you would have to go into the dgate code and figure it out.
Marcel
You use conquest to move from Siemens to Conquest, all right? The error means that siemens ends the connection prematurely. Further no clue. What happens if you transmit from the Siemens console to Conquest ? We do that all the time without any problem. By the way, which version of conquest do you use (just for the record).
Marcel
No clue,
what is that ? If they are dicom objects you can set it up. If they are protocols probably not.
Marcel
Think so,
Conquest does not filter on calling or called AE: it will accept anything. The exportconverters can be configured to filter on calling and or called AE. So you should be able to set it up. You do not even need multiple conquest servers.
Marcel
Hi,
there must be a memory leak somewhere in conquest or mysql. Can you see in task manager which process is used all the (virtual) memory?
Marcel
Maybe spaces in path to server ?
Marcel
odbc or native? (just for the record).
Marcel
1) Should be possible. It works on linux and used pthreads. The original server ran on unix. I do not know how much work it is though.
2) To do that you need to write a section in odbci.cpp, similar to the POSTGRES section. Access to Oracle on windows uses odbc and works - but odbc is not included with linux.
I have no access to a solaris machine to try.
Marcel