Black View Screen

  • I had 9 kpacs systems running with a Conquest Dicom Server up until yesterday. Now, only 1 of the KPacs systems can download from the server or be sent images from the server. What can I look at to fix this? There is error information in the logs but not real explanatory. Any help?

  • You should post some of those log information otherwise we can guess, only. :D


    Check out if you can echo the server from the 8 K-PACS that have the problem (ECHO is available in the DICOM Settings for Query/Retrieve within K-PACS). Also, check your "Known DICOM Provider" list in Conquest. All your K-PACS have to be listed there with their correct settings (AE title, IP, PORT). Keep in mind that the AE title has to be unique for each station, means, all your K-PACS have to have a different AE title.
    And finally, check your network is fine (check with network 'ping').

  • TIA,


    Which log do you want to see?
    I am thinking that it might be a field size issue with the filename or directory. Conquest says that it can't find the file but I can go to each machine, thru the KPacs filesystem tab, locate the file and bring it up and view the image. then I go to another machine, Network tab, locate the name and it comes up with a black screen.
    Here is the a few entries out of the pacstrouble.log:
    20070914 09:09:17 *** Not enough rights to write in MAG0
    20070914 09:36:19 Inconsistent PatientNam in DICOMPatients: PatientID = 'NO ID' PatientID = 'NO ID', Old='DAVIS^ SHERRY', New='EVERETTE COONCE'
    20070914 09:36:19 ***Inconsistent PatientBir in DICOMPatients: PatientID = 'NO ID' PatientID = 'NO ID', Old='20061106', New='20070914'
    20070914 09:36:19 Inconsistent PatientSex in DICOMPatients: PatientID = 'NO ID' PatientID = 'NO ID', Old='F', New='M'
    20070914 09:36:20 Inconsistent SeriesTime in DICOMSeries: PatientID = 'NO ID' SeriesInst = '1.2.826.0.1.3680043.2.1208.0001.158.719.093521168' AND SeriesPat = 'NO ID', Old='093522.000000', New='093521.000000'
    20070914 09:36:20 Inconsistent StudyTime in DICOMStudies: PatientID = 'NO ID' StudyInsta = '1.2.826.0.1.3680043.2.1208.093521168', Old='093522.000000', New='093521.000000'
    20070914 09:36:20 Inconsistent SeriesTime in DICOMSeries: PatientID = 'NO ID' SeriesInst = '1.2.826.0.1.3680043.2.1208.0001.158.719.093521168' AND SeriesPat = 'NO ID', Old='093521.000000', New='093524.000000'
    20070914 09:36:20 Inconsistent StudyTime in DICOMStudies: PatientID = 'NO ID' StudyInsta = '1.2.826.0.1.3680043.2.1208.093521168', Old='093521.000000', New='093524.000000'
    20070914 09:36:21 Inconsistent SeriesTime in DICOMSeries: PatientID = 'NO ID' SeriesInst = '1.2.826.0.1.3680043.2.1208.0001.158.719.093521168' AND SeriesPat = 'NO ID', Old='093524.000000', New='093523.000000'
    20070914 09:36:21 Inconsistent StudyTime in DICOMStudies: PatientID = 'NO ID' StudyInsta = '1.2.826.0.1.3680043.2.1208.093521168', Old='093524.000000', New='093523.000000'
    20070914 09:36:21 Inconsistent SeriesTime in DICOMSeries: PatientID = 'NO ID' SeriesInst = '1.2.826.0.1.3680043.2.1208.0001.158.719.093521168' AND SeriesPat = 'NO ID', Old='093523.000000', New='093525.000000'
    20070914 09:36:21 Inconsistent StudyTime in DICOMStudies: PatientID = 'NO ID' StudyInsta = '1.2.826.0.1.3680043.2.1208.093521168', Old='093523.000000', New='093525.000000'
    20070914 09:36:22 Inconsistent SeriesTime in DICOMSeries: PatientID = 'NO ID' SeriesInst = '1.2.826.0.1.3680043.2.1208.0001.158.719.093521168' AND SeriesPat = 'NO ID', Old='093525.000000', New='093522.000000'
    20070914 09:36:22 Inconsistent StudyTime in DICOMStudies: PatientID = 'NO ID' StudyInsta = '1.2.826.0.1.3680043.2.1208.093521168', Old='093525.000000', New='093522.000000'
    20070914 09:37:13 ***Could not find file:0460941-070618\1.3.12.2.1107.5.2.31.30130.3.2007061813233274476217212.0.0.0_0003_000004_11897151730199.v2
    20070914 09:37:14 ***Could not find file:0460941-070618\1.3.12.2.1107.5.2.31.30130.3.2007061813252672129917791.0.0.0_0004_000002_118971517701a5.v2


    ServerStatus.log:
    9/14/2007 9:37:16 AM [CNSDSVR1] UPACS THREAD 14: STARTED AT: Fri Sep 14 09:37:15 2007
    9/14/2007 9:37:16 AM [CNSDSVR1] Calling Application Title : "CNSDSVR1"
    9/14/2007 9:37:16 AM [CNSDSVR1] Called Application Title : "CNSDSVR1 "
    9/14/2007 9:37:16 AM [CNSDSVR1] Application Context : "1.2.840.10008.3.1.1.1"
    9/14/2007 9:37:16 AM [CNSDSVR1] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.2"
    9/14/2007 9:37:16 AM [CNSDSVR1] C-Move Destination: "STKPServer"
    9/14/2007 9:37:16 AM [CNSDSVR1] Number of Images to send: 20
    9/14/2007 9:37:16 AM [CNSDSVR1] ***Could not find file:0460941-070618\1.3.12.2.1107.5.2.31.30130.3.2007061813340287241518516.0.0.0_0007_000019_118971519101d1.v2
    9/14/2007 9:37:16 AM [CNSDSVR1] C-Move (StudyRoot)
    9/14/2007 9:37:16 AM [CNSDSVR1] UPACS THREAD 14: ENDED AT: Fri Sep 14 09:37:16 2007
    9/14/2007 9:37:16 AM [CNSDSVR1] UPACS THREAD 14: TOTAL RUNNING TIME: 1 SECONDS

  • hello, ok, this information bring up a little bit more light onto your issues ...


    1. The log shows inconsistences in the database of conquest. You should rebuild your database with the functions that conquest offers in 'maintenance'.


    2. The log also shows an access right problem for your archive folder (where conquest stores the images). Means, images can't be written to the archive directory by conquest. Make sure Conquest has sufficient rights to write to its archive folder.


    3. Finally, if Conquest can't deliver the file via a C-MOVE because it is not finding it then it is normal that K-PACS can't show it and only shows a black screen. (means, the DICOM C-MOVE transmission failed)
    Bringing up the images via 'filesystem' is a total different kind of accessing the image data and is not releated to the DICOM transmission (using 'database' in K-PACS).



    Hope, this helps.

  • I have rebuilt/"regen'd" my database several times. I have the folder set for everyone to have "full control". Why is conquest not able to find/deliver the file? It is in the "archive" directory which is why I can look it up thru the KPacs filesystem.
    I appreciate the reply, but #1 - rebuild the database. did that and it still happens.
    #2 - access rights - opened the archive directory for full control for everyone and it still happens.
    #3 - I understand that conquest can't deliver the file because it can't find the file. Was there supposed to be some kind of solution here in #3?


    What can I do? Do I write my own application to be an access point for kpacs since that seems to be all that conquest does when it works?

  • Sorry, looks like I can not help you here. It seems to be a problem of conquest.
    I will move this topic into the "Conquest Section" in this forum. Marcel or other users there might be able to help you more than can.


    Regards, Yves

  • Hi!
    As stoneyaway didn't answer anymore I'll take this topic for myself. :)


    We're having this issue when we try to send one study (just this one, the others are fine) from our CR975 (Kodak) to our ConQuest 1.4.14 (Linux - dBaseIII):


    Quote

    Fri May 15 10:14:15 2009 ***Inconsistent PatientBir in DICOMStudies: PatientID = '0874047F' StudyInsta = '1.2.840.113564.101652289.2009042316020532890', Old='19990207', New='20080320'
    Fri May 15 10:14:15 2009 ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '0874047F' StudyInsta = '1.2.840.113564.101652289.2009042316020532890', Old='0898276B', Refused='0874047F'
    Fri May 15 10:14:15 2009 ***Error saving to SQL: 0874047F/1.2.840.113564.101652289.2009042316020532890/1.2.840.113564.101652289.2009042816081478183/1.2.840.113564.101652289.2009042816081478184.2003000225000.dcm


    What could be happening?


    Thank you!


    [ ]s!

    Gustavo F. Caetano
    Technical Coordinator and Biomedical Informatics Specialized Technician
    Image Sciences and Medical Physics Center
    Hospital das Clínicas - FMRP - USP

  • All information of the patient (e.g. name, id, birth date, sex ...) have to be identical within the same study (for all instances with the same study UID). Looks like the birth date "PatientBir" is not.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!