I am using the CrystalReportViewer in a ASP.net application using VS 2010. The reports were built using CR version 2011.
When printing in firefox a bunch garbage is printed out.
The print works fine in IE and Chrome. Any idea how to make firefox print correctly?
I have the same problem and the only idea I can come up with thus far is to trap the printing on server-side, then use crystal reports object to do the printing. I know its a hack, but it seems to be the only way right now.
Related
I have a very pretty calendar report that I've created on one machine, that shows my company's daily revenue as a color coded block for every day for the past several years. After finally getting a color scheme down and pretty much finalizing it, I went to test it on another machine - and hit a rather large obstacle.
This is the report that I used as a template:
http://bl.ocks.org/mbostock/4063318
It's awesome. And, inside Internet Explorer 11, it looks fantastic. I never would have expected that copying the code and testing the report would produce a blank page, but there it is. On that page, the calendar report is visible. In IE 11. Copying the code to a new html file and opening it, shows nothing. In Firefox, however, everything is visible. as is.
Now, there's a part of that page that points to "//d3js.org/d3.v3.min.js"
And I figured out that in order to make that work in firefox I had to add the http: in front, so that's not my issue.
I'm literally sitting here at my desk staring at two browser windows open and pointing to the same html file. One contains my beautiful report, one is a completely blank page.
Some cursory google searches reveal that IE 8 or lower have issues with the svg. I can't seem to find any references on someone having a similar issue though. Their situation seems to be that with IE10, you need to specify the height and width, not just one or the other, to make sure everything scales properly.
If I could have my way, I'd just run Firefox on all of the machines that are going to run the report, even if it's just for that one thing! Alas, I am but a mere peasant coder and so I have to make it work. in the dreaded IE.
Are there any svg/html/d3.js coders out there that can tell me another way to spit out the data I'm using so that I can get what I'm looking for?
copying the code and testing the report would produce a blank page
Because you're outputting invalid HTML. There is no html or head element for starters.
Output your code in to a file like example.xhtml and open it in Firefox (specifically) as it's XML parser will very quickly tell you what line and column the first XML parser error is occurring on. You are rendering in standards mode instead of quirks though that does not imply your page meets standards.
var m=(document.compatMode == 'CSS1Compat') ? 'Standards' : 'Quirks'; window.alert(m+'-mode.');
I'm using Firefox developer edition, trying to debug a page (html+javascript) in a frame.
With Firefox 33, in the debugger section I can see the source code of the page inside the frame, activate breakpoints...
My problem with developer edition is that it doesn't show the html code of the page, although it is selected in the left side of the toolbar. It shows some html code, but it's not from the selected page. I can't locate where is it from.
Is there a way to have the same behaviour in debugger for firefox 33 and developer edition?
Thanks in advance, best regards
This is what GC does to you
Short answer, the HTML of the frame was being garbage collected away by the browser engine. This happens when the page/html has no script active on it which has still some work left to do.
This can be otherwise prevented by holding a strong reference to any object in the page and putting it somewhere where the browser thinks that its still being used.
For example,
window.foobar = some_object_from_the_page
will work.
Here is the root cause and a potential & partial fix is coming up in near future.
One of our client is trying to generate reports with lots of sub reports, its a single page report. If they generate it for 2-3 years it works for all browsers, but when they generate it for 5 years. Report works fine in chrome and firefox but IE will not be able to load reports and show IE window "Internet explorer cannot load page".
There is no errors in eventlog or in IE console. Even Fiddler does not give any information why IE could not able to load reports. It says response 200.
Reports are generated successfully, as I can see that in log.
I am not sure why this is happening with IE(8,9,10). Please check images below
Thanks
This could be due to the memory management problem in Internet Explorer, as you are fetching the 5 year data.
There is a work around for the memory problem.
->Go IIS
->Open your reporting Website
->Check which application pool its using
->Right click on that and recycle it.
->Then try generating the report.
Not sure if it resolves your problem.
I've seen a very similar issue recently - it started a few months ago, across multiple unchanged reports, and seemed to be triggered by hard or soft Page Breaks (I found that out from a lengthy process of elimination).
That scenario was SQL Server Reporting Services 2012 SP1, via the Native/Report Manager portal.
Does your report render with page breaks?
My solution was to set the Report / InteractiveSize / Height to 1000cm. Then for each hard page break, I disabled it for browser rendering by setting the Page Break / Disable property using this expression:
=Globals!RenderFormat.IsInteractive
The result is a little untidy in the browser, but renders with page breaks in other formats (PDF, Word, Excel). Importantly it stopped the browser freezing in IE.
Personally I have moved away from the report display control. It provides inconsistent display on different platforms (al least it did in 2013 when I did the lions share of converting a project).
Instead I render to PDF (Word or Excel) at the server and use an embed tag to display the content to the user. You are guaranteed to know what it looks like on the user screen that way. A level of caching is possible and its a lot easier to work with.
I have been experiencing the weirdest problem, that I can't even begin to troubleshoot. It is important that the webpage in this project I am working is 100% printable. As you can see the signature field below and the note field (with the string "erererer") shows great in Google Chromes print preview but not when I actually print it out using the Chrome browser. In fact, the note field just prints out the border and nothing else (looks like a white empty div with a border) and the signature field prints out everything but the actual signature. When I use google chrome to save the document as a PDF and then print it out directly from the PDF everything prints perfect. When I use firefox to print, the signature area prints perfect, but the note problem remains of it only printing the outter border.
I would greatly appreciate any suggestions on how to begin to fix this or any input on why this may be happening.
Many thanks in advance!
If you need accurate & reliable printability, going iText and PDF is a solution. You can render the page as PDF and it will show in the browser, and then print exactly as specified.
HTML is often inexact, has marks (page numbers etc) from the browser, and can be glitchy.
iText (latest versions) are available open-source, or commercially. There's also an older version available free. See: What is latest version of itext that is not AGPL?
As for your note field: maybe there's something weird with backgrounds, non-standard styling? , or fonts that aren't present? Try making it a plain vanilla table.
I have an application with crystal reports which I've just noticed has a fairly large issue. The treeview/drill-down menu on the left will not display in Internet Explorer, however it does work with other browsers (chrome/firefox/etc.). I've never used CR before (these are actually inherited, I haven't touched them), but I'm guessing it's an IE option that's not set some where. Any idea how to fix this?
EDIT:
Per the question about browser version, I am working with IE8. I did notice that when compatibility mode was turned off, it displays as I would expect. However, the app is supposed to handle IE7 (which I do not have access to) as well.