Not all images showing in Reportviewer, or when printed. from a winforms project - vb.net

I am using SQL Express 2012 Advanced and Visual Studio Pro 2012.
I have developed a report that displays signatures (stored in a database) on the report in reportviewer, one signature on each line. The report works fine as long as there aren't too many pages of data. Once the number of pages reaches around 100-200 pages, the images fail to load. You can see where this occurs if you watch the page count go up it counts very quickly by single numbers as it is rendering in the reportviewer then slows down and starts counting by jumps in numbers. If I lower the size of images saved in the database, I can get more images to load. So it seems to be a problem with the amount of memory the report is using.
Is there a cache setting for report viewer? Better yet, is there a way to know programmatically if the images are failing to load and to commit an action at that point?

Related

SSRS Datadriven subscriptions Limitations

I am trying to generate 10000 pdf reports into the windows file share location using SSRS data driven subscription methodology and I found that when I run for small bathces and it works and it surely fail when I give 10000 at a time. This behavior is unpredictable and not able to scale the solution. Ex:
When I put 10000 load it generates 2700 and fails rest but when I try to run failed records in another batch then it gets me the PDFs. It fails sometime with small batch sizes also. No proper reason logged.
Thanks

Pause execution till Chrome is done loading

I'm currently in the process of developing a file which is used to fill in a form based on the data from the sheet. The issue I'm facing is that the page gets refreshed for each entered field for one section of the code. The refresh time varies based on the computer.
My current solution is to induce a wait of approximately 5-6 seconds which can be inefficient based on the terminal used. Is there a way that the execution can be paused simply till the page is done loading? Also, there are two versions of Excel that are in use, essentially 2013 and 2003. Not sure if that's relevant but I've had to sort out numerous compatibility issues.

SSRS Portrait/Landscape, Page numbers & TOC

I'm planning to use .NET / SQL Server / SSRS to migrate an old application.
I've just started migrating the report over to SSRS (SQL Server 2012) and have bumped into a few limitations. I've searched the internet and found a few workarounds for them, but when combining them all it seems I've hit a brick wall.
So:
1. The report has both landscape and portrait
2. The report has a table of contents with page numbers
3. The footer has the page number of the report
Now I have read that the only way to get around the #1 limitation is to have multiple reports (some portrait and some landscape) and combine the PDFs later on using something like iTextSharp (not a problem). However, this will then break #2 and #3 as page numbers will reset for each new report.
Is there a way to handle this? I haven't even worked out how to do #2 yet (as there is nothing out of the box) but the concept remains the same.
I would have thought this was basic reporting functionality, but obviously not!
Thanks.
No, you can't easily handle point #2 if you have object that could span over multiple pages depending on data, i.e. Tablix... so 99% of the reports! ;)

Lost my reference to Microsoft.InteropFormTools in a VB.NET 2008 project

