Hello,
I Navigated to “ColdFusionBuilder2018\ColdFusion\cfusion\bin” and typed "cfstart" command and it started the server. Do want to see the text comments after I typed in above?
To clarify, I want the ColdFusion server to start automatically when I boot up, I don’t want to have to go to the Command Prompt.
Please let me know if you want the text comments.
Regards,
Kirk
Kirk, here are a few thoughts.
1) First two things:
a) Priyank asked you to do that in order to see any info that might have been shared (back to the console) that might explain your issue. (That said, I don’t think that it will. Your point is not that CF won’t start, but that you don’t see it as a service. I don’t expect that to be explained by what the console log might show.)
b) Still, and more important perhaps: he didn’t ask you to go to ColdFusionBuilder2018\ColdFusion\cfusion\bin. (That is the CF that is installed INSIDE of CFBuilder, which is a relatively new option in the CFB installer. Is that what you mean when you say you “installed CF”?)
Instead, he asked you to go to ColdFusion2018\cfusion\bin. That is the folder where CF gets installed if you install CF itself (as opposed to this CF install option within CFB).
So do you have such a \ColdFusion2018\ folder (with those cfusion\bin folders and more under it)? If you do not, then perhaps you did NOT really install CF the way you always had before. Is that possible?
2) And I have to admit: I have never used that feature to install CF from within CFBuilder, so I don’t know if THAT CF installer DOES create the Windows Services you seek. The “regular” installer certainly does. But I can say that I know that the CF installer within CFB does in fact install CF into that path that YOU have named, ColdFusionBuilder2018\ColdFusion\cfusion….
3) Finally, as for the “servers” feature in CFB that you refer to, where you told it to start the named server using Windows Services, well, that’s just going to TRY to start that server as a service—assuming that it’s been configured to run as a service (like the normal CF installer would do). It will not “configure” Windows Services for that named server.
Someone might want to point out that you COULD setup Windows Services for this “embedded CF” installed within CFB, using the Windows command line sc.exe, but I don’t know how it if will lead to the exact same result as if CF did it. Here’s why: do you have a coldfusionsvc.exe in your cfusion\bin that you point to? Because technically, THAT is what gets configured by CF to start when a CF service starts, and that then turns around and runs the coldfusion.exe. (And perhaps Adobe doesn’t put that coldfusionsvc.exe in there for that embedded installation. That said, if you don’t have that, I suppose it might still work if you pointed the service to the regular coldfusion.exe. It’s easy enough to google to find how to use SC to create a service.
4) But again I really think if you want things to be “like you used to have them”, you may want to consider uninstalling CFB (and confirm that it removes the embedded CF), and then install CF (itself) and then CFB (and tell CFB NOT to create the embedded CF installation).
FWIW, the embedded one (added in CFB 2016, or maybe CFB3) was added as a seeming convenience for those who “just wanted to install CFB and get CF installed in the bargain”. I suppose it may suit some development styles, but I have seen it cause more confusion (like this) than help. But that’s a personal opinion.
Let us know if any of this helps.
/charlie
AdChoices