• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 428
  • Last Modified:

SQL 2005 Failure Audit When Running Crystal 10 Reports

SQL 2005 database records this error message whenever running Crystal Reports -- reports run fine:

Event Type:     Failure Audit
Event Source:   MSSQLSERVER
Event Category: (4)
Event ID:       18456
Date:           9/29/2008
Time:           12:25:44 PM
User:           N/A
Computer:       NAMEY
Description:
Login failed for user 'validaccountname'. [CLIENT: 172.21.0.111]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00   .H......
0008: 06 00 00 00 52 00 4f 00   ....N.A.
0010: 43 00 4b 00 59 00 00 00   M.E.Y...
0018: 07 00 00 00 6d 00 61 00   ....m.a.
0020: 73 00 74 00 65 00 72 00   s.t.e.r.
0028: 00 00                     ..      
NOTE: I've changed some of the names in this sample, but the error remains valid.  The error type is "password mismatch"
0
sneeman759
Asked:
sneeman759
  • 7
  • 5
1 Solution
 
mlmccCommented:
How are you calling the report?

mlmcc
0
 
sneeman759Author Commented:
Database connection established during report creation using OLE DB (ADO), SQLOLEDB.
0
 
mlmccCommented:
Are you getting this from the Crystal designer or when you call Crystal from an application?

mlmcc
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
sneeman759Author Commented:
Both.
0
 
mlmccCommented:
Even with the error, the report shows what it is supposed to?

Do you have a table in the report you aren't using?

mlmcc
0
 
sneeman759Author Commented:
All reports reflect correct data.  They originally pointed to a SQL 2000 database.  This database was migrated to SQL 2005 on a different server.  I edited each report to use the new data source.

The only difference between the two databases: the db account password was changed between the two databases.

Is there embedded information within the report that's not getting reset?
0
 
sneeman759Author Commented:
FYI: I created a new report from scratch using the same connection information.  No errors.

I hope this doesn't mean I must recreate every report (over 100).  When I modified the old reports, I selected the new data source to generate preview; set data source location; verify database, etc.  I thought these settings were retained with the report - minus the password.  When I open these modified reports to run them, they are pointing to the correct database.  

I'm missing something.
0
 
sneeman759Author Commented:
When running Crystal Reports 10 (SP6)...
"Failure Audit" is logged at the database when the "OLE DB (ADO)" connection window opens -- before I enter the password.  Server, User ID, and Database values are correctly set; only missing password.  Appears the report is automatically trying to connect to the database with a blank password.  Why?

Same thing happens with new reports.

When Crystal Enterprise 10 (SP6) runs scheduled reports, same thing happens and report fails.  If I manually run the report, it runs and no errors.
0
 
mlmccCommented:
How did you edit the reports to use the new data source?

mlmcc
0
 
sneeman759Author Commented:
Using "set data source".  I've found a means to overcome this problem (derived from documentation on SAP's site):

-  Create DATALINK.UDL and configure to use OLE DB for SQL Server; set database user name and password (checked to store password)
-  Copied DATALINK.UDL to server where Reports are executed
-  Opened report in Crystal Reports; clicked on "set database location";
-  In the bottom window pane, create new connection; OLE DB (ADO); check box "use data link file"; selected DATALINK.UDL
-  In Connection window, database and user name filled in as defined in UDL -- no need to enter password; select database from pull-down
-  Returned to 2-pane window (top: current data locations; bottom: new connections); click on database name in top pane then click database name for desired connection in bottom pane -- click "update" button.
-  Save and run

No more database errors and the report run like a champ.
0
 
mlmccCommented:
Is that how you changed the data source before?

mlmcc
0
 
sneeman759Author Commented:
Pretty much -- minus the data link file, containing the saved password.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now