Error message should show source of issue and not a generic message

All error message should show source of issues instead a dumb useless message. In general a better error logging that point at least to the function used in which dll would be a great progress.

As sample i add a message from amhooku. The error message is "Cannot write to the HKEY_LOCAL_MACHINE registry hive."

To know what happen a tool must used that logs all file and reg actions from amhook to know which is the key in question. The key here is "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run".

The software should show already all details to solve the issue.
  • Frank Moenkemeyer
  • Mar 19 2019
  • Future consideration
Meridian Server
  • Attach files
  • Jaime Schatz commented
    January 28, 2020 16:49

    Additionally, there are instances when the error message is different when a single document is selected vs. when the "erroring" document is one of many selected in a batch. Users should not have to select file-by-file in order to see what the underlying issue is.

    ×

    Attachments Open full size

  • Wade Hamaliuk commented
    November 04, 2019 23:11

    When a user attempts to edit a document before the document is 'Started' in a workflow they receive this error message:

    • BlueCielo EDM Client Components Library :

    Operation aborted

     

    How about saying, "Before a document may be edited, it must first be 'Started' in a workflow."

    ×

    Attachments Open full size

  • Ronald Kock commented
    September 24, 2019 14:21

    We see errors like: No Storage available,  Catastrophic failure, Serious error, undefined, No such interface supported, RPC error, Server Busy, No MetaData found, XML DCOM, System cannot find the file specified, Invalid Argument, Parameter not found, etc etc

     

    The errors can popup anywhere. In the Configurator / PowerUser / PowerWeb / GCF sync / etc. 

     

    Errors should be handled so the error is presented user friendly to the user and it can help a partner/support to figure out where it is going wrong. Introduce error codes which can tell what the exact error is (KB of error codes). Or at least let the error tells in what client/component to search for. 

    ×

    Attachments Open full size

  • Frank Moenkemeyer commented
    March 26, 2019 06:12

    One more example:

    The publisher job using Autocad shows the message "Wrong AMACAD Version" instead of "Plotter XYZ not found"

    ×

    Attachments Open full size

  • Chris Tsangarides commented
    March 25, 2019 17:56

    Legacy ID: MER-I-116

    Idea created at: 2018-Jul-19

    Referenced customer:

    COMMENTS:

    Aaron Swain Jul 23, 2018 I'd expand on this request and ask that error messages be significantly overhauled as they are generic/vague far too often. For example, I can figure out what "No such interface supported" means, but the users have no idea what that means or what's going wrong.

    ×

    Attachments Open full size

  • +12

Related ideas