When you have a report that runs fine in Crystal Reports, but it fails when you run it in Crystal Enterprise, it is generally a data access problem.
When you run the report in CR, the report engine is run by the user ID with which you logged in. When it runs in CE, it is run either by the page server service (for on-demand reports) or the job server service (for scheduled reports). By default these services run under the local system account.
At the end of the day, 90% of these problems are caused by the data source not being available to the page/job server services.
Common steps to try: 1. If the report is written against an ODBC DSN, is the DSN a system DSN and not a user or file DSN? Make sure the appropriate type is used.
2. If the report is written against a native driver (eg. SQL*Net or DB2) does the local system account have permission to run this driver? Try running the page/job server services under a named user ID that you know can access the data.
3. Install CR on the same machine as the page/job server and test the report there.