When upgrading our GE PACS Centricity 2.1 to version 3.0 we recognized a strange behaviour of k-PACS.
Searching for patients works fine but when trying to retrieve certain studies k-PACS suddenly finds a lot of sequences in the study.
Output of Process-log:
Code
\par [2632] >> : c-find request for StudyInstanceUID: 1.2.276.0.38.1.1.1.4826.20081219173851.14560131 initated
\par \cf0 [2632] >> : c-find result: 2515 sequences in study with UID 1.2.276.0.38.1.1.1.4826.20081219173851.14560131
\par [2632] >> : c-move request for sequence 1.2.392.200036.9125.3.2413913964148.64572580934.117615512 initiated.
\par [DICOM SCU] >> : (0000,0002), 28,\tab UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
\par [DICOM SCU] >> : (0020,000D), 48,\tab UI, "1.2.276.0.38.1.1.1.4826.20081219173851.14560131" - Study Instance UID
\par [DICOM SCU] >> : (0020,000E), 58,\tab UI, "1.2.392.200036.9125.3.2413913964148.64572580934.117615512" - Series Instance UID
\par \cf0 [STORE SCP] >>22.12.2008 12:21:44: receiving image from AET "GEPACS" with UID 1.2.392.200036.9125.9.0.252225841.3321888960.755371825 successful (LittleEndianExplicit)
\par [STORE SCP] >>22.12.2008 12:21:46: receiving image from AET "GEPACS" with UID 1.2.392.200036.9125.9.0.135230889.597432320.2341180480 successful (LittleEndianExplicit)
Then k-PACS tries to retrieve the 2515 sequences which takes a lot of time and always seems to be the same image. The mentioned study only contains one image.
When trying to retrieve CT-studies the same thing happens and from the process-log one can conclude that k-PACS tries ti receive the scout image 2000 times.
Any clue what happens here. The problem exists for the rather old version 1.0 as well as for 1.6 versions on a Windows XP SP2 machine.