Windows 10 build 1809 and Server 2019 updates causing Integration Platform Printing Failure Follow

Avatar
Raul Soto

Symptom

The Integration Platform no longer is able detect and process triggers when automating BarTender.

You will see the following errors in Administration Console and/or Integration Builder

          The input data file '<trigger name>' was not processed because one or more actions failed to run.
          Review all integration actions, correct any failures, and resend the input data file.
      

          Print job '<Document Name>' did not complete due to the following error:
      
You will see the following message in the BarTender Print Scheduler log:

The log is located at C:\ProgramData\Seagull\Services\Logging\PrintScheduler.Service.txt


          Error while running Print Scheduler task 'Print Document subtask 1 format affinity request'. 
          Details: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
      
You will see the following errors in the Windows Event Viewer

        Faulting application name: BarTend.exe, version: 11.0.8.3153, time stamp: 0x5b86ef32
        Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
        Exception code: 0x40000015
        Fault offset: 0x00000000000761c9
        Faulting process id: 0x1660
        Faulting application start time: 0x01d4b99757898e7b
        Faulting application path: C:\Program Files\Seagull\BarTender Suite\BarTend.exe
        Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR100.dll
        Report Id: 7dc1b75c-4eec-4b27-bf15-7e78454848e3
      

Environment

  • BarTender 2016
  • Integration Platform
  • Windows 10 build 1809
  • Windows Server 2019
  • Any of the following version 1809 October through December 2018 Windows updates are installed:

Fix

Note: Please see our Windows Version Compatibility with BarTender. BarTender 2016 is not considered compatible with Windows 10 build 1809 and later.
This issue has been resolved in BarTender 2019. If you have an active support agreement, you're able to upgrade to BarTender 2019 at no cost. If you have any questions about getting a BarTender 2019 license, please contact our sales department.

Workarounds

The following are workarounds for BarTender 2016 and provide alternative methods in which the Integration Platform can launch and run BarTender to print.

These options may negatively affect print performance. If you have a high through-put environment, we recommend you upgrade to BarTender 2019.

Enabling the "Prompt for data input" option

  1. In your Integration Builder File and particular print actions (Print Document, Print BTXML script, Print Command script etc.), find the "prompt for data input" option under the print option overrides section and enable this option.PromptForData.png
  2. Save your Integration Builder file and redeploy your Integration File back to Administration Console.

Changing Print Scheduler Service Configuration settings

  1. Go in to the BarTender installation directory (e.g. C:\Program Files\Seagull\BarTender Suite).
  2. Find the PrintScheduler.Service.exe.Instance.config file. Make a copy and backup this file to a different location.
  3. Open the new copy of the PrintScheduler.Service.exe.Instance.config file. Within this file, find the following lines and values:
    
    NumberOfPrintEngines="3"
    DynamicEngineScaling="true"
    StartOnDemand="true"
            
  4. Change these lines and values to the following:
    
    NumberOfPrintEngines="1"
    DynamicEngineScaling="false"
    StartOnDemand="false"
            
  5. Save the file with the new changes.
  6. Copy the new PrintScheduler.Service.exe.Instance.config file with the updated changes back to the BarTender installation directory and override the existing file.
  7. Open Administration Console and go to the Windows Services section.
  8. Restart the BarTender Integration and Print Scheduler Services.
    RestartServices.png
  9. At this point, the Integration Platform should now be able to detect triggers to print, but you will still see the Integration error messages. If you want to make them not show you can do the following:
    1. In your Integration Builder File and particular print actions (Print Document, Print BTXML script, Print Command script etc.), set the verification option to "Queue print job and continue immediately."QueueAndContinue.png
    2. Save your Integration Builder file and redeploy your Integration File back to Administration Console.

Remove Windows Update

You may also choose to remove the offending update from your computer. However, please be aware that there are several other important fixes included in those updates. You should review the release notes and your environment carefully before choosing to remove or prevent the Microsoft updates.

Was this article helpful?

Please sign in to leave a comment.