Here are a collection of hints that may help resolve some unexplained or otherwise troubling automation issues.
In order to control other server applications, CCDAutoPilot must be able to link to those applications through Window's automation interface. variously called ActiveX or COM (Common Object Model). With Windows versions later than XP, 12 years old as of this writing, Additional security has been added that may prevent this inter-application communication. First off, make sure you are logged into Windows as administrator. Next, when a server application is first run, be sure to right click on it and choose Run As Administrator. This generally needs to be done only once and should then allow the COM interface to function. In some cases, you may need to set the User Account Control to its minimum setting (search the Control Panel for this setting. Reboot is generally required).
Windows has a default setting to update windows around 3 AM local time. In many cases, the update process will result in a reboot - not a good thing for automation. Thus it is not a good idea to leave this default setting. In Windows control panel, Windows Update, select Download Updates but let me choose when to install them. That way you can keep up-to-date but you decide when to install updates.
Make sure you have sufficient RAM for your computer. A minimum of 3 GB, 4 GB recommended should be sufficient for CCDAutoPilot and the normal collection of server applications.
If you are using any USB connections to your equipment, make sure USB power management is disabled. In Windows 7, this is buried in Control Panel/Power Options/Change Plan Settings/Change Advanced Power Settings/USB Settings/USB Selective Suspend Setting/Disable. Then apply.
It is generally a good idea to not do anything else with the computer while running an automated session. This is especially important with modest processor or memory computers.