Anyone have any luck getting K-Pacs working on Server 2008 R2? I tried running as admin and using compatability mode, but doesn't launch. The process shows up in task manager, but the program never actually pops up.
K-PACS is a DICOM viewer. It was never intended to run on any Windows server editions. It also makes no real sense to use it on a server as it is a user application that is worked with on a normal workstation under normal user privileges. A user loads images to view them and process them. These are no administrative tasks or tasks that can run unobserved on a server.
So, why would you want to use this application on a server?
Mainly as a place for the DICOM Server to stay running. KPServer runs once K-Pacs has been started once on a normal workstation, but sometimes computers are rebooted and/or shutdown and that turns the DICOM Server off.
On a related note, there were instructions on having the DICOM Server autostart by linking KPautostart to the computer's startup folder, but I cannot find this autostart file anywhere in the installation directory.
I still don't understand why the server component of the K-PACS DICOM viewer needs to be running constantly. You can pull all data you need to view from an archive. Is it possible that you are looking for a DICOM archive instead? If so, you may want to look into ConQuest, which can also be found in this forum.
There is no file called "KPautostart" that I know off. If you want to start a specific application when the computer boots, then you need to add this application's executable into the autostart of the system. In this case the KPServer.exe.
Alternatively, the sub-folder "Server" holds an NTService file. This can be used to provide some kind of pseudo Windows service. This may be used to get the server component to run even though the application itself is not started yet.
The server component is used to send studies from the imaging devices to a computer for long term storage so we don't keep them on the imaging devices themselves. We keep it running all the time mainly for simplicity (techs don't need to deal with a computer at all). The KPautostart thing I mentioned was something I saw in the instructions on the download page, but its probably out of date by now.
"3. To start K-PACS Server on Windows startup, link the file KPautostart.exe in [your K-PACS directory)\K-Pacs-Server] to the autostart directory of the “Start” menu."
I will look into ConQuest, thanks for the suggestion. You are probably right in that there is more appropriate software for the desired job.
In the meantime, I will also look to see if the service idea works too. I'm not sure if adding KPServer.exe to startup will work, because when I run that exe manually, the server doesn't actually stay running, just runs for a split second and turns off. It only stayed running after running K-Pacs itself.
As for it not working on Windows Server directly, I guess I can simply run it from inside a virtual machine as a last resort if I needed to. That computer is basically the only computer guaranteed to stay on, be on, always running etc, hence my desire to run the KPServer process on it over a normal workstation.
We are SPLA hosting provider that provides desktops as a service under spla rules we can only deploy Server OS, also any terminal setup would require the installation be on a Server OS.
That is why we are trying to run it on a server OS.
Yes, it takes some time to appear, but once the W drive shows up using Make.bat, it takes me to the program files, unlike the result of Server_Start.bat.