Forum Discussion

Monte's avatar
Monte
New Contributor
2 years ago

TestComplete WebBrowser/MS ReportViewer compatibility

We have recently incorporated a 3rd party webbrowser component into one of our legacy applications.

Our application also uses the Microsoft ReportViewer 8.0 for rendering local *.rdl files.

Normal usage of the application works fine; however, execution of automated testing using TestComplete V.15.40.421.7 results in an error related to Microsoft ReportViewer compatibility.

Removing the web browser dlls from the application folder bypasses the report error; however, it disrupts the usage of the web browser components.

Can you provide any insight on how to resolve the incompatibility within the TestComplete execution?


Thanks,
Monte

Copy of the Report Viewer error.
Microsoft.Reporting.WinForms.LocalProcessingException: An error occurred during local report processing. ---> Microsoft.Reporting.DefinitionInvalidException: The definition of the report 'Main Report' is invalid. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred while compiling expressions. Native compiler return value: ‘[BC2007] unrecognized option '-vegister-pepper-plugins="C:\Program Files (x86)\SmartBear\TestExecute 15\bin\Extensions\tcCrExtension\tcCEFHost.dll;application/x-testcomplete12-0-chrome-browser-agent"'; ignored’.
at Microsoft.ReportingServices.ReportProcessing.ReportCompileTime.ParseErrors(CompilerResults results, CodeClassList codeClassInstDecls)
at Microsoft.ReportingServices.ReportProcessing.ReportCompileTime.InternalCompile(Report report, AppDomain compilationTempAppDomain, Boolean refusePermissions)
at Microsoft.ReportingServices.ReportProcessing.ReportCompileTime.Compile(Report report, AppDomain compilationTempAppDomain, Boolean refusePermissions)
at Microsoft.ReportingServices.ReportProcessing.ReportPublishing.Phase3(ParameterInfoCollection& parameters, AppDomain compilationTempAppDomain, Boolean generateExpressionHostWithRefusedPermissions)
at Microsoft.ReportingServices.ReportProcessing.ReportPublishing.CreateIntermediateFormat(CatalogItemContext reportContext, Byte[] definition, CreateReportChunk createChunkCallback, CheckSharedDataSource checkDataSourceCallback, PublishingErrorContext errorContext, AppDomain compilationTempAppDomain, Boolean generateExpressionHostWithRefusedPermissions, String& description, String& language, ParameterInfoCollection& parameters, DataSourceInfoCollection& dataSources, UserLocationFlags& userReferenceLocation, ArrayList& dataSetsName, Boolean& hasExternalImages, Boolean& hasHyperlinks)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateIntermediateFormat(CatalogItemContext reportContext, Byte[] reportDefinition, CreateReportChunk createChunkCallback, CheckSharedDataSource checkDataSourceCallback, AppDomain compilationTempAppDomain, Boolean generateExpressionHostWithRefusedPermissions)
at Microsoft.Reporting.ReportCompiler.CompileReport(CatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ReportSnapshotBase& snapshot)
--- End of inner exception stack trace ---
at Microsoft.Reporting.ReportCompiler.CompileReport(CatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ReportSnapshotBase& snapshot)
at Microsoft.Reporting.StandalonePreviewStore.StoredReport.CompileReport()
at Microsoft.Reporting.StandalonePreviewStore.StoredReport.get_Snapshot()
at Microsoft.Reporting.StandalonePreviewStore.GetCompiledReport(CatalogItemContext context, Boolean rebuild, ReportSnapshotBase& snapshot)
at Microsoft.Reporting.LocalService.CompileReport(CatalogItemContext itemContext, Boolean rebuild)
at Microsoft.Reporting.WinForms.LocalReport.CompileReport()

Desktop Testing

4 Replies

Sort By
  • Marsha_R's avatar
    Marsha_R
    Champion Level 3
    2 years ago

    I did a search on the Microsoft error message 

    Microsoft.Reporting.DefinitionInvalidException: The definition of the report 'Main Report' is invalid.

     

    and there are many different issues that could cause this. I see path problems and report syntax problems among others. 

     

    I suggest checking this statement for syntax or other errors since it's the one that the error flagged

    -vegister-pepper-plugins="C:\Program Files (x86)\SmartBear\TestExecute 15\bin\Extensions\tcCrExtension\tcCEFHost.dll;application/x-testcomplete12-0-chrome-browser-agent

    • Monte's avatar
      Monte
      New Contributor
      2 years ago

      Thanks for the feedback Marsha.

       

      I'll have our QA team check on the plugin statement. I don't think that it is something we specifically implemented, but may be an option that we can disable.

       

       

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    2 years ago

    ...and I think the switch statement should be --register-pepper-plugins and not -vegister-pepper-plugins!

  • Monte's avatar
    Monte
    New Contributor
    2 years ago

    Thanks to everyone for the feedback.

     

    The test team disabled the browser plugin that was causing the conflict with a chrome-based browser component.