jfields

javax.servlet.jsp.el.ELException: An error occurred while getting property "result" from an inst ance of class com.tonbeller.jpivot.tags.OlapModelProxy From my expirence, when I recieve the "result" error, this meant there was a SQL Exception. Meaning the query to pull the data that was requested blew up. To debug, first turn on Analysis query logging. (In the Analysis Options) When you get the query that blows up, pull it out of the log and run it in a Query Analyzer. Should give you the actual sql error. Hope that helps.

With JS Pro, we were not able to use the jdbcDaoImpl because of the addition of multi-tenancy. I am not sure if it is the same with CE.

I ran into the same problem. I found that JS is no longer using acegi-security jar. Instead, springframework is being used. I use case was for MD5, but I would assume SHA would be similar. Code:<bean id="passwordEncoder" class="org.springframework.security.providers.encoding.Md5PasswordEncoder"/>

Code:Make sure you have the daoAuthenticationProvider uncommented. <bean id="authenticationManager" class="org.acegisecurity.providers.ProviderManager"> <property name="providers"> <list> <!-- not on by default <ref local="ldapAuthenticationProvider"/> --> <ref local="daoAuthenticationProvider"/> <ref local="anonymousAuthenticationProvider"/> <!--ref local="jaasAuthenticationProvider"/--> </list> </property> </bean> Make sure the jdbcDaoImpl is uncommented. Also becareful of the password encoder. Uncomment if you need it. I had to override to use the encoding that the external db used. <bean id="daoAuthenticationProvider" class="org.acegisecurity.providers.dao.DaoAuthenticationProvider"> <!-- jdbcDaoImpl --> <!-- <property name="userDetailsService"><ref bean="inMemoryDaoImpl"/></property> --> <!-- <property name="userDetailsService"><ref bean="userAuthorityService"/></property> --> <!-- <property name="passwordEncoder"><ref local="passwordEncoder"/></property> --> <property name="userDetailsService"><ref bean="jdbcDaoImpl"/></property> <property name="passwordEncoder"><ref local="passwordEncoder"/></property> </bean> This is the override to use the encoding that I use in the external db. <bean id="passwordEncoder" class="org.acegisecurity.providers.encoding.Md5PasswordEncoder"/> Override the jdbcDaoImpl giving the 2 querys that acegi will use to authenticate. I created views on the external db. That made it easier to call from here. The columns returned from these queries is important. Acegi expects the 3 columns from the first and the 2 columns from the second. The dataSource is just another bean i have set up in another file that has a jndi resource for the datasource informantion. <bean id="jdbcDaoImpl" class="org.acegisecurity.userdetails.jdbc.JdbcDaoImpl"> <property name="dataSource"> <ref bean="dataSourceGBS"/> </property> <property name="usersByUsernameQuery"> <value>Select username, password, enabled FROM v_js_user WHERE username = ?</value> </property> <property name="authoritiesByUsernameQuery"> <value>SELECT user_name as username, role_name as authority FROM v_js_user_roles WHERE user_name = ?</value> </property> </bean> Hope this helps. Note: This method will no longer work with JS v3.5. I had to switch to use jaas authentication.

I have the same issue, and don't have an answer on how to fix. Some notes that i have learned though. 1. Per cube, try not to exceed more than 16 dimensions. JS cant handle it. 2. Make sure dimensions to fact table are all indexed. Doing both of those and monitoring the database for 'hung threads' has gotten this error to occur less often. We see it most often when the db gets stressed more and it seems like the query returns no data and you get the 'results' error. That is all I have learned about this error. Maybe some of my knowledge will help. Jeremy

I had the same problem when I upgraded to JS 3.5.1. What I found to be the problem was when I imported the backup from 3.0, the encypted passwords for my db connections were re-encrypted with the 3.5 import. I had to re-enter the all the passwords for all my db connections in the jasperserver console. Hope that helps. Jeremy

Sridevi, I had received the same error with Tomcat. My problem was I did not have the correct path to tomcat in the default_master.properties file that you create for the buildomatic. My first thought is double check 'appServerDir' and verify you have it correct. Otherwise I am not sure about Resin. jfields

Sridevi, I used the export script that came bundled with JS Pro 3.0 to back up my JS database. Also did a mysqldump just in case. Once the database was backed up, I followed the steps in the 3.5 install guild to use the 'buildomatic' scripts. The scripts have you drop the 3.0 database, create a new database based on the 3.5 architecture, setup defualt users, and import my 3.0 data. That part went smoothly. I can log in as the default users (superuser, jasperadmin) all seems fine. My problem is when I modify acegi to authenitcate against an external db. Other than that, the upgrade went very smoothly. HTH, Jeremy

Log in to JS as jasperadmin. Manage the repository. I created a folder called 'Data Sources'. Highlight the data sources folder in the left side nav, and click the button called 'Add Resource'. Select 'Data Source'. Fill in the details for your external db. When you upload a report to JS, you will be asked what data source the report should use. Select 'from respository' and from the drop down select the data source for your external db. Hope this helps.

I am attempting to upgrade from JS Pro 3.0 to JS Pro 3.5.1. I have some custom code for acegi to do the authentication. I override the jdbcDaoImpl bean and implement this bean in the mtDaoAuthenticationProvider. This does not work. Throws the following error on server start up: java.lang.IllegalArgumentException: Cannot convert value of type [org.acegisecurity.userdetails.jdbc.JdbcDaoImpl] to required type [com.jaspersoft.jasperserver.multipleTenancy.MTUserDetailsService] for property 'MTUserDetailsService': no matching editors or conversion strategy found I am guessing I am missing one piece in there somewhere. Thanks in advance for your help. Code:<bean id="jdbcDaoImpl" class="org.acegisecurity.userdetails.jdbc.JdbcDaoImpl"> <property name="dataSource"> <ref bean="dataSourceGBS"/> </property> <property name="usersByUsernameQuery"> <value>Select username, '1' as tenantId, password, enabled FROM v_js_user WHERE username = ?</value> </property> <property name="authoritiesByUsernameQuery"> <value>SELECT user_name as username, role_name as authority FROM v_js_user_roles WHERE user_name = ?</value> </property> </bean><bean id="mtDaoAuthenticationProvider" class="com.jaspersoft.jasperserver.multipleTenancy.MTDaoAuthenticationProvider"> <!-- jdbcDaoImpl --> <!-- <property name="userDetailsService"><ref bean="inMemoryDaoImpl"/></property> --> <property name="userDetailsService"><ref bean="internalUserAuthorityService"/></property> <property name="MTUserDetailsService"><ref bean="jdbcDaoImpl"/></property> <property name="tenantService" ref="hibernateTenantService"/> <property name="passwordEncoder"><ref bean="passwordEncoder"/></property> </bean>

Is it possible to display a date in the title bar of a Ad Hoc report? What I mean is, that I have an Ad Hoc report that an user enters a startDate and endDate as params. The user would like to have the entered startDate and endDate to appear in the Ad Hoc report title. I have gotten the dates returned in the field list but do not see a way to the dates into the title bar. Any ideas? Thanks in advance. Jeremy