BlueCielo Meridian Enterprise 2017 Release Notes

BlueCielo Publisher

The following are known problems with this Publisher release:

• Document properties are not copied to the rendition when print stamps or signature pages are included in the job. This is an issue with the third party component that Publisher uses to render the additional text. There is no known workaround at this time and BlueCielo is researching a solution.
• Attempting to scan a new cluster node for rendering applications after connecting to a different configuration database can generate the error Execution request ... has no task code. To prevent this error, remove all cluster nodes and select rendering applications first before changing to a new configuration database. Re-add the cluster nodes after connection to the new configuration database.
• Rendering profiles configured for SolidWorks to PDF format, Autodesk Revit to BMP format, Autodesk Inventor 2016 to PDF format, and MS Visio to PDF format require Meridian Enterprise Server to be configured to not run as a service as described in the BlueCielo Meridian Enterprise Server Administrator's Guide. For Autodesk Inventor 2016 specifically, Inventor must run in interactive mode when publishing to DWF format in Express mode with the Create 2D snapshot option enabled.

• Rendering vector drawings to raster formats (BMP, TIFF) at 100% scale with the AutoVue rendering module can fail if the output image is very large. A workaround is to apply a smaller scale factor, for example, 50%.

• The AutoVue rendering module does not support filenames that contain commas. Rendering such files will cause errors that contain The requested operation cannot be performed on a file with a user-mapped section open and the publishing job will fail. To work around this issue, remove all commas from the filenames before submitting them for rendering.
• Errors can appear in the publishing log that read [BC Publisher Writing] ERROR: System.InvalidOperationException: There is an error in XML document when publishing TIF files to SharePoint. The issue is caused by invalid EXIF metadata in the files that SharePoint cannot extract.
• Rendering to PDF with the AutoVue rendering module in the landscape orientation does not work correctly for .doc and .txt files.
• The quantity of file extensions that is shown in the Input extensions field of an AutoVue rendering profile is not updated if different AutoVue components (2D or 3D) are installed after the rendering profile was created. You can resolve this by clicking Configure to open the INPUT EXTENSIONS dialog box and then close the dialog box and save the configuration. The quantity should then reflect the currently configured file extensions.
• In Meridian Enterprise Server Configurator, some rendering module option pages might not display correctly in Internet Explorer 10 and lower. This does not affect usability, however.
• On an AutoCAD 2014 or later rendering node:
  • The Meridian Enterprise Server program folder (by default, C:\Program Files\BC-Meridian Enterprise Server) and the Meridian Enterprise program folder (by default, C:\Program Files\BC-Meridian\Program) should be added to the TRUSTEDPATHS system variable in AutoCAD by clicking Tools>Options>Files>Trusted Location.
  • Set the InfoCenterOn value to 0 (zero) in the registry. Otherwise, an extra AutoCAD process will be started during rendering that can cause rendering jobs to fail.
  • AutoCAD rendering jobs that use the AutoCAD DWG To PDF.pc3 plotter option should have the setting Show result in viewer disabled. Otherwise, if Acrobat Reader is not installed, the rendering job might fail because of a Windows dialog.
• If the SharePoint library Require Check Out option is enabled and a feedback property is configured, updates of the feedback property will fail. Also, if the Document Version History option is enabled, publishing documents will create new revisions of the source documents.
• The first revision number of documents published to SharePoint is always 2 if the library is configured to use major revision numbers. If the library is configured to use minor revision numbers, the revision is number 1.0.
• The has the following limitations:
• If the AutoCAD rendering module loads an old Autodesk Mechanical Desktop drawing, the AutoCAD session might display a dialog stating “You cannot edit Autodesk Mechanical Desktop drawings in AutoCAD Mechanical. All AutoCAD Mechanical commands, including SAVE, are now disabled.” Rendering will not proceed until a user clicks the Close button in this dialog. If the button is not clicked, rendering will terminate when the publishing job’s configured timeout period has elapsed. This is a technical problem with AutoCAD. Such drawings should be upgraded or not rendered.
• The Oracle AutoVue rendering module can produce filled black rectangles around shaded models in the PDF output of Autodesk Inventor .idw and .dwg files. This can be prevented by enabling the AutoVue Document Converter option Spool print documents so program finishes printing faster.
• Printer drivers are not supported for creating renditions.
• If the Keep Modification Information option is enabled for a BlueCielo Meridian Enterprise destination vault, it is possible to produce inconsistencies between the source and destination systems. This can occur if the document is modified without updating the Modified file attribute and published again. An example of this is when title block properties are updated by the Meridian Enterprise PowerUser client.
• If the Add comment when document has been published option is enabled in the BlueCielo Meridian Enterprise system link, then publishing a batch of documents might fail and report an error stating "The object is currently being edited by another session." Disabling the option or using VBScript batch support will prevent the error.
• The AutoVue rendering module may fail to render files with names that contain characters that are not supported by the current Windows locale.
• The AutoVue rendering module does not support output of redlines in renditions. Use the AutoVue Desktop Deployment rendering module instead, which does support them but supports fewer rendering options.