Open Forum

Expand all | Collapse all

Smartlist adobe reader error

  • 1.  Smartlist adobe reader error

    Posted Aug 14, 2019 10:30 AM
    end user cannot export info into Excel from smartlist - giving an 'Adobe Reader' error

    "Adobe Reader could not open '20190814-1234.xlsx' because it is either not a supported file type or because the file has been damaged."

    She's telling me now that this happens periodically

    Any helpful tips for this?

    Deanne Rasmussen
    Houston TX

  • 2.  RE: Smartlist adobe reader error

    Posted Aug 14, 2019 02:22 PM
    My first thought is that Adobe Reader has been assigned as the default application for files with extension .xlsx on one of the terminal servers, assuming this is in a ts environment. It would explain why it doesn't happen all the time.

    Mark LeRette
    Application System Analyst II
    Muscatine Power and Water
    Muscatine IA


  • 3.  RE: Smartlist adobe reader error

    Posted Aug 15, 2019 08:48 AM
    I agree with Mark that you need to check the default app, but I have seen intermittent errors like this from Excel opening a SmartList also.
    If it doesn't happened every time I recommend looking for SmartList data issues.

    Now this can get tricky to check, but I have seen two potential issues that can cause Export to Excel errors like "...file has been damaged."
    • Custom SQL SmartLists with Null field values choke on "Export to Excel".
                In any custom SQL I make sure to use a SQL Coalesce or ISNULL to replace NULLS.

    • Data with non-printing characters.  
               Either from data imported into GP from an outside source, or from someone doing a cut and paste into a GP field, these non-printing characters may or
               may not display in the SmartList, but will choke the SmartList to Excel export every time. Sometimes you may see a little box or extra spaces,
               sometimes not.

    How to isolate the "Bad" data? Set filters on your SmartList data, cutting it in half. If one half runs and exports, but the other half doesn't, then you have narrowed the search to half the results. Repeat until you find the (hopefully) one row with bad data. Especially look at comment fields; a common place that GP users paste into from Word, etc. Fix that data either in GP or have your SQL Admin do it, and you should be good to go.

    David Morinello
    Senior Dynamics GP Systems Architect
    Ascend Learning, LLC
    Leawood KS


If you've found this thread useful, dive deeper into User Group community content by role