Thank you for the reply, Sabine.
I run it precisely the same way at 2 other animal hospitals. At the other 2 places, our servers were gradually upgraded from Server 2003 to Server 2008 to Server 2008 R2. Only at this one, where we had to do a fresh install of Server 2008 r2 does KPacs fail to load. All of our "workstations" are thin clients, and thus they use the server for processing.
Any other suggestions?
Thanks, Larry
Posts by drfox
-
-
I have the same problem. KPacs loads in memory, no GUI.
Help, please!
BTW, this is on a fresh install of Server 2008 r2
GUI works fine on server which has been upgraded from an earlier version.
Larry -
Thank you Andreas, yes it was a network issue. It is just very slow. I am now struggling to properly set up Conquest so that it will communicate with my Fuji CR system. I'm neither able to push the images from my Fuji to Conquest, nor pull images from Conquest from my Fuji. I have FCR-View, with veterinary-specific software.
Larry
-
I just installed K-Pacs to a Windows 2008 Server, and I want to have terminals be able to work with images that are stored on a PC attached to the network.
I don't seem to be able to navigate to the networked drive (\\NAS\Dicom\) through K-Pacs, and I can't see the images when I type in the network path. Is this by design or a bug?
Is there a workaround? I have no problem seeing the networked drive through windows explorer.Thanks, Larry