SAP Knowledge Base Article - Preview

1915096 - Scheduling Crystal Report fails when set to use Custom database logon


  • Crystal Report is based on a stored procedure
  • Order of the parameters for stored procedure is changed during design
  • Scheduling Crystal Report works fine with using Original database logon information
  • Scheduling Crystal Report fails when using Custom database logon information with same data source settings, for example:
    • Error in File ~tmp.rpt: Database Connector Error: '22001:[IBM][CLI Driver][DB2/AIX64] SQL0433N Value "xxxxxxxxxx" is too long. SQLSTATE=22001 [Database Vendor Code: -433 ]'



  • SAP BusinessObjects Business Intelligence 4.0 (BI4.0)
  • Windows Server 2008
  • IBM DB2 9.7


SAP BusinessObjects Business Intelligence platform 4.0


original custom db database configuration config , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.