SAP Knowledge Base Article - Public

1215804 - OLAP reports sends blank password to database when refreshed in Crystal Reports

Symptom

  • Login with no password sent to the database.
  • Database monitoring tool shows login errors.
  • If a lockout policy is set up on the database, passing the blank password after three attempts locks out the report from the database.
  • When refreshing an OLAP report in Crystal Reports, a blank password is passed to the database before the logon screen appears.
  • How to avoid sending empty logon to the database, when refreshing an OLAP report in Crystal Reports?

Environment

  • SAP Crystal Reports 2008
  • SAP Crystal Reports 2011
  • SAP Crystal Reports 2013
  • SAP Crystal Reports 2016

Reproducing the Issue

  1. In Crystal Reports, create a report off any data sources using an OLAP connection.
  2. On your database side, monitor the database logons.
  3. In Crystal Reports, refresh the report.
  4. On the database side, notice a logon error for an attempt to login with the user name you used to create the report, with an empty password. Why is this occuring?

Cause

  • Crystal Reports does not store the database password in a report, but does store the user name used to create the report. And by design, when refreshing a report in Crystal Reports, it always send a logon to the database with an empty password. If it fails, it then prompts for the user name and password to use to connect to the data source.

Resolution

  • To change the behavior, and avoid sending an empty password when refreshing an OLAP report in Crystal Reports, add the registry key: AlwaysAttemptOlapLogon, and set the value to No     
       
    WARNING 
    The following resolution involves editing the Microsoft Registry. Using the Microsoft Registry Editor incorrectly can cause serious problems. Use the Microsoft Registry Editor at your own risk. For more information, see the SAP Knowledge Base Article 1323322
          
           
    1. Open the Microsoft Registry Editor.
      ( In MS Windows, under the menu Start, select Run, and type: regedit )
          
    2. In the Microsoft Registry Editor, navigate to the path corresponding to the version of the product used:
         
      • Crystal Reports 2008
          
        • For 32bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Database
             
        • For 64bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports\Database
            
             
      • Crystal Reports 2011, 2013, 2016:
           
        • For 32bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\SAP Business Objects\Suite XI 4.0\Crystal Reports\Database
               
        • For 64bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database
                
               
    3. Right click on the Database key, and select: "New - String Value"
          
    4. Set the String value to: AlwaysAttemptOlapLogon
         
    5. Set the value to: No
         
    6. For the change to take effect, close and re-open Crystal Reports.

Keywords

CR 9 MHF PWD SP ONLINE ANALYTICAL PROCESSING LOG ON EMPTY NULL Crystal Reports OLAP Data Source Logging On , c2013152 , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Bug Filed

Product

Crystal Reports 2008 V1 ; SAP Crystal Reports 2011 ; SAP Crystal Reports 2013 ; SAP Crystal Reports 2016