Discussions
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Diagnosing Unexpected Errors
Simple question. When a web service (or I suppose anything else for that matter) returns an "Unexpected Error" and provides an Error ID, is there any way to get more information about what's wrong? My experience with web services has been very frustrating because anything but the most trivial mistakes are punished with these useless responses, and I end up spending most of my time on trial/error debugging.
I apologize if this question has been answered already, but as you might imagine, searching the forums for "unexpected error" produces an epic list of threads. Reviewing a few samples suggests that further detail exists, but that the only way to find out the nature of the failure is to file a ticket with support, which as a rather serious problem for a "self-service" customer. I would expect paid support customers to be annoyed as well, given my experience with the availability and responsiveness of support.