Recent Activities

  • marcelvanherk

    Replied to the thread Conquest Delivery Errors.
    Post
    Hi,

    too bad. Can you strip down the export converters to their bare essence and try again? And what happens if you disable the delete converter? 'Failed to connect' of course points at a network error. Is the listed host correct? There may be a lookup…
  • kakarr0t

    Replied to the thread DICOM server 1.4.19 released.
    Post
    Thank you for that reply. I should have mentioned we're using Linux CentOS. We complied on a test CentOS station and copied over the dgate file as well as the dgate.dic. Thanks again! --Tim
  • garlicknots

    Replied to the thread Conquest Delivery Errors.
    Post
    We upgraded yesterday actually. Unfortunately that did not resolve the issue.

    /edit: we have also now added an additional vCPU to the guest in case this was somehow related to processing power.

    /edit2: Marcel - I am reading in other threads about how…
  • marcelvanherk

    Replied to the thread DICOM server 1.4.19 released.
    Post
    Hi,

    just replace the two exe files and maybe dgate.dic. You can start with dgate(64).exe first with limited risk.

    Marcel
  • marcelvanherk

    Post
    Hi,

    You are likely right, conquest attempts to change the registry itself when installing. But it needs admin rights to do this.


    'Empty' is likely a patient ID; can you look at the header of the images insde


    regards,

    Marcel
  • marcelvanherk

    Replied to the thread Problem with Conquest Dicom Server.
    Post
    Great idea!

    Marcel
  • marcelvanherk

    Replied to the thread Conquest Delivery Errors.
    Post
    Hm, it is a complex issue.


    is it possible to test this with 1.4.19b? You can swap dgate(64).exe without any change.

    Marcel
  • garlicknots

    Replied to the thread Conquest Delivery Errors.
    Post
    There are no ExportFailures files on any of our nodes in the cluster, interestingly enough.
  • garlicknots

    Replied to the thread Problem with Conquest Dicom Server.
    Post
    Axel,

    We've observed behavior like this when certain abstract syntax selections and have disabled them. You should look at the syntax being negotiated in 1.4.17 and modify your 1.4.19 dgatesop.lst to encourage that preferred method.
  • garlicknots

    Post
    @jacknsnac

    DICOM server 1.4.19b bug fixes and updates

    this resolved our build issues.
  • garlicknots

    Replied to the thread Conquest Delivery Errors.
    Post
    I'm working with kakarr0t on this issue. Our biggest question right now revolves around the fact that stopping and starting the process will result in successful deliveries. It's as if the ExportConverter thread itself becomes unstable or something. We…
  • simjo

    Thread
    Hi,
    I use Conquest 1.4.19b together with the anonymization script.
    Everything works fine but when I send large studies to Conquest, I get a MySQL error
    20180712 11:19:23 ***Cannot connect to MySQL on port 3306
    20180712 11:19:23 ***MySQL Error message:
  • marcelvanherk

    Post
    You need to use the updated qrsop.cxx from the bug list page; that will alleviate at least one error. Can yoy try that?

    Marcel
  • jacksnac

    Post
    Hi Marcel,

    I am using the latest release which is 1419b, sorry I was messed with the error message, I have put the error messages shown in the console in the attachment this time.

    Kind Regards,
    Jack
  • kakarr0t

    Replied to the thread Conquest Delivery Errors.
    Post
    dicom.ini file, HERE. (posted separately from post above)
    (Code, 190 lines)

  • kakarr0t

    Posted the thread Conquest Delivery Errors.
    Thread
    Hi Marcel, we've been having a lot of intermittent "Forward failed to connect" errors for quite some time, with no apparent rhyme or reason, and it only seems to be getting worse. We archive several days worth of logs (serverstatus.log, PacsTrouble,…
  • kakarr0t

    Replied to the thread DICOM server 1.4.19 released.
    Post
    Hi Marcel, do you have any instructions for upgrading from 1417e to 1.4.19b? Thanks! --Tim
  • tsuyoshi

    Post
    Hi!

    Thank you for your reply.

    I understood what you meant.

    Tsuyoshi
  • marcelvanherk

    Post
    Hello,

    these are warnings not errors and should not affect compilation or function.

    regards


    Marcel
  • marcelvanherk

    Post
    Just the console output is in the text (you overwrote it in the last line).

    Did you use the update that is in the bug list page?


    Marcel