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.
Related
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"
I have a web-application running on WildFly 8.2.
The application has a view, with links to txt-files.
I have the application running on a local WildFly and on a remote "test" server. Both environments have exactly the same version of the application and same version of WildFly. I also try them with the same web browser (Internet Explorer) on different tabs.
When I click one of those links, using the same web browser, in the application that runs on my local wildfly, it shows the umlaut (äöå) perfectly. In the test environment it doesn't. It shows just empty white boxes.
Now, when I right-click on the page on internet explorer. I can see that in the correctly working version the encoding shows "Western European (Windows)" and in the NOT working, test environment, the encoding shows "Unicode (UTF-8)" being used on the site.
Is there a configuration in WildFly that determines this? Because I'm running the same version of the program in the same branch in both instances so the problem shouldn't be programmatical.
I have taken up a project to integrate JasperReports Server with an existing web application. I am using the community edition 4.5 of JRS. I was able to succesfully download and point it to my tomcat server and mysql databases. My question is: I want to re direct users from my web app to the JasperReports Server webapp and bypass the login screen of JasperReports Server. My web app uses LDAP validation. Is there a way to do this?
You can find the answer on this website http://ebookbrowse.com/jw11-jrsintegration-lukeshannon-pdf-d67595249. There is pdf file "Integrating and Deploying JasperReportsServer with Java Applications".
I successfully embedded JasperReports Server with HTTP from my Java web application using JSP.
Regards
Sorry there is no way to do that .
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.
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.