Is it possible to configure REST to dump error information in the response when hitting a 500 server error? The default seems to be “Sorry! Something went wrong. Please contact your system administrator.”
Though pulling the actual error from the server logs is possible, I’d love to have some control over this.
@josephmoeller did you put some spyware on my box? I literally asked this exact same question of @Olga yesterday … runs antivirus
Changing that setting does work
@Olga, again, thank you! This did work for me immediately! @josecgomez ha! That would be a good trick! nothing to see here… (exec spywareuninstall.exe @target?ipjosecgomez)
Yep, this should reload the settings into the application running on IIS. I think a stop/start of the app pool might do this, too, to avoid the full iisreset per @aidacra but depending on your version, I’ve seen issues with this working as expected.
And honestly, this should only be done on Dev instances. Sending error messages to a client is a dangerous security practice. The better solution is logging to a place that is available by the dev.
Aaaaand, that is a part of the DevOps Epicor Idea. So vote if you want to…
We just started getting this error in all of our environments. It just so happens that the day it started we installed 2022 on our TEST server, which is isolated from LIVE. However, we are also getting the errors in LIVE. Was anyone able to determine what caused this, or how to fix other than suppressing the error.
Note - this is out of the box CPQ, nothing crazy/custom. I assume Epicor does not like something in the data that CPQ is trying to post, but I have no idea what. The appserver logs give me a stack trace, but it’s giving me nothing to work with in identifying what’s wrong:
Thanks, yeah, I realized that after posting that the failure is actually happening while Epicor server code tried to communicate with KBMax… So my only hope is Support being able to see something on their servers.