locked
Login failure issue with Crystal reports connecting to SQL Server 2005 RRS feed

  • Question

  • Hi All,

     

    My  application  uses  "crystal reports" control to integrate some reports that can be viewed from within the application.

     

    I'm getting a login failed (due to bad password SQL State 8) error when I bring up the report from within the application. The report runs fine outside the application with the same username password.

     

    - I've checked several times to make sure that I'm passing the correct username/password from the application.

    -  All letters in the password are lower case. There is not case-sensitive issue.

    - I printed the username and password on a pop-up to see what values are passed , and they are correct.

    - A single test page that uses the same version of "Crystal Reports" control , using the same username/password, brings up the same report works fine.

     

    I guess , my question is:

     

       Is there a way to trace the login failure event on the SQL Server side to see what is the value of the password that is being sent by crystal reports control?

     

    I'm using Crystal Reports XI with sp2.

    SQL Server 2005.

     

    I appreciate the help.

     

    Thanks,
    Satish

     

     

    Tuesday, November 6, 2007 6:41 PM

Answers

  • I don't think you can find out the password being passed by the application. Of course you can get the login name

     

    Madhu

     

     

    Wednesday, November 7, 2007 2:15 AM
  • Ya Hi,

    Please use the ODBC(RDO) connection string then your problem will be solve...

     

    for details visit. www.connectionstrings.com

     

     

    Best of luck

    Monday, April 7, 2008 10:46 AM
  •  Osama Alborbar wrote:

    Try creating a new user at the SQL server (new login other than sa) with blank password

     

    This is just asking to be hacked and a violation of best practices.  Do not follow this advice.  Blank passwords should never be established on a SQL Server Login account.

    Tuesday, November 4, 2008 6:15 AM

All replies

  • I don't think you can find out the password being passed by the application. Of course you can get the login name

     

    Madhu

     

     

    Wednesday, November 7, 2007 2:15 AM
  • What do you mean..."outside the application?"

     

    It sounds like it's using impersonation or windows authentication.

     

    Please post your connection string without the login and password.

     

    Adam

    Wednesday, November 7, 2007 2:22 AM
  • When I say "outside the application", I mean creating a test asp page that passes the hardcoded username and password to the crytal report control, and pull a specified report. This page has nothing to do with the application.

     

    I'm using SQL Server authentication, and the connection string is fine because the application is able to connect to the database. I read the connection string and send the parameters to the crystal report control in the application.

     

    Thanks,

    Satish      

      

    Wednesday, November 7, 2007 5:34 PM
  • Ya Hi,

    Please use the ODBC(RDO) connection string then your problem will be solve...

     

    for details visit. www.connectionstrings.com

     

     

    Best of luck

    Monday, April 7, 2008 10:46 AM
  • Try creating a new user at the SQL server (new login other than sa) with blank password and set the Crystal Report conection login ID as that user.

     

    It worked for me.

     

    Good lock.

     

    Caution:

    Jonathan's reply below is right. This is too risky. Do not follow my advice. Look for other solutions

    Tuesday, November 4, 2008 3:43 AM
  •  Osama Alborbar wrote:

    Try creating a new user at the SQL server (new login other than sa) with blank password

     

    This is just asking to be hacked and a violation of best practices.  Do not follow this advice.  Blank passwords should never be established on a SQL Server Login account.

    Tuesday, November 4, 2008 6:15 AM