ReportViewer responds with 502 error after it times out











up vote
1
down vote

favorite












We have been building reports for SSRS 2016. Reports that execute in under 2 minutes work fine. However, we have some remotes that need well over 10 minutes.



However, when executing the report it times out after about 2 minutes and returns this error:



Sys.WebForms.PageRequestManagerServerErrorException: An unknown error 
occurred while processing the request on the server. The status code returned
from the server was: 502


I tried setting the execution timeout in web.config



<httpRuntime executionTimeout="2147472000" maxRequestLength="2147483647" />


I also tried setting the ScriptManager's timeout



 ScriptManager scriptMan = ScriptManager.GetCurrent(this);
scriptMan.AsyncPostBackTimeout = 10800;


Unfortunately, none of that solved the issue. Any help would be appreciaated.
Thanks guys.










share|improve this question







New contributor




Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
























    up vote
    1
    down vote

    favorite












    We have been building reports for SSRS 2016. Reports that execute in under 2 minutes work fine. However, we have some remotes that need well over 10 minutes.



    However, when executing the report it times out after about 2 minutes and returns this error:



    Sys.WebForms.PageRequestManagerServerErrorException: An unknown error 
    occurred while processing the request on the server. The status code returned
    from the server was: 502


    I tried setting the execution timeout in web.config



    <httpRuntime executionTimeout="2147472000" maxRequestLength="2147483647" />


    I also tried setting the ScriptManager's timeout



     ScriptManager scriptMan = ScriptManager.GetCurrent(this);
    scriptMan.AsyncPostBackTimeout = 10800;


    Unfortunately, none of that solved the issue. Any help would be appreciaated.
    Thanks guys.










    share|improve this question







    New contributor




    Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      We have been building reports for SSRS 2016. Reports that execute in under 2 minutes work fine. However, we have some remotes that need well over 10 minutes.



      However, when executing the report it times out after about 2 minutes and returns this error:



      Sys.WebForms.PageRequestManagerServerErrorException: An unknown error 
      occurred while processing the request on the server. The status code returned
      from the server was: 502


      I tried setting the execution timeout in web.config



      <httpRuntime executionTimeout="2147472000" maxRequestLength="2147483647" />


      I also tried setting the ScriptManager's timeout



       ScriptManager scriptMan = ScriptManager.GetCurrent(this);
      scriptMan.AsyncPostBackTimeout = 10800;


      Unfortunately, none of that solved the issue. Any help would be appreciaated.
      Thanks guys.










      share|improve this question







      New contributor




      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      We have been building reports for SSRS 2016. Reports that execute in under 2 minutes work fine. However, we have some remotes that need well over 10 minutes.



      However, when executing the report it times out after about 2 minutes and returns this error:



      Sys.WebForms.PageRequestManagerServerErrorException: An unknown error 
      occurred while processing the request on the server. The status code returned
      from the server was: 502


      I tried setting the execution timeout in web.config



      <httpRuntime executionTimeout="2147472000" maxRequestLength="2147483647" />


      I also tried setting the ScriptManager's timeout



       ScriptManager scriptMan = ScriptManager.GetCurrent(this);
      scriptMan.AsyncPostBackTimeout = 10800;


      Unfortunately, none of that solved the issue. Any help would be appreciaated.
      Thanks guys.







      iis reporting-services reportviewer ssrs-2016






      share|improve this question







      New contributor




      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked Nov 4 at 9:40









      Khaled Abul Borghol

      61




      61




      New contributor




      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Khaled Abul Borghol is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          There are several different timeouts in play when you run a report including the viewer control, the report server, and your source database. Keep in mind that waiting over 10 minutes each time you want to run a report is not an ideal experience.



          Instead, I would suggest looking into caching the report on a schedule. You can set this up in the report processing options on your report server. You can choose to have the cache refresh once a day for example. This way, when a user decides to run the report, it will load much faster.



          Reports do not have the same timeout limitations when refreshing a cache. And since the cached report renders more quickly, you don't have to adjust any timeout settings. This also provides a better user experience.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });






            Khaled Abul Borghol is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53139450%2freportviewer-responds-with-502-error-after-it-times-out%23new-answer', 'question_page');
            }
            );

            Post as a guest
































            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            There are several different timeouts in play when you run a report including the viewer control, the report server, and your source database. Keep in mind that waiting over 10 minutes each time you want to run a report is not an ideal experience.



            Instead, I would suggest looking into caching the report on a schedule. You can set this up in the report processing options on your report server. You can choose to have the cache refresh once a day for example. This way, when a user decides to run the report, it will load much faster.



            Reports do not have the same timeout limitations when refreshing a cache. And since the cached report renders more quickly, you don't have to adjust any timeout settings. This also provides a better user experience.






            share|improve this answer

























              up vote
              0
              down vote













              There are several different timeouts in play when you run a report including the viewer control, the report server, and your source database. Keep in mind that waiting over 10 minutes each time you want to run a report is not an ideal experience.



              Instead, I would suggest looking into caching the report on a schedule. You can set this up in the report processing options on your report server. You can choose to have the cache refresh once a day for example. This way, when a user decides to run the report, it will load much faster.



              Reports do not have the same timeout limitations when refreshing a cache. And since the cached report renders more quickly, you don't have to adjust any timeout settings. This also provides a better user experience.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                There are several different timeouts in play when you run a report including the viewer control, the report server, and your source database. Keep in mind that waiting over 10 minutes each time you want to run a report is not an ideal experience.



                Instead, I would suggest looking into caching the report on a schedule. You can set this up in the report processing options on your report server. You can choose to have the cache refresh once a day for example. This way, when a user decides to run the report, it will load much faster.



                Reports do not have the same timeout limitations when refreshing a cache. And since the cached report renders more quickly, you don't have to adjust any timeout settings. This also provides a better user experience.






                share|improve this answer












                There are several different timeouts in play when you run a report including the viewer control, the report server, and your source database. Keep in mind that waiting over 10 minutes each time you want to run a report is not an ideal experience.



                Instead, I would suggest looking into caching the report on a schedule. You can set this up in the report processing options on your report server. You can choose to have the cache refresh once a day for example. This way, when a user decides to run the report, it will load much faster.



                Reports do not have the same timeout limitations when refreshing a cache. And since the cached report renders more quickly, you don't have to adjust any timeout settings. This also provides a better user experience.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 2 days ago









                StevenWhite

                4,37021036




                4,37021036






















                    Khaled Abul Borghol is a new contributor. Be nice, and check out our Code of Conduct.










                     

                    draft saved


                    draft discarded


















                    Khaled Abul Borghol is a new contributor. Be nice, and check out our Code of Conduct.













                    Khaled Abul Borghol is a new contributor. Be nice, and check out our Code of Conduct.












                    Khaled Abul Borghol is a new contributor. Be nice, and check out our Code of Conduct.















                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53139450%2freportviewer-responds-with-502-error-after-it-times-out%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest




















































































                    這個網誌中的熱門文章

                    Xamarin.form Move up view when keyboard appear

                    Post-Redirect-Get with Spring WebFlux and Thymeleaf

                    Anylogic : not able to use stopDelay()