CR report scheduling fails

[Former Member]

1. While scheduling CR reports (from infoview) on BO 3.1 enterprise, facing following errors u2013

- Error in File ~tmp933858664557440.rpt: Unable to connect: incorrect log on parameters. Details:Database Vendor Code: 18456].

- Error in File ~tmp1bfc5852b405c50.rpt: Unable to connect: incorrect log on parameters. Details:Database Vendor Code: 1005]

2. Using MSSQL 2005 and cannot save the password for the data source in the ODBC data source.

3. Issue is even with default connection, when logged in as user with administrative privileges

[fritzfeltus]

Have you set your logon credentials in the report object's Process > Database information in the Central Management Console?

[Former Member]

yes I did.

CMS, Audit and PM databases is on SQL Server 2005

Data Source for the failing report is SQL Server 2000 (SP4)

Following steps has already been suggested: -

1. Open the ODBC - edit the database username and password Click Test Connection and then try report/s schedule Result: Success

2. When the ODBC connection has been created on the workstation, the short "user name/password" might be used for accessing the Lotus Notes database instead of using a full "Server\Domain name\User name".

3. Again try to re-enter the parameters required for scheduling like database password, export format, destination, etc. schedule the report.

4. To ensure that the ODBC connection properties are set to use SQL authentication, perform the following steps: - Open the report in Crystal Reports.

- Click Database > Set Datasource Location.

- Click on the plus sign next to Properties to check the connection properties. The Trusted Connection attribute should not be checked. If Trusted Connection was selected when the connection was created, it will be listed with a value of "1" (true).

- Change the value to "0" (false) to correct it.

- Publish the report to Enterprise. (The report should run successfully when set with standard database object properties)

5. Modify the default DSN entry in ODBC settings.

6. Need to check settings with data provider. Try to create new connection of data provider if possible with B

Edited by: Siddhi Godhankar on Jan 27, 2009 2:49 PM