I have several reports which have been integrated into a dashboard web app. On several of the reports we use the "Widgets Pro" angular gauge component. This renders and displays fine with visualize.js. The user would like to be able to export some of these as PDF documents. It renders fine if I export to PDF from within TIBCO jasper studio, but when I deploy it jaspersoft-pro and attempt to export it as a PDF or a DOCX file from the server the component does not render and the error message "[Fusion Component Not Supported]" is left in its place.
I'm not really sure where to start with this. I assume some components or libraries need to be added to our server.
A couple other details to mention: The workstation on which I develop is Windows. The server is Linux based. We are running TIBCO jasperserver 7.5.0
Well the local crew ended up figuring this out.
Turns out that PhantomJS needed to be updated and configured on the jaspersoft-pro server, to 2.1.1 in our case.
More specific steps:
Download PhantomJS 2.1.1 from official website and extract to an appropriate spot on your system (like /usr/local/phantomjs).
Edit $CATALINA_BASE/webapps/jasperserver-pro/WEB-INF/js.config.properties and set "phantomjs.binary=/usr/local/phantomjs/bin/phantomjs"
Edit $CATALINA_BASE/webapps/jasperserver-pro/WEB-INF/classes/jasperreports.properties and set "net.sf.jasperreports.phantomjs.executable.path=/usr/local/phantomjs/bin/phantomjs"
Related
I'm using LeadTools v20 HTML5 Document Viewer with Asp.Net Core backed Document Service Library which was available in their examples project in the installation directory. This works fine with PDF files or other file formats mentioned in their site. But I'm getting LeadTools.RasterException error with a message as invalid file format for .docx,.xlsx,.pptx but opens .doc,.xls,.ppt
Files having extension ending with x(mostly Microsoft office documents) are not getting loaded in development mode. But all these works when the application is published. Any suggestions on where I'm going wrong?
Here is the screen print of the exception and error.
Please assist me if I'm wrong
Can you check the dependencies on both machines and compare the differences? If you're testing this on Windows, one way to do that is to use Process Explorer to see what DLLs are being loaded. You can download it here:
https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
To see the DLLs being loaded go to View > Show Lower Pane, then View > Lower Pane View > DLLs:
Select the ASP.NET Core Document Service while it's running and then attempt to load the document on the working machine and see what DLLs get loaded, then do the same on the non-working machine and see which DLLs are loaded. You should see a DLL missing.
My guess is that you are missing the DocumentFormat.OpenXml(v2.0) since that is required for all of the x microsoft formats (docx, xlsx, pptx). You can see which DLLs are required for which formats by the SDK at this link:
https://www.leadtools.com/help/sdk/v20/dh/to/file-format-support.html
If you are still having issues after trying the above, they offer free technical support via email (anytime) and live chat (M-F business hours):
https://www.leadtools.com/support/supportoptions?linkloc=navbar
We used Apache tomcat 8.5.27 and deployed Jasper reports server 7.1. The deployment was successful with no issues and when we access the homepage, it displays the garbled home page and does not load. However, on deploying jasper reports server 6.2 login page works fine and loads all images etc in perfect manner. Please advice of there is anything to be done.
The jasper reports 7.1 is a WAR file. Garbled login page
When we upgade from 6.x version to 7 version, There is a file in WEB-INF/application-context.themes.xml. This will have two options to load Themes from file or DB.
7.1 was using loading from DB and faiing.
we reconfigured the application-context-themes.xml and that fixed the problem.
I just started to get my head around AEM 6.0 . Installed an app with 'mvn clean install -Pauto-dev-deploy'. I can see the app in CRXDE and the packages are visible in the packagemanager. It does not however show up in the touchUI. Is it possible to run a preview of this site and how to do it?
In Adobe Experience Manager your application (app) and your content are to different things. Your application contains templates and components with which you build your content.
Deploying your app therefore means that you don't necessarily will have content. Without having a look at your source it is hard to see how and where you can create content. Usually your apps templates and components only work in certain content paths. This is usually defined in /etc/designs/<your-project-name>
If you are running AEM 6.2 I suggest that you have a look at the new We Retail demo application and demo content. The source of which can be found on Github: https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail
I created a VS 2008 C# MVC application which uses CrystalReportViewer to display a report. All the .dll files I used are either version 12.0.2000 or 12.0.1100.
The application works well on my localhost and the dev environment.
When I deployed it (on a vista virtual machine with IIS 7.0) I ran two files :
1) CRRuntime_12_2_mlb.msi
2) CRRedist2008_x86.msi
Still when I open the viewer to view a report all I see is an empty view( the view only contains the CrystalReportViewer so obviously something is not working with the viewer on the deployment machine)
Can anyone give me clear steps on how to deploy a web app with CrystalReportViewer???
I looked around and could not find a clear instruictions.....just seems that everyone tries stuff until it works.
Thanks very much in advance
Susan
I have got the same problem like above. Does somebody have a solution?
The web project using the following controls:
CrystalReportSource (Version 12.0.2000.0)
CrystalReportViewer (Version 12.0.2000.0)
On the server I have only installed CRRuntime_12_2_mlb.msi.
Best regards,
Daniel
I created a ASP.NET3.5 website having a crystalreportviewer in it, it works fine if I run through visual studio 2008 or on my own machine. But when i deployed project on web server, it started giving me error.
Firstly it was giving error on first page that CrystalDecision.web assembly can't be found, then I installed Crytal Runtime 2008 on my web server. After installation application seems like ok, but when I opened page with CrystalReportViewer it gave me different error, as following:
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Any idea about it??
You probably have slightly different versions of the crystal assemblies on the server and your development machine. Compare the version numbers in c:\windows\assembly on both and see if there is a difference. If there is, either update the server or change the version numbers for the assemblies in web.config.
Also, The located assembly's manifest definition does not match the assembly reference
After spending almost 2hrs I finally found the fix.
Uninstall the Crystal Reports run time from web server.
Check if web server still have \program files\Business object folder, if still exist then delete it. Ensure other applications are not dependent on it.
Give Read and Write access permissions to ASPNET user on \windows\Temp folder
Install Crystal Report run time now.
Restart IIS
Following these steps should fix the crystal report viewer problem.
But then one more problem arises, crystal report viewer doesnt show the icons, the reason is crystal report viewer looks for aspnet_client\system_web\2_0_50727 folder in root folder of the website. In my case I have multiple websites on my server including .NET 1.1, 2.0 and ASP, so I have wwwrootASP2.0 folder for this website. But by default web server created aspnet_client\system_web\2_0_50727 folder under default website (wwwroot). So, the fix is, just copy that aspnet_client\system_web\2_0_50727 folder into your website's root directory. Bingo !!!!!! It works fine now.
I hope it will help,
Cheers.
I just wanted to add that an easier way seems to be creating a virtual directory under you web application called aspnet_client that points to C:\Inetpub\wwwroot\aspnet_client.
This also makes the images on the crystal report viewer show up. It was tested with visual studio 2008 crystal basic on IIS running on server 2003.
I figured this out after reading http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/e2dc93b3-e594-4ae6-ba92-9440ccc7f6be.