CM needs better error reporting: "FSY0004611E Error: Cannot open file... DMN4510112W Warning: Deleting partially written file..." Hot

https://serenacentralphotos.s3.amazonaws.com/original/37/8c/97/CM2014320error20message20improved20-2010-03-2016-47-1475505180.png
by Joshua Trosclair on March 03, 2016

The error is in "English", but may as well be in another language. The end user is none the wiser from reading the error and us system administrators have to put on our "investigator" hat to deciper yet another ambiguous Dimensions CM error message. That error appears when a user tries to download a file from the CM web client when the item library file does not exist on the CM server.

  • Some of us sys admins have cases where we copy a CM base database from our production to our test/dev environments that are mirrored (mostly) to our production environments (for testing/training/dev, etc). My item libraries are often too large to place on a dev/test environment, so I don't copy them over all the time. If a user goes to my test environment and tries to get a file that shows up in the CM web client, but isn't on the CM server's item libraries, an error like this appears:

    "FSY0004611E Error: Cannot open file D:product_libMFOMATMsrcabout-05.aspx-5601378_4 - No error (error=0)
    DMN4510112W Warning: Deleting partially written file D:ServersTomcatworkCatalinialocalhostdimensionsmwisbx6167.dir/587zq96168.tmp"

    If I had a say in the error reporting, the error would look like this instead:
    "Cannot find file. Please have your system administrator check to see if the file exists in this directory on the server: D:product_libMFOMATMsrcabout-05.aspx-5601378_4
    System administrator can be reached at this email address: sysadmin@mail.com"

    Not only does the 'modified' error message tell me what is wrong; I have the email address of who I need to contact about the issue. From there, the user has no "laziness" excuse to not notify me of the issue. 

     

    Ideas

    Status
  • Please login to view any attachments.

  • Cool, that's good to hear.
    Thinking things over again, it seems to me that, the admin email address idea can be a good or bad feature to have; there are some error messages that I would prefer the CM POC(point of contact) for a customer group to be contacted first... before bringing me into a what is a matter of a 'training' issue that the CM POC is responsible for. I have over a dozen CM base databases with many customer organizations, so it probably would be overbearing for me to receive everyone's emails. Yet, if the error messages were written so that they are understandable by the end user, perhaps the email idea wouldn't be needed as much.
    If there was an admin email address specified per base database, I imagine I would likely set a different CM POC per base database, and then have those POCs forward cases to my CM administration team for issues that the CM POCs can't handle.... basically a 2-tier support structure.
    Joshua Trosclair Commented by Joshua Trosclair March 07, 2016
    Top 50 Reviewer  -  

    Cool, that's good to hear.
    Thinking things over again, it seems to me that, the admin email address idea can be a good or bad feature to have; there are some error messages that I would prefer the CM POC(point of contact) for a customer group to be contacted first... before bringing me into a what is a matter of a 'training' issue that the CM POC is responsible for. I have over a dozen CM base databases with many customer organizations, so it probably would be overbearing for me to receive everyone's emails. Yet, if the error messages were written so that they are understandable by the end user, perhaps the email idea wouldn't be needed as much.
    If there was an admin email address specified per base database, I imagine I would likely set a different CM POC per base database, and then have those POCs forward cases to my CM administration team for issues that the CM POCs can't handle.... basically a 2-tier support structure.

    "Hi Joshua, We will change the wording to be more understandable. We will also consider saying something like "Please contact your Dimensions CM administrator" We cannot include the email address because we don't specifically store an admin username anywhere. This is targeted for our next release, 14.3, which is due late spring/early summer.
    Lee  Lewell Commented by Lee Lewell March 07, 2016
    Top 50 Reviewer  -  

    "Hi Joshua, We will change the wording to be more understandable. We will also consider saying something like "Please contact your Dimensions CM administrator" We cannot include the email address because we don't specifically store an admin username anywhere. This is targeted for our next release, 14.3, which is due late spring/early summer.

    Lee  Lewell Commented by Lee Lewell March 06, 2016
    Top 50 Reviewer  -  
     

PrintEmail