We have received few incidents wherein users were not able
to start ColdFusion services after server reboot or while restarting the
services manually.

Reason:

Applications dynamically generate ColdFusion files and
sometimes also deletes them, but ColdFusion does not remove any old files from
the cfclasses folder.

{cf.root}/cfusion/wwwroot/WEB-INF/cfclasses

If you have a huge number of websites on one ColdFusion
server, it creates thousands of cfclasses depending on number of incoming
requests.  

Solution:

Deleting all the class files of cfclasses folder and
restarting the ColdFusion server.

If you are unable to delete the files, rename cfclasses
folder and create an empty cfclasses in the same location.

To avoid such issues in future, you can manually delete
class files at regular time intervals.

If you do not wish to save the class files, you can disable
this feature in administrator from Server
Settings > Caching

 Save class files 
When you select this option, the class files
generated by ColdFusion are saved to disk for reuse after the server restarts.
Adobe recommends this for production systems. During development, Adobe
recommends that you do not select this option.