Rank: Newbie
Groups: Member
Joined: 2/14/2023
Posts: 4
|
We have recently incorporated the EO.WebBrowser components (v.22.1.13.0) 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 seems to work fine; however, execution of automated testing using SmartBear TestComplete V.15.40.421.7 results in an error related to Microsoft ReportViewer compatibility.
Removing the EO dlls from the application folder bypasses the report errors, but disrupts the usage of the web browser components.
Our legacy application is dependent on .NET Framework 2.0, so evaluating with newer versions of the EO objects has not been evaluated due to the incompatible framework changes.
Are there any known incompatibilities with this configuration?
Are there any options to assist in identifying and resolving the automation conflict?
Any other feedback or suggestions would be appreciated.
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()
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
We can't tell much just from this exception because this exception is from SmartBear. Exactly why the mere present of our DLLs trigger that error would be a question for them since we do not know how and based on what condition they would throw that exception.
Additional information that related to our product and you may find useful:
1. You CAN use the latest version on .NET Framework 2.0. We did brieft remove support for .NET Framework 2.0 but we have since added it back because we have received many complains from our users;
2. You CAN NOT use pepper plugin with EO.WebBrowser. This is because Chromium browser engine have removed pepper plugin support since last year. As such our latest version no longer support pepper plugin. So if your solution uses pepper plugin then it won't work. Note that this only means we can not use pepper plugin. Other components such as SmartBear may use an older version of Chromium browser engine that still supports pepper plugin;
Hope this helps.
Thanks!
|
Rank: Newbie
Groups: Member
Joined: 2/14/2023
Posts: 4
|
Thanks for the quick response, confirmation and additional information.
I agree that it does not make sense as to why the presence of the EO assemblies would have any impact on the processing of MS ReportViewer rdls when run via TestComplete.
We will continue the search for answers with Smartbear.
I will also update our notes regarding version compatibility. It is nice to know that we are no longer version locked.
Thanks!
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Great. Please feel free to let us know if you have any more questions.
|
Rank: Newbie
Groups: Member
Joined: 2/14/2023
Posts: 4
|
FYI - the testing team disabled the browser plugin that was causing the conflict from testcomplete.
Thanks for the assistance.
Monte
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Did that resolve the issue? And did you find out why the mere existence of our files would trigger the problem on their end?
|
Rank: Newbie
Groups: Member
Joined: 2/14/2023
Posts: 4
|
Removing the extension resolved the issue.
I'm not actively involved in the test efforts, but my understanding is that someone updated TestComplete and it added a step that attempted to hook in the browser extension which resulted in the failure.
Knowing how/why it chose to add the extension based on the inclusion of your assemblies is beyond my area of interest :)
|