Summary #
This article is intended to be used as a troubleshooting guide for errors that arise from the use of the Run Crystal Report tool in a task.
Error returned from Crystal Reports – (0x80020009) #
Cause 1: A parameter required by the report has not been mapped within the Run Crystal Report tool.
Solution 1: Ensure that the report parameter is mapped within the Run Crystal Report tool.
Cause 2: A parameter in a sub-report that is already mapped from the parent report is being mapped within the Run Crystal Report tool
Solution 2: Remove the sub-report parameter mapping within the Run Crystal Report tool.
Cause 3: A resource that the report accesses is referenced by a mapped drive letter. For example; a database file resides on a file share, within the Crystal report’s data source the database file is referenced using a mapped drive.
Solution 3: Convert the mapped drive to a UNC path as follows:
- Open the crystal report in the report designer.
- From the main menu select Database ->Set Data Source Location.
- Expand the ‘Properties’ folder
- Right-click the ‘Data Source’ property and select ‘Convert to UNC’.
Cause 4: An invalid printer has been setup for the report.
Solution 4: Open the crystal report in the report designer. From the main menu select File ->Page Setup. Under ‘Printer Options’ put a tick in ‘No Printer (optimize for screen display)’.
Cause 5: The printer setup in the report does match the opereating system default printer.
Solution 5: Set up a printer in the report (Under File >Page Setup) to match the default printer on the machine where the TaskCentre Server is hosted.
Cause 6: Impersonation does not work when a report is printed.
Solution 6: Add the local system account to the list of permissions on the printer share as follows:
- Right-click the printer ->Properties ->Security tab.
- Click ‘Add’ to bring up ‘Select Users, Computers, or Groups’
- Click the ‘Objects Type’ button and add ‘Computers’ as an object type.
- Add the TaskCentre Server computer name.
Error 0x80047e528 (may also see variants 0x80047e52, 80047e528, 80047e528) #
Cause: Not fully understood why the Crystal runtimes return this error. Observation has shown that table logon succeeds but then fails at the parameter mapping phase.
Solution: Update the report’s Data Source so that it no longer uses an external Data Source Name (DSN.)
- Open the report in the Crystal designer.
- From the main menu select Database >Database Expert.
- Create an OLE DB (ADO) data source with the same parameters as the existing ODBC (RDO) data source, and click OK to save the changes.
- From the main menu select Database >Set Data Source Location.
- Change the location of the data from ODBC (RDO) to OLE DB (ADO)
‘Logon failed for table’ error even though the login details are correct #
Cause 1: The table logon details mapped within the Run Crystal Report tool contains a long password (Affects TaskCentre versions prior to build 4.5.1137)
Solution 1: Apply SR 4 Hotfix E (Build 4.5.1137) where the issue is fixed by development ticket 38198
Cause 2: The report’s Data Source references a non-existing DSN.
Solution 2: Using The 32-bit version of the ODBC Administrator tool( %windir%\SysWOW64\odbcad32.exe) recreate the missing DSN.
Cause 3: Sometimes just the fact that the report’s Data Source is set up to use an external Data Source Name (DSN) prevents table logon.
Solution 3: Update the report’s Data Source so that it no longer uses an external Data Source Name (DSN.)
- Open the report in the Crystal designer.
- From the main menu select Database >Database Expert.
- Create an OLE DB (ADO) data source with the same parameters as the existing ODBC (RDO) data source, and click OK to save the changes.
- From the main menu select Database >Set Data Source Location.
- Change the location of the data from ODBC (RDO) to OLE DB (ADO)
Tasks with a Crystal Report step produce the error code 0x800706be #
Symptom 1
The task fails at runtime and the event log records the following error (Where TASK_NAME is the name of your task):
Task ‘TASK_NAME ‘ was terminated or unexpectedly aborted. 0x800706be
Cause
The Crystal Report data source is set to login to the database using windows (Trusted) authentication. At runtime the task is unable to resolve the authentication chain.
Solution 1a
The simplest solution is to use database authentication in place of windows authentication. If this is not possible, use solution 1b.
Solution 1b
Change the TaskCentre Server service account from the default LocalSystem, to a domain account that is setup as a login on the database.
Symptom 2
Task fails where the Crystal Report export format is PDF, it occurs even if the report has no data source. The following error code is produced:
0x800706be
Cause
Version conflict between the TaskCentre CR runtime and the Crystal Reports designer.
Solution
Uninstall Crystal Reports from the system including the runtimes. Re-install by first installing the TaskCentre internal Crystal runtimes via the Configurator. Then install the regular Crystal Report application.