Produmex Scan Crystal Reports Printing Issues

This article describes possible Crystal Reports printing issues, reasons and solutions.

Possible errors:

1. “The operation has timed out”
2. “The type initializer for .rpt threw an exception”
3. “Error in File .rpt Operation not yet implemented”
4. Connection Errors

1. The operation has timed out

Known reasons:
- Wrong printer configuration

Usually this error happens when the "Run us User" who is configured in Produmex Service Broker service doesn't have enough right to use the printer.

Solution:

• Start ServiceBroker in console mode. If you can print with console mode, then it means that your Windows user has enough right to use the printer. Open the Produmex Service Manager and set the "Run us User" in the Service Broker configuration. You can change this setting of the ProdumexServiceBroker in Windows Services as well.
  
  
• In case you have a network printer try to install the network printer as a local printer for testing purpose.

2. The type initializer for .rpt threw an exception

Known reasons:
- Crystal Reports Runtime Engine and Add-on or ServiceBroker 32bit and 64bit versions mismatch

Solution:

Please double-check if you are using only 32bit or only 64bit for all the installed components.

3. Error in File .rpt Operation not yet implemented error

Known reasons:

- Using a font that is not supported by the CRR.

Solution:

- Change the font in the report file.

4. Connection Errors

Reason:

These errors occur because of the wrong database configuration in the report file.

Solution:

In case of HANA database system, you can use the HANA Report Setting Tool to configure the connection in a proper way.

http://builds.produmex.name/Utils/Standalone_HanaReportSettingTool/

In case of MS SQL system please use OLE DB connection type

Make sure 64bit B1CRHPROXY or HDBODBC is configured in ODBC Data Sources correctly on Produmex Server.