After migrating from BI4.2 to BI4.3, we discovered a problem with a FHSQL report. Upon changing the SQL, all of the result objects disappear. We can re-add the objects, and the query functions normally.
I tried another test with a very simple repor...
We have set up two new BI4.3 SP2 environments in preparation for an upgrade from BI4.2.
In both environments, the BI launchpad Guided Tours don't seem to be working, or I just can't figure out how to use them.
The "Create a hyperlink object" and ...
I am working on converting a Java web application that uses the BO Java SDK, from BI4.2 to BI4.3. The application includes calls to com.crystaldecisions.report.web.viewer.CrystalReportViewer to generate a CR viewer.
The problem is that when I use ...
I found the SAP note regarding the changes required for SDK programs to comply with the crypto changes in BI4.3 SP02. I have two questions:
1) All the references I see relate to Java. Are there no changes to .NET SDK projects?
2) Our BO servers a...
We have found that in the Java and COM SDKs, it's possible to log in using the host name of a CMS that is currently unavailable.
For example, my cluster @BO runs on three hosts: boe_a, boe_b, and boe_c. With the Java SDK, I can call CrystalEnterpr...
Snowflake. It's a hack to manually add the keypair settings to an ODBC driver: https://community.snowflake.com/s/article/How-to-set-up-ODBC-Driver-with-key-pair-authentication-to-connect-to-Snowflake-on-Windows I don't know if there's a better way, b...
So it looks like there is a workaround in which you make a registry change to point the ODBC driver to the key file. Not ideal, but we might have to go with that option.
John, have you found any more info on this? All the other platforms that we work with are supporting keypair, but not BO. It'll be an issue for us if it's not introduced before Snowflake disables user/password in November.
I checked the Platform REST API docs and I don't believe it's possible with the REST API.A while back I created a Java program object to do this, because we had a big problem with sessions not being closed. You might be able to adapt it to your need...
Exceptions in Tomcat logs are pretty common; unless you're actually having a problem they can likely be ignored.With that said, it looks like it has something to do with SSL.