05-27-2015 05:29 AM
Hello,
I have the full LV 2014 Developers Suite installed, and occassionally Citadel 5 (or nictdl.exe as in the process list) starts hogging my CPU and makes my computer unresponsive. I have never run the DSC part of the LabVIEW Suite or used anything that this seems to be tied to Citadel, so I am not sure why it is even starts running in the backrgound. I have tried to find out how to disable it starting - as I am happy to manually re-enable should I ever need it. There doesn't appear to be any obvsious settings in MAX etc. So my options seem to be either use Task manager to stop the service each time it starts to hog my PC, or uninstall DSC which seems a bit drastic.
Thanks,
Andy
Solved! Go to Solution.
05-27-2015 05:55 AM - edited 05-27-2015 05:57 AM
Disable the service in Window Services (or perhaps set to manual startup)? That should stop it from running when your computer boots up - you'll obviously need to re-enable it if you want to use/access Citadel databases (e.g. from DSC module, MAX)
05-27-2015 06:06 AM
Stopping the service only helped until the next reboot, as it automatically started each time. I'd forgotten about the manual startup setting, so I'll try that. I'd have hoped there would be a little check-box somewhere, but providing this improves things I'm not bothered about elegance. Many thanks,
05-27-2015 06:51 AM - edited 05-27-2015 06:52 AM
Not stopping the service - disabling it. If you disable the service from the 'Startup type' it will never run unless you explicitly start it. Setting it to 'manual' should only start the service when needed (but that might happen when you open MAX or something like that) - it'll then remain running until next boot (and then will restart when something tries to access it).
05-27-2015 07:58 AM
Unfortunately setting the NI Citadel 5 service to a "Manual" start, still results in it starting automatically after a reboot!! It must be started by another service. Would be nice to have a simple way of inhibiting this, or only have it start when it is actually used.
05-27-2015 09:15 AM
It's probably because another NI Service tries to access the service at some point during the boot - causing it to start up.
Like I said - the way to inhibit it from starting at all by setting it to 'Disabled'.
05-29-2015 03:20 AM
Sam
You were right, disabling the nictdl.exe service was the only way to prevented it from starting at every boot. Just got to remember I did this should I get around to using that feature!!
Thanks,