Enable Robust Reporting

[hamackey]

Server 2012

IIS

CF2016

1. Comments on stackexchange seem to indicate I need to mod cgi.path_ info. Is this true? Where is this file?
2. Can robust reporting be enabled on a test server with no license? I have a license for the production server.

Thanks,

Harry

[WolfShade]

Log on to CFAdmin

From left panel, expand "DEBUGGING & LOGGING"

Click on Debug Output Settings

Put a check in box for Enable Robust Exception Information

Click "Submit Changes" button in upper-right corner of page

From left panel, click Debugging IP Addresses

Make sure the IP address of your computer is in the list

If not, add the IP address of your computer to the list

HTH,

^_^

[hamackey]

Thank you, it does appear that robust reporting is enabled, however, despite adding the ip addresses of the developers to the list, the only way the can see the debug output is on the server using the installed browser.

Still cannot see why a local pc cannot see this. Firewall is off. I used three browsers.

[hamackey]

In addition to following the instructions above, you also need to uncheck this setting on your test server.

Check your "enable http status codes" setting under server settings > settings in the CF administrator. http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSc3ff6d0ea77859461172e0811cbf3638e6-7ffc.html

When CF sets a 500 status code on error IIS sees this and responds with its error page.

While unchecking this option will technically solve your issue the real solution would be to modify IIS' settings so that it serves up your desired error page. You shouldn't be sending coldfusion's error pages to users on a production site

[WolfShade]

hamackey wrote:

When CF sets a 500 status code on error IIS sees this and responds with its error page.

While unchecking this option will technically solve your issue the real solution would be to modify IIS' settings so that it serves up your desired error page. You shouldn't be sending coldfusion's error pages to users on a production site

You should create a generic error page that does not divulge any information to the user, and have the error message(s) sent to the developers via CFMAIL (type="HTML" and the body should be CFDUMP of the exceptions - or the cfcatch if you are using cftry.)  In CFAdmin, you can set that page as the default error page, AND set up a function in application.cfc for the onError() event.

If the developers are using IE, there is an IE setting that will show "friendly error messages" (ie, no real information) or the standard error messages (ie, the cause of the error.)

But if the CFAdmin has the right boxes checked and the right IP addresses in the list for displaying robust information, then double-check your application.cfc to make sure that there isn't a CFSETTING for not showing debug output.  Even after 17 years of CF coding, that one still kicks my butt, on occasion. 

HTH,

^_^