Coldfusion 2018 Enterprise

marlenkhoo, besides the helpful advice from altascene, I will note that what you are seeing (with that error message, and the "blue ball" icon you don't mention) is the error that CF shows you (from CF10 and above) if one has turned on the "secure profile" feature of CF. That enables about 20 settings in the the CF Admin to be "more secure" than the defaults.

In particular, this "blue ball" (and that error msg you see) is controlled in the CF Admin "settings" page and its "site wide error handler". The Secure Profile sets the value for that field to a CF template that comes with CF, if there is not one put there already by the user (or as may be imported, if the admin import feature is run).

While you could remove it (remove that file and its path) from the CF Admin setting, you should not. That would start causing CF errors to appear on-screen, which is the very security vulnerability that Adobe is avoiding by putting in at least SOME file in that setting.

Instead, note that this Adobe-provided error handler DOES write the "real" error that you got to the CF logs, so check out the cfusion/logs folder in your CF directory, and see the applicaiton.log. If you run your request getting the error, the "real" error message should appear at the bottom of that log. (The application.log values are also duplicated into the coldfusion-out.log, so you will find it there also).

As for what you may find the error to be, it could of course be anything. But once you see it, you may readily recognize how to solve it. Or share it here and we can help. As Altascene indicated, it may simply be that your local dev environment had some CF admin setting that is NOT in place on the prod server. Again, it could be anything (a datasource name, a mapping, and so on). Or there error may have nothing to do with admin settings.

I would suggest that you start by opening the CF Admin screens for both servers, side by side, and setting things up on your Enterprise server like they are on your dev server.  Re-test after that and, if you still see issues on the Enterprise server, move on to checking your web server settings.