can't transfer case from one kpacs install to another

The log does not show any errors. Maybe you should check the receiving station for errors instead. Maybe you don't have permission to write in the database folder. Or a firewall prevents the transfer. Or the database/imagebox is not correctly configured. Or the UIDs of the study are too long and the database path too deep in the Windows folder structure, so that the allowed number of characters is exceeded and the objects cannot be stored.

thank you for the reply.

how do i find the log of the receiving station ?

so i can check it for errors ?

Use the verbose mode option in the server admin tool. Activate the option, best increase the number of displayed lines in the command prompt window and then repeat the sending of the data.

The log options are much, much nicer in iQ-VIEW, though.

thank you for reply
I will give that a go.
also my test image may be bad.
it is the only dicom I have.
I am retired radiologist age 73
I will look for test dicoms both on image-systems biz and google.
best regards

alan white md

ps
I will t

We offer lots of DICOM studies in our Download Center. Just log in with the same login data you use for this forum. And then check out the section "Demo Images".

thank you for reply.

i downloaded kpacs samples and used lung abscess demo 166 to test.

still not able to transfer to another kpacs.

not able to find verbose mode checkbox. did following. another install windows 7 pro. another install kpacs v 1.0.1. install conquest 14d.

i was able to transfer lung abscess demo 166 to conquest but could not view image ther in conquest.

but i was able to transfer from conquest head 101 to kpacs and view it there.

log from conquest of transfer of lung abscess from kpacs to conquest

CONQUESTSRV1] Monitoring for files in: C:\dicomserver\Data\incoming\
[CONQUESTSRV1] DGATE (1.4.17d, build Sun Mar 09 14:18:24 2014, bits 64) is running as threaded server
[CONQUESTSRV1] Database type: built-in SQLite driver
[CONQUESTSRV1] User interface test: local server is running!
[CONQUESTSRV1]
[CONQUESTSRV1] UPACS THREAD 1: STARTED AT: Sun Nov 09 06:09:08 2014
[CONQUESTSRV1] Calling Application Title : "KPSERVER"
[CONQUESTSRV1] Called Application Title : "CONQUESTSRV1"
[CONQUESTSRV1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384
[CONQUESTSRV1] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.1" 1
[CONQUESTSRV1] Written file: C:\dicomserver\Data\Demo166\1.3.46.670589.30.1.3.1.1625066929.1215677599328.1_0001_000001_14155421510000.dcm
[CONQUESTSRV1] UPACS THREAD 1: ENDED AT: Sun Nov 09 06:09:11 2014
[CONQUESTSRV1] UPACS THREAD 1: TOTAL RUNNING TIME: 3 SECONDS
[CONQUESTSRV1]
[CONQUESTSRV1] UPACS THREAD 2: STARTED AT: Sun Nov 09 06:09:11 2014
[CONQUESTSRV1] Calling Application Title : "KPSERVER"
[CONQUESTSRV1] Called Application Title : "CONQUESTSRV1"
[CONQUESTSRV1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384
[CONQUESTSRV1] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.1" 1
[CONQUESTSRV1] Written file: C:\dicomserver\Data\Demo166\1.3.46.670589.30.1.3.1.1625066929.1215677603109.1_0002_000001_14155421550001.dcm
[CONQUESTSRV1] UPACS THREAD 2: ENDED AT: Sun Nov 09 06:09:15 2014
[CONQUESTSRV1] UPACS THREAD 2: TOTAL RUNNING TIME: 4 SECONDS

all suggestions greatly appreciated.

alan

Why are you using such an old version of K-PACS? The current version is 1.6.0. Might be that the verbose mode of the server did not even exist in that version you are using.

v 1.0.1 is only version i have used for years.
i will download 1.0.6 and install it.

thank you for reply
alan white

oops 1.6.0

I have downloaded 1.6.0 and will try it out

i installed 1.6.0 and put a check in the checkbox verbose mode of the server.

then stopped server then started server . i got an empty black box on the screen.

where is the error cod stored ?

follow up. after i clicked verbose mode i clicked stop kpserver then start kpserver and got blank black box on screen. maybe an hour later there is about 20 lines of text in the box. how can i capture that text to send to you ?

thank you

Of course, the command prompt is empty at first. It captures the actions when they happen. So, after you start the verbose mode, you repeat the actions that led to the erroneous behavior and the log will be written in that box. Afterwards you can check the log for errors or any indication of what the issue might be. You may also use the options of the command prompt to copy and paste the log elsewhere.

Since DICOM logs can get really long, make sure to extend the size of the command prompt window beforehand, i.e. especially the number of lines that will be maintained in the prompt.

thank you for reply

"the command prompt is empty at first. It captures the actions when they happen. So, after you start the verbose mode, you repeat the actions that led to the erroneous behavior and the log will be written in that box. Afterwards you can check the log for errors or any indication of what the issue might be. You may also use the options of the command prompt to copy and paste the log elsewhere.
Since DICOM logs can get really long, make sure to extend the size of the command prompt window beforehand, i.e. especially the number of lines that will be maintained in the prompt."

i understand.

the black box works if trying to access kpacs from conquest, but can't use kpacs

Well, this would mean that the sending K-PACS is not even trying to communicate with the receiving K-PACS. Otherwise the server component of the receiving K-PACS would at least get an association request, which would be logged in the command prompt window.

thanks for reply. i will reinstall. if tht helps, i will repost.