Current filter:
                                You should refresh the page.
                                  • Hi team,

                                    After the Google Chrome update 76.0.3809.132 of September 10th, the Print Report button of every of our Web Sites are no longer working.

                                    The workaround we have found is to export the report to PDF then print the PDF file afterward.

                                    Are you aware of this issue and would it be possible to be fixed? Is this change of Google Chrome will prevent this functionality for ever working again?

                                    Regards.

                                Show all comments
                                • Mauro Porpino 09.11.2019

                                  Hi,

                                  We have the same problem here after the Google Chrome update 77.0.3865.75.

                                • Federico José Picado 09.11.2019

                                  Hello

                                  We have the same issue when we updated Chrome to Version 77.0.3865.75 . We use the Document Viewer control of version 19.1.4 of ASP NET MVC.

                                • Episode Developpers 09.11.2019

                                  Hi Federico,

                                  We have tried your suggestion, however it wasn't a success. The buttons are still unresponsive, sadly.

                                • Cory Haibloom 09.11.2019

                                  We are also seeing the same thing.  In addition, the WebDocument viewer opens the .axd page but doesn't automatically bring up the print dialog. You must then actually click the print button on the .axd screen for the dialog to appear.

                                • Customer77262 09.11.2019

                                  I have the same issue after update Chrome, I tried different ways to solve the problem but I can't get the solution . . .  any suggestions?

                                • Yaroslav (DevExpress Support) 09.11.2019

                                  Hi Everyone!

                                  I confirm that we see the issue on our side as well. We're looking into it and will update this ticket once there is any results to share.
                                  If you're running any version higher than v15.1, you can avoid this printing issue today by replacing the old viewer with the new one: What is the difference between ASPxDocumentViewer (ReportViewer) and ASPxWebDocumentViewer.

                                  Some background explanation:
                                  While the old viewer provides a desktop-like experience by printing an invisible iFrame element, this solution (and its various variations) do not produce a consistent result across browsers. Sometimes, it simply does not work at all:  Partial display of pdf in iframe of iOS browser. All those cases make users wonder what is wrong with the viewer and why it does not print. That is the exact reason why new viewer opens a separate tab for printing.

                                  If for any reason you're unable to update your application and/or use ASPxWebDocumentViewer in your application, please let us know in the comments section below.

                                • Alexandr Polyanin 09.12.2019

                                  Hello! Our users are actively using Print Report feature and we are unable to upgrade to versions higher than v15.1.
                                  What can you suggest as a possible workaround? Thank you.

                                • Anthony Taieb 09.27.2019

                                  Hello,
                                  I want to try your solution below (in placing the source code) but you don't explain where exactly I have to place this source code ! I think that I have to place the script section inside the "Default.aspx" file, but where do I need to intriduce this (I'm working on a WAF project) :

                                  [ASPx]
                                  <dx:ASPxDocumentViewer ID="ASPxDocumentViewer1" runat="server" Height="763px" ReportTypeName="XtraReport1"> <ClientSideEvents Init="init" /> </dx:ASPxDocumentViewer>
                                • Yaroslav (DevExpress Support) 09.27.2019

                                  Hi Anthony,
                                  Try placing the "script" block above the viewer declaration. Let us know if it works.

                                • Anthony Taieb 09.27.2019

                                  I don’t understand what you mean, give me more details please. For remind i’m working on a XAF project. I have only one file in ASP it’s default.aspx file. The other files are in C#.

                                  s‍o where do I need to place those 2 blocks of source code (the script block and the call function block)

                                  t‍hanks

                                • Yaroslav (DevExpress Support) 09.27.2019

                                  >>For remind i’m working on a XAF project.
                                  Thank you for the clarification. In this case, I suggest that you follow the steps outlined in this help topic: XAF | How to: Access the ASPxDocumentViewer and ASPxWebDocumentViewer Controls.

                                • Anthony Taieb 09.27.2019

                                  Ok it's working ! Thank you !

                                • jdubeau 10.03.2019

                                  Hi Yaroslav,

                                  I have the same problem in chrome with Web Forms.

                                  assembly="DevExpress.XtraReports.v14.2.Web, Version=14.2.13.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a"/>

                                  The funny thing is, it works fine in FireFox.
                                  You are recommending an upgrade to 19.1.7 or use init(s)

                                  Thank you,
                                  Joe

                                • Elliot (DevExpress Support) 10.04.2019

                                  Hello Joe,

                                  Could you please clarify if this problem is resolved?

                                  Thanks,
                                  Elliot

                                2 Solutions

                                Creation Date Importance Sort by

                                Fixed:

                                Show all comments
                                • Alexandre G 09.13.2019

                                  Hi,

                                  Missclicked the hotfix, we already tried Yaroslav’s solution and it worked. I do not need the hotfix.

                                  Thank you.

                                • Elliot (DevExpress Support) 09.13.2019

                                  Hello Alexandre,

                                  Thank you for your clarification. I believe that the hotfix for this issue will be useful to other customer.

                                  Thanks,
                                  Elliot

                                • SAMALOGI 09.16.2019

                                  Hello, I have the same error described in ticket, but with the v16.2.4 and Chrome Update 77.0.3865.75
                                  What solutions do we have for this version? 

                                • Elliot (DevExpress Support) 09.16.2019

                                  Hello,

                                  If updating the ASPxDocumentViewer control is not an option for you, please consider the workaround provided by Yaroslav in this ticket.

                                  Thanks,
                                  Elliot

                                • MarcR 10.03.2019

                                  Hi,
                                  We installed the hotfix 18.2.11 but when we click the printbutton, it throws an Error in Chrome: Cannot read property 'contentType' of null
                                  The error occurs on: if(f.contentDocument.contentType !== "text/html")
                                  We use the DocumentViewer Extension

                                  Screenshot is attached
                                  is there any solution?

                                • Andrey (DevExpress Support) 10.03.2019

                                  Hello,

                                  I've created a separate ticket on your behalf (T820506: A java script error when printing a report from the ASPxDocumentViewer control in Chrome v77). It has been placed in our processing queue and will be answered shortly.

                                • Artem B. 10.07.2019

                                  Hi, Can you create a fix for 19.1.5 version (We need a fix for production server without going to 19.1.6 version) ? 

                                • Yaroslav (DevExpress Support) 10.07.2019

                                  @Artem
                                  Here, at DevExpress, we follow the continuous integration model. A new build gets released and its version number is incremented. A hotfix is just an intermediate build that we provide for those who don't like waiting for the next official release that will incorporate all necessary changes (that would be version 19.1.7). The current hotfix version is 19.1.6.19280. This is the version you need to update. If you can't update, consider using the workaround provided below.

                                To whom it may concern:
                                If you're still an old version of our components (any version up to v15.1) and updating is not possible/desired, consider using the following workaround:
                                ASP.NET WebForms

                                [ASPx]
                                <dx:ASPxDocumentViewer ID="ASPxDocumentViewer1" runat="server" Height="763px" ReportTypeName="XtraReport1"> <ClientSideEvents Init="init" /> </dx:ASPxDocumentViewer>

                                ASP.NET MVC

                                @model XtraReport
                                
                                    @Html.DevExpress().DocumentViewer(settings => {
                                    settings.Name = "documentViewer";
                                    settings.Report = Model;
                                    settings.CallbackRouteValues = new { Controller = "Home", Action = "DocumentViewerPartial" };
                                    settings.ExportRouteValues = new { Controller = "Home", Action = "DocumentViewerExport" };
                                    settings.ClientSideEvents.Init = "init";
                                }).GetHtml()

                                where the Init function is declared as follows:

                                [ASPx]
                                <script type="text/javascript"> function init(s) { var createFrameElement = s.viewer.printHelper.createFrameElement; s.viewer.printHelper.createFrameElement = function (name) { var frameElement = createFrameElement.call(this, name); if(ASPx.Browser.Chrome) { frameElement.addEventListener("load", function (e) { if (frameElement.contentDocument && frameElement.contentDocument.contentType !== "text/html") frameElement.contentWindow.print(); }); } return frameElement; } } </script>

                                If you're using the old ReportViewer (with our without ReportToolbar), change the handler as follows:

                                [ASPx]
                                <dx:ReportViewer ID="RepViewer" runat="server" PageByPage="True"> <ClientSideEvents PageLoad="init"/> </dx:ReportViewer> <script type="text/javascript"> function init(s) { var isChrome = /Chrome/.test(navigator.userAgent) && /Google Inc/.test(navigator.vendor); var createFrameElement = s.printHelper.createFrameElement; s.printHelper.createFrameElement = function (name) { var frameElement = createFrameElement.call(this, name); if(isChrome) { frameElement.addEventListener("load", function (e) { if (frameElement.contentDocument.contentType !== "text/html") frameElement.contentWindow.print(); }); } return frameElement; } } </script>

                                Please try it out and let us know your results.

                                Show all comments
                                • bahar 09.12.2019

                                  I've tried,  successful,

                                  Thank you..

                                • Yong Xiang Tay 09.16.2019

                                  Hi,

                                  We are using version 14.1.6.0 and due to some reason we can't update the version. I tried the workaround but failed.

                                  My .aspx:
                                  <dxxr:ReportViewer ID="ReportViewer1" runat="server" CssFilePath="~/App_Themes/RedWine/{0}/styles.css"
                                                                  CssPostfix="RedWine" SpriteCssFilePath="~/App_Themes/RedWine/{0}/sprite.css"
                                                                  LoadingPanelText="">
                                                                 <ClientSideEvents PageLoad="init" />

                                                                  <LoadingPanelImage Url="~/App_Themes/RedWine/Web/Loading.gif">
                                                                  </LoadingPanelImage>
                                                                  <LoadingPanelStyle ForeColor="#303030">
                                                                  </LoadingPanelStyle>
                                                              </dxxr:ReportViewer>

                                  Javascript Error:

                                   Uncaught TypeError: Cannot read property 'printHelper' of undefined

                                  Please help!

                                • Yong Xiang Tay 09.16.2019

                                  I think i have fixed it by making some changes to the init function:

                                  function init(s) {
                                              var isChrome = /Chrome/.test(navigator.userAgent) && /Google Inc/.test(navigator.vendor);
                                              var createFrameElement = s.printHelper.createFrameElement;

                                              s.printHelper.createFrameElement = function (name) {
                                                  var frameElement = createFrameElement.call(this, name);
                                                  if(isChrome) {
                                                      frameElement.addEventListener("load", function (e) {
                                                          if (frameElement.contentDocument.contentType !== "text/html")
                                                              frameElement.contentWindow.print();
                                                      });
                                                  }
                                                  return frameElement;
                                              }
                                          }

                                  thks anyway.

                                • Elliot (DevExpress Support) 09.16.2019

                                  Hello Yong,
                                   
                                  Thank you providing a workaround for the 14.1 version. I believe it can be useful for other customers.
                                   
                                  Thanks,
                                  Elliot

                                • Sedat Öztürk 09.16.2019

                                  Hello,

                                  I am using DevExpress Version 17.1.6.0. Currently, the ASPxDocumentViewer print feature does not work with the Firefox 69.0 update. Could you help?

                                • Elliot (DevExpress Support) 09.16.2019

                                  Hello,

                                  I've created a separate ticket on your behalf (T815156: The ASPxDocumentViewer print feature does not work with the Firefox 69.0). It has been placed in our processing queue and will be answered shortly.

                                • Selim Kandilli 09.16.2019

                                  Hi,
                                  We use dx:ReportViewer and dx:ReportToolbar.
                                  Our devexpress version is 16.1.5
                                  Unable to change to AspxDocumentViewer.
                                  How can activate the print button.
                                  Thanks a lot

                                • Elliot (DevExpress Support) 09.17.2019

                                  Hello Selim,

                                  Please consider the workaround provided by Yong Xiang Tay in this ticket to avoid this issue.

                                  Thanks,
                                  Elliot

                                • Mark Hopper 09.17.2019

                                  As stated on the blog post in regards to this issue, this also appears to affect ASPxWebDocumentViewer. Attempting to print from the preview screen of the ASPxWebDocumentViewer, results in no print job being generated, or it being rejected.

                                  I've been testing this on 18.2.9.

                                • Dmitry Tok (DevExpress Support) 09.17.2019

                                  Thank you for mentioning this issue in this thread, Mark.

                                  We'll research it in the context of the Web Document Viewer - Print Report button does not work after Google Chrome Update 76.0.3809.132 thread.

                                • Customer77262 09.17.2019

                                  Do you know when the hot fix will be ready?

                                • Elliot (DevExpress Support) 09.17.2019

                                  Hello,

                                  We have already published the hotfixes for this issue so that you can install the required hotfix and check whether the issue is solved.

                                  Thanks,
                                  Elliot

                                • Rudolf Vanek 09.18.2019

                                  Would there be a hotfix for 17.2 or 17.1?

                                • Elliot (DevExpress Support) 09.19.2019

                                  Hello Rudolf,

                                  17.1 and 17.2 are outdated builds, so we do not provide hotfixes for them. If the upgrade of your application to a new version of our controls is not an option for you, use the workaround provided by Yaroslav to avoid this issue.

                                  Thanks,
                                  Elliot

                                • Nikos Argiropoulos 09.23.2019

                                  I have the same problem in version 19.1.6 and it seems that above links to 19.1.7 are broken, where can I find it?

                                • Nikos Argiropoulos 09.23.2019

                                  Please ignore my previous comment-question, after refreshing the page I managed to download the patch of 19.1.6 that solved the problem, however  warning message "Resource interpreted as Document but transferred with MIME type application/pdf" still shows. 

                                • Elliot (DevExpress Support) 09.23.2019

                                  Hello Nikos,

                                  Would you please prepare a screencast that illustrates how to replicate this issue? For example, use the Jing or ShareX tools for this purpose.

                                  Thanks,
                                  Elliot

                                • Jan Slavsky 09.24.2019

                                  Maybe better version with check for null

                                  [JavaScript]
                                  function init(s) { var createFrameElement = s.viewer.printHelper.createFrameElement; s.viewer.printHelper.createFrameElement = function (name) { var frameElement = createFrameElement.call(this, name); if(ASPx.Browser.Chrome) { frameElement.addEventListener("load", function (e) { if (frameElement.contentDocument && frameElement.contentDocument.contentType !== "text/html") frameElement.contentWindow.print(); }); } return frameElement; } }
                                • Jan Slavsky 09.24.2019

                                  There is an error in console that frameElement.contentDocument is null

                                • Elliot (DevExpress Support) 09.25.2019

                                  Hello Jan,

                                  Thank you for your clarification. I have corrected Yaroslav's answer in this ticket.

                                  Thanks,
                                  Elliot

                                • Jan Slavsky 09.25.2019

                                  Maybe important is also include this fix also to hotfix release.

                                • Chandana Pushpa Kumara 09.25.2019

                                  Hi all

                                  error in console that "Uncaught TypeError: Cannot read property 'printHelper' of undefined" please refer the attachement

                                  I am using 14.2.4 version and can not be upgrade

                                   

                                • Elliot (DevExpress Support) 09.26.2019

                                  Hello Chandana,

                                  I've created a separate ticket on your behalf (T818267: Print Report button does not work after Google Chrome Update). It has been placed in our processing queue and will be answered shortly.

                                • Elliot (DevExpress Support) 09.26.2019

                                  Hello Jan,

                                  Note that we do not provide hotfixes for outdated (old) builds. If the upgrade of your application to a new version of our controls is not an option for you, consider using the workaround provided in this ticket.

                                  Thanks,
                                  Elliot

                                • Duc VNYI 09.26.2019

                                  I am having the same issue with DevExpress 13.1.14

                                • Yaroslav (DevExpress Support) 09.26.2019

                                  Hi Duc,
                                  Did you have a chance to try the above workaround? Does it work for you?

                                • Stuart A Lowe 09.26.2019

                                  HI

                                  I did try it and it takes a while before the Print Dialog Screen appears – as if you selected CTRL – P in chrome.
                                  So the workaround works – now I have to add this to about 20+ forms for each Report View control…

                                  Kind regards

                                  Stuart Lowe

                                • IntelliTrack 09.26.2019

                                  Is it possible to have a hotfix for this available for DevExpress 18.1.3?

                                  Using the 18.1.13 hotfix would require us to upgrade our version of DevExpress that we use, which we are not prepared to do at this time.

                                • Ronald Mejia 09.26.2019

                                  Is it possible to get a hotfix for this issue on DevExpress 17.2.4?

                                • Yaroslav (DevExpress Support) 09.26.2019

                                  Hi,
                                  As you probably know, here at DevExpress, we follow the continuous integration model. The version you mentioned (v17.2.4) is very old and its life cycle has already ended. Unfortunately, we won't be able to prepare a hotfix for this version.
                                  If you're unable to update, consider using the workaround I provided above.

                                  Regards,
                                  Yaroslav

                                • Ronald Mejia 09.26.2019

                                  Thank you Yaroslav,
                                  I am now updating the project from 17.2.4 to 19.1.6. (i could not find 19.1.7)
                                  Does the hotfix work on 19.1.6 as well as 19.1.7?
                                  Ron

                                • Yaroslav (DevExpress Support) 09.26.2019

                                  When the ticket's status is "Fixed", this means that the corresponding issue has been fixed, and the fix will be included in the next public release. Version 19.1.7 is not yet here. At the same time, version 19.1.6 was released prior to this inquiry report and therefore it does not contain the required code changes. If you do not want to wait for the next build release (v19.1.7), you are welcome to try a hotfix (an intermediate build) immediately. The current hotfix version is 19.1.6.19269.

                                  Regards,
                                  Yaroslav

                                • Janaka Neranjan 10.01.2019

                                  Hi Yaroslav,

                                  This solution I applied to  Version  14.2, but it did not work.Please let me how I solve this on version 14.2.

                                • Julie Schwalm 10.01.2019

                                  You provided Javascript above for the old ReportViewer control:

                                  "If you're using the old ReportViewer (with our without ReportToolbar), change the handler as follows:"

                                  However, I couldn't find a ClientSide Init event for this control, or for the toolbar. Is there a way to handle this issue for the ReportViewer control?

                                  Thanks!

                                • Yaroslav (DevExpress Support) 10.01.2019

                                  @Janaka,
                                  I see you've already created a separate ticket regarding this matter: Web report toolbar print buttons do not work in Google Chrome.
                                  Let's continue our discussion there.

                                  @Julie,
                                  Use the client-side "PageLoad" event instead. I've updated my answer to avoid any ambiguity.

                                • Pedro Martinez 2 10.09.2019

                                  I had the same problem this week, thanks to all this comments i have solved, applying the Yaroslav's suggestion https://docs.devexpress.com/eXpressAppFramework/113612/task-based-help/reporting/how-to-access-the-document-viewer-and-web-document-viewer-controls, I used the HTML5 at ReportsAspNetModuleV2.ReportViewerType property, The same problem occurs if i ran the application in Microsoft Edge and FireFox, all of them where solved. I still using 16.2.6 version.

                                  Thanks

                                  Regards.

                                • Yaroslav (DevExpress Support) 10.09.2019

                                  You're very welcome, Pedro! I'm happy to hear that my solution worked out for you.
                                  Should there be further questions, feel free to contact us at any time.

                                  Regards,
                                  Yaroslav

                                • Pedro Martinez 2 10.10.2019

                                  Hi Yaroslav.

                                  I realize today that i have a couple of apps which continue using the old report module (No, the ReportModuleV2), so, is there any solution for it?.

                                  Any suggestion?

                                  Regards.

                                • Yaroslav (DevExpress Support) 10.11.2019

                                  Pedro,
                                  If you have to stick with the old ReportViewer / DocumentViewer component, use the code approach I provided above. It can be implemented both in a regular ASP.NET application or in a XAF application. The only difference here is that in XAF the viewer is created for you, so you have to use a XAF-specific API to register your custom client-side event hander, exactly as my colleague explained in the ASPxDocumentViewer ver. 16.2.4 - Print Report button not working after Google Chrome Update 77.0.3865.75 thread. If there are any issues with this approach, please post a reply in that thread and elaborate on what you've tried and what issue you encountered (whether it's a compilation error, a runtime error, etc).

                                  Regards,
                                  Yaroslav

                                • Customer77262 10.15.2019

                                  Hello I've update my devexpress components to the 18.2.11 version that apparently solves the print problem for Google Chrome browser but when I've tried to use the reporter it throws me an error Cannot read property 'contentType' of null can anyone help me solve this problem? 

                                • Yaroslav (DevExpress Support) 10.15.2019

                                  Hi,
                                  The same runtime error has been already reported here: A java script error when printing a report from the ASPxDocumentViewer control in Chrome v77. Unfortunately, our attempts to reproduce the same issue using v18.1.11 were unsuccessful. If you have a demo project that we can test on our side, or if you aware of any steps that one should follow to reproduce the issue, please let us know in the comments section of the A java script error when printing a report from the ASPxDocumentViewer control in Chrome v77 thread.

                                  Regards,
                                  Yaroslav

                                • Liow Yeow Chong 10.17.2019

                                  Hi,
                                  I am using 14.2.6.
                                  The workaround is not working for me. I had ASPxDateEdit component on the report aspx to allow user to define the period. The calendar will not appear when I click on ASPxDateEdit after Iadded the javascript.
                                  Pls take note that I have the  ASPxDocumentViewer  in  a UserControl file (.ascx)
                                  Please advice.
                                  Thank you.

                                • Yaroslav (DevExpress Support) 10.17.2019

                                  Hi Liow,
                                  It's highly unlikely that the issue your face has anything do with ASPxDateEdit. Rather, it's a script error that prevents the editor's correct execution. You should be able to see this error while running your project and opening the developer tools of your browser, the "Console" tab (F12).
                                  There are two major reasons why the code you have put into your UserControl does not work:

                                  1. The "Init" handler must be defined before the viewer and not after.
                                  2. There is no "ASPx.Browser.Chrome" constant in the version you're using: you have to use a regular expression instead (see the alternative solution posted above).

                                  For your reference, I've attached the sample project that target v14.2. Please check it and confirm that it works for you.

                                  Regards,
                                  Yaroslav