I'm facing an error with a .prpt file.
While running the prpt in report designer it just works fine .
But when the same prpt ran in PUC (user console), the report contents are not displayed.
It is a simple report containing total 8 columns with only text and number fields in the detail section and only labels (formulated also) in headers.
Please help with your valuable tips
Check the server logs - there'll be an exception. I've seen this before - frequently it is due to layout issues, not sure why but for some reason in some cases the server bombs, yet the client does manage to render it. Double check the obvious like overlapping elements etc.
Also check the version of your PRD client, and the exact version of the reporting libraries on the server, they MUST match.
I've seen this happen when you have a prpt file that was created in an older (or newer) version of PRD than the server. You'll get javascript errors and onscreen you'll just see a blank page/tab. Make sure your version of PRD matches the server version.
Related
I've created a report in Pentaho Report Designer 6.0.1 with dependent parameters. Published the same to Pentaho BI Server 6.1. The report runs perfectly in the PRD in Preview and i'm able to see the data. Also, there are no errors thrown during publishing the report as well. But after publishing, when i try to launch the report, the link opens up blank with the loading spinner just rotating forever. I checked the logs in the biserver as well (catalina.out and pentaho.log), apart from 1 error during launch (java.io.UTFDataFormatException: encoded string too long: 78805 bytes), there is no other error seen. Not even during the report load.
Can someone please tell me what is going wrong here?
Check your SQL behind the report. I've had some similar problems whilst trying to run some reports from the server on 6.0.
The problem I faced had to do with me not manually typing the correct typecasts. e.g. active = 1 instead of active = TRUE (basically I was creating "bad" SQL's). After I made those changes they launched correctly again.
I struggled with this issue for too long before finally tracking down how to avoid/fix it. It seems like something that should be on StackOverflow for the benefit of others.
I had an SSRS report where the query worked fine and displayed the string results I expected. However, when I tried to add that field to the report, it kept showing "ERROR#". I was eventually able to find a little bit more info:
The Value expression used in [textbox] returned a data type that is
not valid.
But, I knew my data was valid.
Found the answer here.
Basically, it's a problem with caching and you need to delete the ".data" file that is created in the same directory as your report. Some also suggested copying the query/report to a new report, but that appears to be the hard way to achieve the same thing. I deleted the .data file for the report I was having trouble with and it immediately started working as-expected.
After you preview the report, click the refresh button on the report and it will pull the data again creating an updated rdl.data file.
Another solution to this issue is to click Refresh Fields in the Dataset Properties menu.
This will update the list of fields, and force SSRS to get new data, rather than relying on a cached version.
I have installed and configured SSRS using SharePoint integrated deployment mode and have been able to successfully run a report from SharePoint. I created a custom deployment application that will upload all reports and datasets as well as create all data sources and make the proper connections between them when necessary.
I have one report that failed and I need to manually mess with the reports connection to a data source but I found that the drop down does not contain the options to let me manage its shared data sources (see example below).
In this image you can see the option that I am missing. Please excuse the colors, this is the best image I could find online in a pinch.
This is only happening in one environment so there must be a configuration change I am not thinking of to show these options. Here are the things I have already checked:
The account I am using is in the sites Owners group and has full control of everything, including the report file.
The item is being uploaded as a Document content type for some reason, but I edited properties and changed that to Report Builder Report content type.
The Report Server Integration site collection feature has been activated.
All of the Reporting Service content types have been added to the list.
I would revert to deployment from BIDS to debug this issue. It will perform some validation during that process and possibly return meaningful errors.
So this turned out to be caused by one of our customizations. We had an old custom javascript function that was named the same as a SharePoint javascript function that has something to do with those drop down actions. Hope this helps someone else.
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?
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.