I am curious about the phase "Accessing Data" that occurs between the time I log into the database and the time that the report says it is "Reading Records". I'm speaking about the words in the bottom left hand side of Crystal. When I run this report from a remote location away from the database it takes up to 45 minutes to go through the accesssing data phase. The funny thing is, I checked the SQL Server 2005 activity logs and found something.
(Background info: Running XP locally, MS 2003 server for the DB operating system, XI Crystal with MS SQL 2005 database using the OLE DB ADO: Microsoft OLE DB Provider for SQL Server - Driver)
Each time I run the report I get three sets of errors one tells of the login failure and the other tells you the state.
1. When I kick off the report:
Login failed for user "crystal" [Client: xxx.xx.x.x} where X represents my IP addy. Then the activity log also records: ERROR: 18456, Severity 14, State 8.
State 8 is = to "The password is incorrect."
2. About 40 minutes after I kick off the report I get:
Login failed for user "crystal" [Client: xxx.xx.x.x} where X represents my IP addy. Then the activity log also records: ERROR: 18456, Severity 14, State 5.
State 8 is = to "User ID is not valid."
3. I get one more error RIGHT as its about to actually go into the reading records phase. This time its the same error as #2.
The thing is, I'm not entering my user id/password over and over again, I enter it once, and Crystal does its thing. For some reason, its banging its head against the wall and then resolving itself. Had it actually been a bad user ID or password, it wouldn't run.
Does anyone have any ideas how to resolve this or improve my performance? Is there a better driver to use? Any thoughts or ideas?
(Background info: Running XP locally, MS 2003 server for the DB operating system, XI Crystal with MS SQL 2005 database using the OLE DB ADO: Microsoft OLE DB Provider for SQL Server - Driver)
Each time I run the report I get three sets of errors one tells of the login failure and the other tells you the state.
1. When I kick off the report:
Login failed for user "crystal" [Client: xxx.xx.x.x} where X represents my IP addy. Then the activity log also records: ERROR: 18456, Severity 14, State 8.
State 8 is = to "The password is incorrect."
2. About 40 minutes after I kick off the report I get:
Login failed for user "crystal" [Client: xxx.xx.x.x} where X represents my IP addy. Then the activity log also records: ERROR: 18456, Severity 14, State 5.
State 8 is = to "User ID is not valid."
3. I get one more error RIGHT as its about to actually go into the reading records phase. This time its the same error as #2.
The thing is, I'm not entering my user id/password over and over again, I enter it once, and Crystal does its thing. For some reason, its banging its head against the wall and then resolving itself. Had it actually been a bad user ID or password, it wouldn't run.
Does anyone have any ideas how to resolve this or improve my performance? Is there a better driver to use? Any thoughts or ideas?