Generic Error: "CMN3101E The system is unavailable due to "CMN1086E"."



  • I clicked on a link (from http://www.ladyada.net/library/equipt-kits.html#basic) to a [url=http://www.jameco.com/webapp/wcs/stores/servlet/ProductDisplay?langId=-1&storeId=10001&catalogId=10001&productId=116572v]product page for a soldering iron[/url], and got this error:


    Generic Error
    The store is currently experiencing problems. Try again later.

    Store developers:
    To view detailed error information, see the comments in the HTML source for this page. Exception Type: 1
    Message Key: _ERR_DIDNT_SET_PRODUCT
    Message: CMN3101E The system is unavailable due to "CMN1086E".
    System Message: The product reference number attribute of the command was not set.
    Originating Command:
    Corrective Action:



    I especially like that helpful message: CMN3101E The system is unavailable due to "CMN1086E".



  • Okay, that's stupid.  A better solution is to log all that crap, and give the user a more friendly (if not helpful) message.  For example, "We are unable to process your request due to an internal system problem.  We saved some information about the error, but if you'd like to contact us with more, use the error reference BLAH-BLAH-BLAH."  where the reference is some unique per-incident id that got logged along with the error information.  If you actually want them to contact you (AOT just wanting to make nice), the "contact us" part can be a link.

    Dumping the actual technical details to the user is a total waste of time and users' brain cells.  Those are in short supply.
     



  • Bizarrely enough I just got a very similar message when ordering a bike on the Halfords website...

    CMN3101E The system is unavailable due to "CMN0412E".

    Simultaneously I got a text message confirming the order...



  • @junkman said:

    snip necromancy
    Dead thread, RISE FROM YOUR GRAVE!



  • @bstorer said:

    Dead thread, RISE FROM YOUR GRAVE!
    No U!



  • Yah, hence the WTF.. that after all this time the same random error is reproduced in a completely different location years later....

     *sigh*


Log in to reply