I'm trying to publish this PRD file that I created and it works on my machine when I do a preview. But when I pusblish it to the server it returns "Report validation failed".
The prpt file uses a transformation as a source, and that transformation looks into an excel file that changes daily.
My assumption the BI server is having some problems working out the report is that the sources files that are used are accessed locally on my computer. So I changed the access type to UNC path. While using UNC, I tested it on my machine and it still works. I published it to the server and I still get the same error.
Any suggestions other than looking at the log file of the server?
If you have sub-reports on your report, check if you changed the connection on each sub-report.
If you have defined any parameters check those parameter's properties (Double click on the parameter fields) there is some check boxes , untick the check box and check whether its working or not. if it is working check your parameters that you have defined.
Related
I am new to Pentaho (5.01) and Open ERP(7.0) I have an existing report that I have added a field (text), that is a selection in the corresponding module.
In the Pentaho Report Designer Preview the value of the field is correct, however after loading the .prpt into OpenERP the report runs (PDF) and all the other fields are populated correctly except this one.
Is there some setting I am missing in OpenERP that is preventing display of this field? The field value is also correct in the DB (Postgres) table.
The issue was that the pentaho.server.url had been hardwired to an IP address.
In our OpenERP installation we have three servers, production, demo (copy of production) and development, The pentaho.server.url stored as a record in the ir_config_parameter table in the Postgres DB on developmen, has been pointed to the Pentaho report server for production. So even though I was loading the correct .prpt report file on the development system the query was pulling data from the production system which did not have the correct DB data or structure.
I deciphered this by debugging the report activation and calling code in the core.py (community/pentaho_reports) module.
I created an schema in Schema Workbench and publish with no errors, but when I got in BI Server with the standard user admin, I choose New->jpivot, then it display the name of the schema I created but it does not display the cube. For reference the error I get from catalina.out is:
17:11:45,174 ERROR [PentahoDataSourceResolver] PentahoXmlaServlet.ERROR_0002 - IDatasourceService.UNABLE_TO_INSTANTIATE_OBJECT
org.pentaho.platform.api.data.DBDatasourceServiceException: javax.naming.NameNotFoundException: Name [Esquema Salario] is not bound in this Context. Unable to find [Esquema Salario].
Name [Esquema Salario] is not bound in this Context errors usually appear if you use JNDI name, which is not defined on your system. So, I assumed, that this is the name of the datasource, which you reference while publishing Mondrian schema files to BI server.
Xml file with Mondrian schema definition generated by Schema Workbench does not contain any information regarding how to connect to database. So, you need to specify these details when you upload your schema file on BI server (It's done on step 4 below).
But first you have to create the connection itself (steps 1-2):
Create new JDBC datasource:
Define connection parameters:
If cubes still don't appear after these steps, you may republish your cube: follow same steps as in step 1, but select "Analysis" instead of "JDBC" in the end.
Upload the xml file, generated by schema workbench and select the datasource, which you have created on step 2. .
If cube still does not appear - check your log again. If you see the same Name is not bound error, you may try to restart your BI server application (new connections usually get recongnized immediately, but if you had a connection with same name before, than you might need to restart tomcat).
If that does not work, than once again, check log files. I guess, you'll have some different error in this case.
I had the same problem as the OP (blank screen when clicking New View) with the latest version of Pentaho BI server 7.1 (latest at the moment) and even with the 6.0 version one, Pivot4J SNAPSHOT 1.0 plug in version (latest as of today), Schema Workbech 3.14 (latest as of today).
And as, in line with OP, my catalina.out log was also spitting the Name [DatasourceName] is not bound in this Context. Unable to find [DatasourceName].
After several trials and errors I noticed the problem showed up when I checked the "Register the XMLA Data Source" when publishing the schema on Schema Workbench. So to fix the problem I just unchecked it before publishing.
Another way to fix this is going to the Manage Datasources option on the BI server, Import Analysis, choosing the schema created by Schema Workbench, AND manually setting the data source parameter value EnableXmla to false and saving changes. Now the schema should show up when clicking on Create New > Pivot4J view.
So I've designed a report in Pentaho Report Designer 3.9 and previewed it and ran it on my machine and everything works fine.
I have an input paramater that is a dropdown list and gets its values from a query called Vertical-List.
Now the drop down works on my machine. However, when I publish the report to the Online interface and try to access it, I get a message that says "The Specified query 'Vertical-List' is not executable here". I don't know what that means and what to do. It worked this morning and suddenly it stopped working.
Please help a brother out.
here is the query that generates the drop down
SELECT
`verticals`.`vertical_id`,
`verticals`.`vertical_name`
FROM
`verticals`
Double check your datasource and query, especially the parameters. If you have parameters, remember that a parameter is read in the Pentaho Report Designer as ${parameter_name}.
Also double check that you have defined the datasource in your BI Server.
We have one report that when run throws an error stating "Database login failed". I have 20+ reports configured the same way that execute without any problems. In the Crystal Reports Designer, I verified the database and everything is good. The sql queries used to generate the report look good.
The reports are run from an ASP.NET application. We're not using a report server. We're using the 13.x runtime on the server. Reports are defined in CR Designer and passed parameters from the ASP.NET application.
Can Crystal store a username and password in the report file? How do I clear any saved values? Any other ideas? I'm a bit lost here since everything else is working just fine.
Yes. Crystal can store authentication/connection info in the .rpt file. You can override this with your ReportSource definition by setting parameters.
It most definitely does NOT store account/password in the RPT file.
You will need to explicitly set the authentication credentials.
It does not store the password. It does store the ID most of the time. The reason some reports work sometimes has to do with if Windows authentication indicates you have access to the data.
The safest most consistent way to run reports is to use the ID/password evertime, although in some cases, if it's expecting Windows authentication only, putting the ID/password will cause it to fail.
I've inherited a project (without a handy handover) that contains reports published to a Reporting Server (2005).
MY SSRS knowledge is 4 years stale, so I need your help.
I need to edit one of the published reports, is this possible?
I also want to peek into the Data Source on the RS, because that's probably where I can change stuff.
I'll add more info as I get a better understanding of what exactly to ask.
EDIT: I found a project for some of the reports, opened up in VS2005 BI.
Still, how do I see where the Data Source gets its data?
It brings back 56 fields but I don't know which tables/stored procs/queries are used to get these.
Yes you can.
1st - to edit the published reports: Browse to the folder containing the report source you want on report server (web server). On the right side click 'Show Details'. Now click the properties icon under the 'Edit' column. Near the bottom you will see two links: Edit & Update. Click edit and the source RDL file will start to download. This is the actual report source.
You can import this right into a VS2005 report project and have full access for modifications.
2nd - As to the project you found: After opening an RDL file for editing, click the 'Data' tab. directly under that you will see a drop down list labeled 'Dataset:'. A report can have one or more datasets. These are the actual queries that generate report data. Also clicking '...' will allow you to see other properties of each dataset, such as parameters, etc.
You can run a profiler on your server, then run your report. The profiler give you most info about your query or stored procedure.