locked
Error 0x8007007A occurring on app-v clients only RRS feed

  • Question

  • Hi all,

    We have a .NET client application that incorporates the Crystal Reports Viewer, version 2013.

     

    When we deploy to a Windows client or server (Windows7, 8, 10) everything works fine. We can view CR reports without problems

     

    We have two customers that use App-V to deploy the application. One of them encounters this problem:

     

    As soon as we try to open a report, the application runs into this error:

    "The data area passed to a system call is too small"

     


    Any suggestions on where to look for a solution? We don't have App-V expertise ourselves.

    Her's part of the stacktrace:

    System.Runtime.InteropServices.COMException (0x8007007A): Retrieving the COM class factory for component with CLSID {F734A321-8381-4FFD-A614-139E8906DC83} failed due to the following error: 8007007a Het gegevensgebied dat aan een systeemaanroep is doorgegeven, is te klein. (Exception from HRESULT: 0x8007007A).
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.CreateRptDoc()
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper..ctor()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Initialize()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor()
       at CrystalDecisions.ReportSource.NonHTTPCachedReportSource.GetReport(RequestContext context, Boolean bAddToCacheWhenCreated)
       at CrystalDecisions.ReportSource.LocalReportSourceBase.GetAvailableExportFormats(ExportRequestContext reqContext)
       at CrystalDecisions.Windows.Forms.ViewerDocument.GetAvailableExportFormats()
       at CrystalDecisions.Windows.Forms.PageView.CreateReportDocument(String rptURI)
       at CrystalDecisions.Windows.Forms.PageView.CreateNewReportDocument(String pageName)
       at CrystalDecisions.Windows.Forms.CrystalReportViewer.CreateReportSource(Object reportSource)
       at CrystalDecisions.Windows.Forms.CrystalReportViewer.set_ReportSource(Object value)
       at INFOplan.CrystalRapportViewerForm.InitReport()
       at INFOplan.CrystalRapportViewerForm.Form1_Load(Object sender, EventArgs e)
       at System.Windows.Forms.Form.OnLoad(EventArgs e)
     



    1*! Galletto

    Wednesday, March 2, 2016 1:10 PM

All replies

  • Is the .NET Application delivered via App-V or the Crystal Runtime, or both? Was the Crystal Reports Viewer installed during Sequencing?

    Simon Dettling | msitproblog.com | @SimonDettling

    Wednesday, March 2, 2016 1:32 PM
    Moderator
  • The Crystal Reports Viewer is part of the application. The Visual Studio project references it. The setup installs the Crystal Reports viewer on the client, which is then made into an app-v.

    Does that answer what you were asking?

    Best regards,

    Will de Haan


    1*! Galletto

    Wednesday, March 2, 2016 1:39 PM
  • What version of App-V are you using? Have you tried using Procmon to trace the issue?

    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Wednesday, March 2, 2016 2:00 PM
  • There is an issue with the path length's Crystal Reports uses that cause some type of failure inside an AppV bubble.  The fix is to shorten the paths.

    Here are the steps I documented to fix this:

    http://trentent.blogspot.ca/2015/06/crystalreports-13-and-appv-5-have-issues_26.html

    I got a different error message then what you are reporting but the cause/fix maybe the same still.


    • Edited by TrententMVP Wednesday, March 2, 2016 5:01 PM
    Wednesday, March 2, 2016 5:01 PM
  • Make the PVAD of the application the location where the Crystal Reports viewer is installed.
    Friday, March 4, 2016 6:30 PM
    Moderator