Skip to main content

Error - 'Logon failed for table xxx' when a crystal report step is failing

Updated over 2 weeks ago

There are several causes for this error. Ultimately, they are all because crystal reports cannot log on to the tables in the database, so it must be determined what is causing the connection to fail.
​
Codeless Platforms have advised that Crystal Reports should be using an OLEDB connection within the report as this is more stable and reliable.
​
To check the connection type and/or update the connection type, follow these steps:

  1. Open the report in crystal designer.

  2. In the menu bar, click Database and select Set Datasource Location.

  3. On the Current Data Source, expand the properties node. The details of the connection saved in the report are now displayed.

To change the connection type, follow these steps:

  1. In the Replace With pane, expand OLE DB.

  2. Double-click Make New Connection.

  3. Enter the Server details, user credentials of an account to log into the SQL server and select the database to connect to.

  4. Click Next

  5. Click Finish.

  6. Expand your new connection, dbo, tables.

  7. Update each table by selecting it in the Current Data Source pane.

  8. Select the relevant table under the Replace With pane and click Update.

  9. When all tables have been updated, click Close.

  10. Save the report template.

  11. Open the failing task in TaskCentre.

  12. Open the crystal report step.

  13. Import the update report template into the task.

  14. Apply the credentials in the Database Tables Logon Information.

  15. Apply any Mapped Report Parameters.

  16. Click OK to save the step.

  17. Click OK to save the Task.

  18. Queue the task.

Did this answer your question?