SSRS 2017 Errors on exporting to Excel or Word .xlsx, .docx RRS feed

  • Question

  • I cannot export in SSRS 2017 to EXCEL or WORD 2013 versions, EXCELOPENXML or WORDOPENXML.  2003 versions work fine in the environment when turned on.  This also happens in SSRS Report Builder.  There is something fundamentally wrong in the rendering.  The following are the types of errors I am seeing:

    An Error occurred during rendering of the report.  (rrRenderingErrorr). In report builder

    In SSRS:

    library!ReportServer_0-2!1a5c!07/24/2019-14:50:26:: e ERROR: Report server dump occured. Exception: Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.TypeInitializationException: The type initializer for 'MS.Utility.EventTrace' threw an exception. ---> System.Security.SecurityException: Requested registry access is not allowed.
       at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource)
       at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
       at Microsoft.Win32.Registry.GetValue(String keyName, String valueName, Object defaultValue)
       at MS.Utility.EventTrace.IsClassicETWRegistryEnabled()
       at MS.Utility.EventTrace..cctor()
       --- End of inner exception stack trace ---
       at MS.Utility.EventTrace.EasyTraceEvent(Keyword keywords, Event eventID)
       at System.IO.Packaging.Package.Open(Stream stream, FileMode packageMode, FileAccess packageAccess, Boolean streaming)
       at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.XMLModel.XMLStreambookModel.get_ZipPackage()
       at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.XMLModel.PartManager..ctor(XMLWorkbookModel workbookModel)
       at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.XMLModel.XMLStreambookModel..ctor(Stream outputStream)
       at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.ExcelApplication.CreateStreaming(Stream outputStream)
       at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.OpenXmlGenerator..ctor(CreateTempStream createTempStream)
       at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.ExcelOpenXmlRenderer.CreateExcelGenerator(CreateTempStream createTempStream)
       at Microsoft.ReportingServices.Rendering.ExcelRenderer.MainEngine..ctor(CreateAndRegisterStream createStream, ExcelRenderer excelRenderer)
       at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
       --- End of inner exception stack trace ---

    Monday, July 29, 2019 5:11 PM

All replies

  • Hi Todd,

    From you post:

    1. Do you have in your environment also SSDT installed?  If so could try export into those format using SSDT?

    2. Are you using Sharepoit integrated mode of SSRS, If so please try following two links see if they help.

    Requested Registry Access Is Not Allowed

    Quick Solution 5 : Requested registry access is not allowed

    3. Try open the rsreportserver.config in RS root folder. Find render session and check if those format docx and xlsx are listed in it.

    Could you give more back ground like how this error happened?



    MSDN Community Support Please remember to click Mark as Answer; the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, July 30, 2019 6:01 AM
  • Answers to questions:

    1) No

    2) native mode

    3) here is what is listed there: 

                           <Extension Name="WORDOPENXML" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordOpenXmlRenderer.WordOpenXmlDocumentRenderer,Microsoft.ReportingServices.WordRendering"/>
    <Extension Name="WORD" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordDocumentRenderer,Microsoft.ReportingServices.WordRendering" Visible="false"/>
    <Extension Name="EXCELOPENXML" Type="Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.ExcelOpenXmlRenderer,Microsoft.ReportingServices.ExcelRendering"/>
    <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="false"/>
    <Extension Name="PPTX" Type="Microsoft.ReportingServices.Rendering.PowerPointRendering.PptxRenderingExtension,Microsoft.ReportingServices.PowerPointRendering"/>
    <Extension Name="PDF" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer,Microsoft.ReportingServices.ImageRendering"/>
    <Extension Name="IMAGE" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.ImageRenderer,Microsoft.ReportingServices.ImageRendering"/>
    <Extension Name="MHTML" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.MHtmlRenderingExtension,Microsoft.ReportingServices.HtmlRendering">

    The overall issue is if you schedule a report to render in excel or word it fails.  You get the above previous mentioned errors.  It also fails to export to those formats from the report builder or from the web interface as well. 

    Tuesday, July 30, 2019 5:12 PM
  • Hi Todd,

    Thanks for your reply.

    As I checked your list, seems your configuration file is OK. 
    From the error log and error info, it seems your SSRS registry had some issue within. You could open registry editor by runing regedit. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application this location to check if Report Server(SSRS) and Report Server Windows Service(SSRS) are listed in it.

    Since registry could be dangerous if it is modified not correctly, I highly recommend to run the SSRS2017 installer, and choose the repair function see if it works.

    Hope it helps.


    MSDN Community Support Please remember to click Mark as Answer; the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, July 31, 2019 7:09 AM
  • Those entries are present.  I performed repair, reboot.  Run any report and try to export to excel or word and get a Reporting Services Error of the same type posted above.  I can run the same report in SSRS 2016 without issue.  It is just this 2017 SSRS instance having problems.

    Wednesday, July 31, 2019 12:10 PM
  • So I found another forum that mentioned the Execution Account setting in SSRS configuration.  If I remove the account then everything works.  Of course that is not how things should be and wish to have it set.  It is set without problem in my 2016 versions.  So if the issue is the execution account what does that account need to have access to on the system for things to be copacetic.  I gave it the same SQL Security settings on Report Server DB and Temp DB as in my 2016 environment but, still getting error.  Does it need to have security permissions set on any specific windows or Sql folders?
    Wednesday, July 31, 2019 12:43 PM
  • Hi Todd, 

    Great is that at least we've found some clue for this. I tested a little bit by creating a brand new execution account in my test machine. The exportation is working. So could you also try make a new account to give a try?

    MSDN Community Support Please remember to click Mark as Answer; the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, August 1, 2019 7:21 AM
  • I replaced the Execution account with a different one, same issue.  Does the Execution Account in SSRS Configuration require to also be given security permissions elsewhere in the system or Sql Server, i.e. permissions to the ReportServer DBs.  If so, and they are not automatically configured where is a list of settings that I need to create?

    Friday, August 2, 2019 12:41 PM
  • Have you found a resolution to this? I'm having the same issue but with SSRS 2016 SP2 CU8. 

    Friday, August 23, 2019 6:20 PM
  • No, the work around offered is remove the execution account from the global ssrs report configuration.  In doing so you will be required to provide an execution account for each ssrs report data set during creation.  Not the work around I would want to use.  Can someone who understands the issue presented please provide a real permanent fix and not a work around.
    Monday, August 26, 2019 5:02 PM
  • IMHO the info in the link below is 100% applicable. 


    "fundamentally broken" = Regression. Most SQL 2016 builds were OK - maybe because they used something other than System.IO.Package for ZIP file handling - but SP2CU8 is not. I'm >50% sure SP2CU6 was OK, and all SP1 builds I worked with were OK... Please if someone has the resources - test and pinpoint the exact CU that broke this.

    Wednesday, December 4, 2019 4:14 PM
  • I was able to reproduce this with SSRS 2016 and the most bleeding-edge version of PBIRS. Things I noticed as well as the solution follow.

    Event viewer shows successful impersonated logons in which the SSRS service account impersonates the execution account when logging on. These are successful.

    Running a ProcMon during the issue will show ReportingServicesService.exe getting an ACCESS DENIED error for the following key. This key is only accessible while SSRS is running and disappears when it is not. Changes made to its permissions are retained.


    Giving the execution account read access to this registry path resolves the problem. Your path will be slightly different since we're not using the same user accounts presumably.

    Friday, July 10, 2020 10:13 PM