Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
In cases that a project does not start or shut down properly, it is advised to check the processes. In the case the project did not shut down properly, the process can be killed manually using Windows Task Manager. This way upon a restart of Runtime Manager, the project starts without any problem.
The example below shows a project with six I/O Servers (numbered 2, 4, 6, 8, 10 and 12), a Trend Server, one Alarm Server and a Client (represents the main project); a total of 9 processes as shown in Runtime Manager.
The processes above can be verified in Windows Task Manager as shown below. There is an entry for each of the above 9 processes, each labeled Citect32.exe *32. Note the one-to-one correspondence among the Process IDs in Task Manager and Process IDs in Runtime Manager. For example PID 22716 in Task Manager corresponds to IOServer6 as show in the above picture.
In case PowerLogic Scada application is open for editing a project, there will be three additional processes. Process names and their corresponding application are shown below:
CtDraw32.exe *32 Citect Graphics Builder
CtEdit32.exe *32 Citect Project Editor
CtExplor.exe *32 Citect Explorer
Sign up for all the latest solutions, offers and best practices straight to your inbox.
We are excited that you have joined the group. You will receive your welcome email soon describing the program and what to expect in the upcoming weeks. Enjoy!