PK83927: Crystal Report Viewer/Query Engine Error occurs when trying to r un a Crystal Report

APAR status

• Closed as Permanent restriction.

Error description

• cq_version : 7.0.1.x (7.0.1.4)
  DB_server_OS_Vendor : Windows
  DB_server_OS_Version : IBM DB2 v8.x, v9.x
  (Not happens on Oracle 10g, MS Access )
  
  Description :
  
  An Crystal Report Viewer/Query Engine occurs when trying to run
  a Crystal Report, if a record contains certain multibytes
  characters in a field.
  
  Error messages are:
  [Crystal Report Viewer/ Database Connector Error: ' ] in
  ClearQuest Windows Client.
  [Crystal Report Viewer/ Query Engine Error: 'Error Code:
  0x8004005, Sources: Microsoft OLE DB Provider for ODBC Drivers,
  Description: [DataDirect][ODBC DB2 Wire Protocol driver]Error in
  row.] in ClearQuest Windows Client.
  [Crystal Report Viewer/ Query Engine Error: 'Error Code:
  0x8004005, Sources: Microsoft OLE DB Provider for ODBC Drivers,
  Description: [DataDirect][ODBC DB2 Wire Protocol driver]String
  data code page conversion failed. Error in column 3.] in
  ClearQuest windows Client.
  [Exception/ Unable to load message ID 23190 from resources.
  Message parameters are: msgid=23190 details= - failed to run
  report. Details - failed to run report engine.] in ClearQuest
  RCP client.
  (See attachments of screen shot)
  
  Problematic multibytes are:
  Above sign  (UTF+32A4)
  doller sign (UTF+3326
  squire meter sign (UTF+33A1)
  (Refer to
  http://ja.wikipedia.org/wiki/Unicode%E4%B8%80%E8%A6%A7_3000-3FFF
  )
  
  Affected clients:
  
  ClearQuest Windows Native Clients
  ClearQuest Eclipse RCP Clients
  
  Steps to reproduce:
  
  1) Create a sample user database (SAMPL) in IBM DB2 database.
  2) Launch the ClearQuest Windows Client or Eclipse RCP client.
  3) Create a defect record, input the problematic characters in
  the headline field, and save it.
  4) Go to the Public Query > Report > Defect Detail (All) or
  Defect Summary (All), run the report.
  5) The error occurs.
  
  Business Impact:
  
  
  Potential business impact is HIGH because
  
   - it is not acceptable workaround to permit manually to input
  the problematic characters.
   - it is hard to prevent users from input problematic Multi
  bytes characters.
  
   - if the problem characters is stored in the Notes Log field
  once, it is not possible to get rid of them by users.
  
   - if customer is using lots of Crystal Reports, this issue
  likely happens in future.
  

Local fix

Problem summary

• Crystal Report Viewer/Query Engine Error occurs when trying
  to run a Crystal Report with certain multibytes characters
  in field.
  
  Tech Note 1392684 explains the situation.
  

Problem conclusion

• After an investigation, we determined that this is not a
  defect in ClearQuest code, so we cannot fix it.  For the
  problematic multibyte characters, DB2 with the 932 codepage
  and Crystal Reports have different encodings, so Crystal
  Reports cannot decode certain characters and then throws an
  exception.  If the user creates the user database with the
  UTF-8 code page, the report can be run successfully.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels