Symptom
- In a Unix environment, Crystal Reports scheduled against a Sybase IQ or SQL Anywhere database fail with the error message, "Error in File ~tmp1cexxxxxxxxxxxx.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: -100 ]"
- The .rpt filename varies from one attempt to another.
- The report can be viewed successfully on demand, and also works correctly in the Crystal Reports designer.
Environment
- SAP Business Intelligence Platform 4.0
- Sybase IQ or SQL Anywhere as a reporting database
- Linux, Solaris, or AIX
Reproducing the Issue
- Create a Crystal Report based on a Sybase IQ or SQL Anywhere environment, then publish it to Enterprise.
- Populate the report properties, especially the Database configurations.
- View the report on-demand and confirm it views successfully.
- Schedule the report to Run Now. It fails with the aforementioned error.
Cause
- This issue was raised as a potential product defect, as ADAPT01664333.
- It was determined that, when using the libdbodbc12.so driver, this behavior is as expected.
- SAP Business Intelligence Platform 4.0 uses Unicode ODBC API, yet the Sybase IQ ODBC driver defaults to the ANSI API.
Resolution
- The resolution is to configure the Sybase connection to use the Unicode API (UTF-8).
- On the Crystal Reports Job Server, edit the ODBC configuration file, $INSTALL_DIRECTORY/sap_bobj/enterprise_xi40/odbc.ini
- Find the data source associated with the Sybase connection, then add the following line to its properties:
- ~UserDefinedTextEncoding=UTF8
- Save the odbc.ini file, then re-start the Crystal Reports Job Server for the change to take effect.
- Repeat the same steps on all Crystal Reports Job Server machines.
Keywords
ADAPT01664334 , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-CRS , SAP Crystal Server , Problem
Product
Crystal Reports Server 2008 V1