Table of Contents

6. Printing

6.1. The name of the printer is incorrectly configured

6.1.1. Check printer name

1. Make sure that the printer name in printer properties is the same as the Local Printer Name on the Printers Setup window. For more information about setting up the printers please see: Setting up the printers

6.1.2. Redirected printer

If the printer is redirected, try to install the printer directly on the server where the Service Broker runs.

6.2. The “Run as user” for Service Broker service is not allowed to use the printer

Enable printing permissions for the Run as user for Service Broker service.

Open the ‘Printer properties’ of the printer. On the Security tab select the ServiceBroker user and allow the following permissions:

6.3. Label won’t be printed on a PDF printer

Issue
When printing with a virtual printer, the printer does not open the document after printing.

Solution
The document does not open after printing if the Service Broker runs as a service. If you want to use the PDF printer for a demo or in case you want to test your label, then you should start ProdumexServiceBroker in console mode.

If Produmex Service Broker runs as a service, stop it. Then run BxServiceBroker.Console.exe as an administrator. The file is located in C:\Program Files (x86)\Produmex\ServiceBroker

Configure the ProdumexServiceBroker with an administrator user other than system user.

Install a PDF printer that allows automatic saving. Configure an output location and automatic document numbering for the ServiceBroker user. Make sure that you configure the PDF printer in a way to show the document after generation.

Please note: We recommend to try multiple PDF printers because not every PDF printer is supported.

6.4. Default printing solution

1. Check whether the correct printer name is set.

2. Configure the database connection Open the .rpt file in Crystal Reports designer. Print a preview document and change the connection to the right database. Save the report.

6.5. Custom printing solution

1. Check the custom printing settings.

For more information please see: Custom printing

2. Open rpt file in Crystal Reprts designer. Print a preview document and change the connection to the right database. Save the report file. If you had to configure the database connection, import the report to SBO again. Make sure that you modify the report ID in the user query if needed.

3. Check if the report can be printed from SAP Business One.

6.6. Advanced printing configurations

With the advanced printing configurations printing issues caused by incorrect server/database connection settings in Crystal Reports can be solved.

To add the advanced printing configurations, run the following query on the database:
SQL 

INSERT INTO "VALI002"."@BXPCONFIG" ("Code", "Name", "U_BXPDescr", "U_BXPValue", "U_BXPVType", "U_BXPRowVr") 
VALUES('BXMPRAO', 'BXMPRAO', 'Crystal Reports connection parameters', '54', 1, NULL)

A new record will be inserted to the BXPCONFIG table. With this record the following parameters can be set:

  • PRINTERADVANCEDOPTIONS_SETTABLELOGON = 1;
  • PRINTERADVANCEDOPTIONS_SETTABLECONNECTION = 2;
  • PRINTERADVANCEDOPTIONS_SETSUBREPORTS = 4;
  • PRINTERADVANCEDOPTIONS_DISSOCIATESIZE = 8;
  • PRINTERADVANCEDOPTIONS_USEPRINTERSETTINGS = 16;
  • PRINTERADVANCEDOPTIONS_USECONNECTIONCLONE = 32;
  • PRINTERADVANCEDOPTIONS_USESETTINGWITHNAME = 64;

The value of BXMPRAO is the sum of the value of the enabled parameters.

The default and recommended value is 54. It means that the Settable connection (2), the Set sub reports (4), the Use printer settings (16) and the Use connection clone (32) parameters are enabled (2+4+16+32=54) by default.

Do not change the default value. If the issue persists, please contact Produmex support.

Enabled settings:

  • Settable connection (2): Creates a new connection structure with the actual parameters.
  • Set sub reports (4): Applies the (1) and (2) setting to the sub reports as well.
  • Use printer settings (16): Uses a non-standard access to printer settings.
  • Use connection clone (32): Uses a clone of the connection structure.

Other settings that can be enabled:

  • Settable log on (1): Resets the server/database connection to the actual in the tables of the existing structure. This setting is not taken into account if the Settable connection (2) setting is also enabled.
  • Dissociate size (8): Enables the ‘Dissociate Formatting Page Size and Printer Paper Size’ option.
  • Use setting with name (64): Uses both the standard and non-standard access to the printer settings.

Known cases:
* The error message 'Not supported within subreports'

Set the value to 1

2017/07/19 14:24 · csuhaa

6.7. Printing does not work on SBO 9.3 PL04

Starting from SBO 9.3 PL04, SBO includes a new SAP Crystal Reports runtime engine version 13.0.22 (technical version number 13.0.3500.0). In the past the SAP Crystal Reports runtime engine version 13.0.14 (technical version number 13.0.2000.0.) was used. Produmex Scan will support the new Crystal Reports version from version 18.2.

You can check the current SAP Crystal Reports version on Control Panel > All Control Panel Items > Programs and Features.

Workaround for Produmex Scan version 18.1 or older

In order to print with version 18.1 (or older) of Produmex Scan on SBO 9.3 PL04, make the following modifications:

1. Adjust the app config file of the Service Broker. Open the BxServiceBroker.Service.exe.config file from C:\Program Files (x86)\Produmex\ServiceBroker\ with a text editor. Insert the following code after the already existing “dependentAssembly” tags. 

  <dependentAssembly>
    <assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture="neutral"/>
    <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="CrystalDecisions.ReportSource" publicKeyToken="692fbea5521e1304" culture="neutral"/>
    <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
  </dependentAssembly>    
  <dependentAssembly>
    <assemblyIdentity name="CrystalDecisions.Shared" publicKeyToken="692fbea5521e1304" culture="neutral"/>
    <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
  </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="CrystalDecisions.Windows.Forms" publicKeyToken="692fbea5521e1304" culture="neutral"/>
    <bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.3500.0"/>
  </dependentAssembly>