Conversion and batch printing errors - SmartPlant Foundation - IM Update 48 - Help - Hexagon

View rendition errors when batch printing Microsoft Office files

Error Messages

You receive the following error messages when batch printing multiple Microsoft Office files:

Failed to print the following files:

Failed to generate view rendition for [file name].

File can not be found: [file name].

The view rendition generated for [file name] is discarded due to the above failures.

Possible Cause

These errors could occur if view rendition generation fails. A view rendition is required for batch printing of Microsoft Office files.

Solution

Follow the steps in View rendition (CSF) will not generate.

File conversion (CSF/PDF) fails from the command line

The following are some troubleshooting tips for CSF/PDF conversion failure from the command prompt.

• Make sure you have opened Microsoft Office after installation on the SmartPlant Markup Plus Server and addressed all prompts that arise.

• Microsoft Office file formats must be converted to the intermediate XPS format using the Microsoft Automation API before a CSF file can be generated. You can test XPS conversion by opening the file in Microsoft Office on the SmartPlant Markup Plus Server and doing one of the following:

  • Click File > Export > Create PDF/XPS Document > Create PDF/XPS.

  • Save the file as an XPS Document.

  • Print the file using the CSF Writer.

  Record the time it takes to convert to XPS. If the file is failing to convert to CSF, see Cannot view large PDF files using View and Markup for instructions on increasing timeout values. The time you recorded will help.

• Files containing invalid data, such as invalid URLs or print titles, incorrectly formed print titles set across multiple cells, links, or pop-up notifications, cannot be converted to XPS, and CSF generation fails. Open the files using their native applications to fix invalid data and acknowledge any pop-up notifications so that the files can be converted to the intermediate XPS format.

  • Alternatively, you can modify the BIPrint.ini file to ignore all URLs including any invalid ones:

    • Go to [installation location]\Brava! Enterprise\CSFWriter and open the BIPrint.ini file.

      If you are using a version prior to SmartPlant Markup Plus 2019 Service Pack 1, the folder is: [installation location]\SmartPlant\Markup\Blazon\Blazon Enterprise\CSFWriter.

    • Add the file extension to the [DisableHyperlinks] parameter, for example:

      [DisableHyperlinks]

      FileExtensions=docx

  • If a file continues to fail and you are using SmartPlant Markup Plus version 2019 or earlier, you can try an alternative to XPS conversion:

    If you use this alternative, the CSF conversion might take longer, and it might cause a reduction in visual fidelity.

    • Go to [installation location]\Brava! Enterprise\CSFWriter and open the BIPrint.ini file.

      If you are using a version prior to SmartPlant Markup Plus 2019 Service Pack 1, the folder is: [installation location]\SmartPlant\Markup\Blazon\Blazon Enterprise\CSFWriter.

    • Make sure the [PrintIfSaveAsXPSFailed] parameter is set to Yes.

    • Remove the file extension from the [SaveAsXPSImplementedFor] parameter, for example:
      [SaveAsXPSImplementedFor]

      FileExtensions=doc,htm,html,mht,mhtml,mpp,ppt,pps,pptx,ppsx

• Files containing high resolution images are converted to lower quality JPGs during processing. To increase resolution, convert these files to EMF as the intermediate format:

  If you use this alternative, the CSF conversion might take longer.

  • Go to [installation location]\Brava! Enterprise\CSFWriter and open the BIPrint.ini file.

    If you are using a version prior to SmartPlant Markup Plus 2019 Service Pack 1, the folder is: [installation location]\SmartPlant\Markup\Blazon\Blazon Enterprise\CSFWriter.

  • Remove the file extension from the [SaveAsXPS] and the [SaveAsPDF] parameters.

• If what you see does not match what you see in the native application, fix the data so that it is correct in the print preview of the native application, or when exported to a fixed format such as XPS, PDF, or CSF.

• Go to the folder where the original file is located and look for a text file with the same file name as the file. For example, if test.docx failed to convert and is located in C:\temp, the test.docx.txt file is located in C:\temp. This text file contains error messages explaining why the file failed to convert.

  • If it contains the following error message, contact support.

    File = c:\temp\Test.docx ~ License Expired ~ Invalid License ~ publish_error

  • If it contains one of the following error messages, see Check CSF Writer settings for conversion.

    File = C:\Temp\Test.docx ~ Unable to load file: C:\Temp\Test.docx ~ Can't open source file(s) ~ Error opening one or more files ~ publish_error

    File = c:\temp\Test.docx ~ Job aliveness check failed ~ publish_error

    File = c:\temp\test.docx ~ Exception processing filepublish_error

  • If it contains the following error message, set the TEMP and TMP system environment variables using the below steps.

    File = c:\temp\test.docx ~ Can't open source file(s) ~ Critical CDL Error: Print Publishing: Temp folder not found (0x005B): c:\temp\test.docx ~ Error opening one or more files ~ Unable to load file: c:\temp\test.docx ~ publish_error

    • Right-click This PC and click Properties.

    • Click Advance system settings and then Environment Variables.

    • Set the system variables TEMP and TMP to %SystemRoot%\TEMP.

    • Click OK to dismiss the dialog boxes and save your changes.

• Go to the Job Processor Status section of the SmartPlant Markup Plus Server Status Page.

  • If the section contains the following error messages, save the file to your computer in the same file format as the Microsoft Office version on the server and try converting the file again.

    

File conversion (CSF/PDF) fails from SmartPlant Foundation

The following are the most common reasons for CSF/PDF conversion failure.

• The SPFUsers user ID must have Delete and Read/Write permissions to the File Service and the Remote Services temp directories, for example, C:\Windows\Temp\SPFFileService and C:\Windows\Temp\SPFAlternateRenditionService. If the File Service cannot delete the temporary files or folders created during CSF/PDF processing, the entire transaction fails.

• The SPFRemoteServices user ID must be added to the Administrator user group.

• The SPFServer and SPFRemoteServices user IDs must have Local Launch and Local Activation permissions defined in the DCOM configuration (using dcomcnfg.exe).

• Verify that all settings and steps are complete as described in Install and Set Up SmartPlant Markup Plus Server Software.