Making use of E10 ODBC credentials in Crystal

Epicor ERP 10
1

Have been trying to make use of the “ODBC Connection” functionality in the Company Maintenance, Email and Reporting tab. I have verified the credentials are correct, and can run the report locally IF I have an ODBC connection set up for my machine.

I’ve followed Support’s instructions to create a new ODBC(RDO) connection within the report itself and change the data source accordingly, but no luck. The error being generated now is “Crystal Report Windows Form Viewer / Failed to open the connection. Failed to open the connection. x2vvpx0nwfp {E7C6DEE0-1B73-46B2-8BE5-404761849478}.rpt”

This is short is what we’re doing:

  1. Create an ODBC connection (SQL Server Native Client 11.0) in the ODBC Data Sources on the Development machine (have attempted both with Integrated Windows authentication and SQL Server authentication). The default database is set accordingly, to the Production database. At the end of setup, run the Test Data Source, which is successful.
  2. Open up the Report in Crystal Developer on the Development machine.
  3. Go to Database, Database expert.
  4. Open the ODBC (RDO) under the “Create New Connection”. Click the Make New Connection option.
  5. The ODBC (RDO) window displays, Data Source Selection. The new connection is showing in the list of Data Source Names. Highlight it, click Next.
  6. The Server, User ID, and Database are already filled in. Enter the password. There is a Trusted Connection checkbox which we have both tried to select, and left deselected with no success.
  7. Click Finish. Are returned to the Database Expert page, with the new ODBC (RDO) source shown. Click Ok to be returned to Developer.
  8. Click Database, Set Datasource Location.
  9. Highlight the “old” connection in the upper portion of the screen, then highlight the “new” connection in the lower portion of the screen, then click Update. The new connection successfully replaces the old connection in the upper portion of the screen.
  10. Click Close to return to developer.
  11. Save the report.
  12. Attempt to run the report in Epicor…get the error specified above.

Any ideas what we’re missing?

2

i don’t use the odbc connection within epicor. i have a .dsn file on a network drive that connects the crystal report to a sql server.

3

Thank you for the reply, Paul. So you have all the clients referencing this DSN file rather than each client having its own DSN entry?

4

Yes. Its a single .dsn file for any crystal report that requires it.

5

How do you embed that in the report, to reference the single .dsn file, instead of each client having an individual ODBC connection?

6

place the .dsn file on a shared drive. (make sure it all works first). in crystal report, you will need to create a new connection. select “create new connection:” -> ODBC -> “Find File DSN”. Select the file from your network share.