Advanced Pack/Reports: Error 500

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tobias
    Senior Member
    • May 2016
    • 229

    Advanced Pack/Reports: Error 500

    Hi there,

    We've just recently upgraded to Advanced Pack 1.33.8 and get the following errors since:
    Code:
    [Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (exportList, line 0)
    [Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (getEmailAttributes, line 0)
    The first error occurs when trying to export a Report, the latter when trying to e-mail a report.

    What could be the issue here?
  • yuri
    Member
    • Mar 2014
    • 8453

    #2
    Hi,

    Anything in EspoCRM logs?
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • tobias
      Senior Member
      • May 2016
      • 229

      #3
      Hi Yuri,

      Thanks for your quick reply. Nope, today's log is empty.

      Comment

      • yuri
        Member
        • Mar 2014
        • 8453

        #4
        Could you install a previous version to make sure the error doesn't occur there?

        The error message must be somewhere in logs.
        If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • yuri
          Member
          • Mar 2014
          • 8453

          #5
          Maybe you upgraded something on your server? Check Administration > System Requirements.
          Last edited by yuri; 02-19-2019, 09:04 AM.
          If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

          Comment

          • tobias
            Senior Member
            • May 2016
            • 229

            #6
            Thanks so much, Yuri. The problem was indeed a failed system requirement, xmlwriter wasn't installed.

            Comment

            Working...