I've got an older VB.NET 2008 project, which uses Crystal Reports. In order to access the .rpt files I used Microsoft.InteropFormTools assembly. This has worked OK for a number of years. What this does is allows the user to specify what amounts to parameters to the reports in the Crystal Reports, and then click a button and out prints the report. (The user is not interested in previewing the report, so it prints directly to the printer, using Crystal.) The one problem, which I've never been able to figure out, is that sometimes (how, and under what circumstances I don't know, because I can reliably reproduce the error) loading the Crystal Report will cause an error flag to come up. Next Crystal will insist that the user enter parameters to the report before it previews them. OF course the users don't know what's going on, so what we've done in the past is just have the user start it over again, and Crystal normally is happy and sends the report to the printer.
However, we've got new users coming on board to do this, and they're not as forgiving. When I wrote this app 4 years ago, I let the CPU be “Any CPU”. I'm wondering if that could be the root of my problems with these Crystal reports not coming out. So, I've gotten into the project, and changed it from “Any CPU” to “x86”, which really is more appropriate, especially since our old version of Crystal is 32-bit. However, now that I've done that I've got a new error message popping up. Visual Studio 2008 is telling me that, “The system cannot find the reference specified”. In this case the missing reference is Microsoft.InteropFormTools. No other changes have happened to this application in 3 years, besides my changing the project configuration from “Any CPU” to “x86”. Could that be what's causing it to not be able to find the path to Microsoft.InteropFormTools?

Intermittent Crystal Reports error "The request could not be submitted for background processing."

We are running Crystal Reports on a Windows Server 2008 with .NET framework 3.5 SP1.
I have seen many causes of the general error "The request could not be submitted for background processing." on other forums, however they tend to be persistent and repeatable affecting just a single report due to a specific formatting issue with a specific report.
We are seeing this error with the below stack trace, intermittently.
It affects multiple different reports we have.
It affects one particular report more frequently than other reports.
Once a report is affected the same error will often appear in multiple reports at approximately the same time eg. for the next 10 minutes.
The same report run with the same parameters may work when run again (soon after) or the application may need restarting before the report can be successfully re run.
These reports all worked previously without issue. No change in server or code seems apparent which would have precipitated this error. All code behind for this is VB.NET
We have had difficulty reproducing it in test environments and upgrading to the latest version of Crystal has not helped at all.
Any help or suggestions that you might be able to make to resolve this issue would be appreciated.
"The request could not be submitted for background processing."
at CrystalDecisions.ReportAppServer.Controllers.DatabaseControllerClass.ReplaceConnection(Object oldConnection, Object newConnection, Object parameterFields, Object crDBOptionUseDefault)
at CrystalDecisions.CrystalReports.Engine.Table.SetDataSource(Object val, Type type)
at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSourceInternal(Object val, Type type)
--- End of inner exception stack trace ---
at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)
at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSourceInternal(Object val, Type type)
at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSource(DataSet dataSet)
at "USER CODE"
After many days, finally I discovered what is the root of problem, in case you are including jpg images in your report.
The thing is that CR for VS2008 or later versions, can’t handle jpg files in CMYK mode. CR only can handle jpg files in RGB mode.
It’s funny that lower versions of CR (the one that came with VS2003) could handle any kind of jpg files. Thanks, Crystal.
For me the issue was with the Temporary Crystal Report that gets generated in the TEMP folder in Windows. There is a limit to the number of Temporary Crystal Reports that can be generated by Crystal report engine while processing it in a loop. Either the space in Temp folder runs out due to low memory in C drive or the limit of reports is reached after which in one single run crystal report cannot export further. It will give the error mentioned in question.
For me this issue was recurring at every 500 reports that were processed (I was generating the reports say, for a year and exporting them to a system folder one by one using my application)
The solution is simple. Always close and dispose the temporary .rpt Crystal Report file after exporting it .
for i as integer=0 to reportcount -1
Dim rpt as New MyCrystalReport
Dim filename as String = "MyReport" & i & ".Pdf"
//Query the DB obtain the dataset then set the datasource to the report
...
//Export the report
rpt.ExportToDiskCrystalDecisions.Shared.ExportFormatType.PortableDocFormat,fileName)
rpt.Close()
rpt.Dispose()
next
Isolate the report generation code.
Our final resolution was to take the code that was generating the report and move it into its own isolated service. Our original service then calls our new Crystal service with the relevant parameters and Crystal RPT file. This is obviously a costly solution as it involves modifying all report generation code to call the Crystal service instead. The Crystal service does not exhibit the error. The code had not changed besides that, so we can only presume the cause of the error was some interaction of the Crystal reports engine and the environment within our application.
Is there a chance the report object is leaked in the server's memory? I ran into a similar case where the report object was being stored into a Session object, so the report didn't need to get reloaded as the user navigated between pages. However, when the user was done with the report, the object remained in the Session, and wasn't cleaned up properly when the Session was destroyed by the server. I had to add a bit of code in the Session_End event in global.asax to find the report object and call the dispose method on it.
The fact that this appears intermittently but then affects all reports for a matter of 10 minutes makes me think it could be session-related. In my situation the server reached a limit on the number of reports that could be created on the server (in memory) because they weren't being released. The symptoms were similar to yours.
Hope this helps!
Try this: If you left any blank space at crystal report(header,footer or any sections) suppress it. that's all. I had this problem and i fixed this way.
I too have come across such issue, where I figured out the Column having Photographs was creating the issue. The way out was to convert the photograph (Datatype Image in SQL Server) from .NET Data set to byte and then save it as Bitmap. After , that this same BMP file can be converted to bytes and replaced to appropriate column of the identified row. By this the space reduced to a great extend and then after exporting the Report document and Datatable was disposed properly.