Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Status 500 in DevTools when PDF Report takes longer than 2 minutes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Status 500 in DevTools when PDF Report takes longer than 2 minutes

    How do I make the IIS Alpha server give more time to an IIS Worker Process?
    Is there a configuration option in IIS or Alpha that I am overlooking or do I need a build newer than 5581?


    In the browser DevTools console panel, I receive status 500 if a report take longer than about 2 minutes to generate its PDF output.

    The response message begins as:
    Server Error in '/' Application.
    Request timed out.

    - Rich Fulham


    #2
    This is from the latest release of Alpha (8245. Might be what you are looking for.

    UX and Grid Components - Reports - Chunked Responses - Show Progress -Cancel - When you use Action Javascript to print a report to PDF, you can now turn on chunked responses and you can display progress as the report is printing. You can also enable a button to cancel the report.

    If you display a report that takes a long time to print, it is possible that the client (i.e. the browser) will time out before the server has completed the report. When the server eventually completes the report, if the client has timed out, the report will not be displayed. This problem can be solved by turning on the chunked reports option. This will ensure that the client continues to listen for a response from the server past the time that it would otherwise have timed out.

    In addition, if you turn chunked responses on, you can display progress messages as the report is printing. This will keep the user informed of progress while the report is printing. You can also display a button to cancel the report.

    Comment


      #3
      I would think you have a few options.
      The first thing is to determine why the report is taking so produce. If it's fixable, fix it.
      If it's not fixable, maybe create a method where your app will email the report to the user
      when it's ready (Microsoft does this often).
      Gregg
      https://paiza.io is a great site to test and share sql code

      Comment


        #4
        Thank you Rusty, that may very will correct the issue.
        But, at the moment it sounds like my Reports might break if I upgrade AA IIS.

        At the moment my reports take longer than two minutes to generate if they contain more than about 50 pages and, as I mentioned, IIS seems to send "Error 500 - Request timed out" at the two minute mark. Even though the IIS Application Pool has been configured to not ping the worker processes. Even if IIS were to ping them it has been set to wait 900 seconds before deciding the worker process has timed out and I've set the site connection timeout to 3600 seconds.

        The built-in IDE Dev Server can run these reports just fine, as it doesn't care how long the report takes to process. I am wondering if I can export my reports to a desktop version and have that run on the server to generate my reports. All I need to do is get hundreds of these reports generated so the user can get all their data into PDF for long term storage / retention outside of this application.

        Comment


          #5
          Madtowng,
          Okay, I am trying out the option to email the generated PDF.

          The reports may run slower than other people's reports because I use a lot of conditional formatting to show/hide various fields.

          Comment


            #6
            SOLVED: There are multiple places in IIS that deal with "Timeouts", but the one place I had over looked is:

            "Sites" / your_site_name //// "Configuration Editor" / "executionTimeout"

            It had been set to 00:01:50 = 1 minute, 50 seconds.

            I knew from watching the IIS Worker Process(es) in Task Manager that I needed up to 4 minutes for a particular report to finish. So, I set it quite a bit larger than that.

            Other places to look for timeout values are under:
            "Application Pools" / your_app_pool_name // "Advanced Settings..." { whole bunch of things you can set on this page! }
            "Sites" / your_site_name / / Limits...

            Comment

            Working...
            X