Meridian Release Notes 2010 R5.4


This Meridian 2010 R5.4 release (Build 2010 5.4.0.17197) includes bug fixes and an enhancement.


Software Requirements


The following software is required to successfully use Meridian.


Server



  • Windows Server® 2008 R2 

  • Windows Server® 2012  

  • Windows Server® 2016

  • Windows Server® 2019

  • Microsoft® .NET 3.5 Framework (Required to use Meridian's .NET component,
    if .NET is not detected during installation, you are offered the option to have .NET installed for you.)


Client


(32- or 64-bit editions)



  • Microsoft® Windows 7, 8, 8.1, 10 

  • Microsoft® .NET 3.5 is recommended ( .NET is used if available, otherwise C++ is used)


Note: For client machines running Windows XP and Windows 8 that do not have .NET or the Visual Studio 2008 C++ Redistribution package installed:
Download and install the Visual Studio 2008 C++ Redistribution package before installing a Meridian printer.


Hardware Requirements


The minimum hardware requirements for Meridian are:


Server



  • 350 MB of RAM

  • 175 MB of hard disk space (for application)


Client



  • 256 MB of RAM

  • 25MB of hard disk space (for the application)


Enhancement


When a print request does not include a filename for the output file, Meridian now provides a default filename.


Bug Fixes


The following bugs were resolved.
























































Bug



Description



Resolution



10125



Print conversions from client machines failed when the location of the default temp folder was changed in the Meridian User Interface General tab.



Code updates related to retrieving and setting the temp directory address resolved this issue.



12051



When user impersonation for UNC paths (Impersonate) was set for file copy/move in the Meridian User Interface, and the Overwrite Method setting was set to alter filenames instead of overwriting existing files, static printers using a UNC output folder continued to overwrite any existing PDF files that had the same name.



Code updates related to how the overwrite setting was monitored resolved this issue.



13316



In the Meridian User Interface, when the PDF Naming setting was changed to "Ask me each time" to prompt the user for a filename and save location, and PDFDirectory was not specified, the user was not prompted to provide a filename and save location when converting a document.



Code updates related to how creating an output directory was handled resolved this issue.



13351



When a client clicked the Cancel button in the Save as PDF dialog box, , an output PDF was still created on the server.



Code updates related to how temp files are handled resolved this issue.


Note: Install the updated client file for all users to implement this resolution.



14323



When Meridian was installed on a 2008 R2 server and an static networked printer set up, a linked network printer installed on a client 2012 server was not able to fetch the output PDF from the 2008 R2 server.



Code updates related to output file naming resolved this issue.


Note: Install the updated client file for all users to implement this resolution.



14325



When the Overwrite Method setting was set to alter filenames instead of overwriting existing files in the Meridian User interface, and a client machine converted files with the same file name, the client machine fetched the output PDF with the original filename, instead of the more recent conversion with the altered file name.



Code updates related to how the overwrite setting and output file names were monitored resolved this issue.



14804



Relaunching the Meridian User Interface (UI) after changing the Printer Profile’s page orientation to Landscape or Portrait created invalid settings for page orientation.



Code changes made related to page orientation settings resolved this issue.


Note: If edits have been made to the page orientation in the Printer Profiles section of the UI, before opening the Meridian UI each time, restart the activePDF Meridian Service.



14831
14832



When using the local machine (where Meridian is installed) to convert a file to PDF and move a copy to a user-specified folder, the original copy in the output folder was deleted.



Code changes made related to save method settings and how file extensions are handled resolved this issue.


Note: Install the updated client file for all users to implement this resolution.



14936



In the Meridian User interface, if the FTP Options were configured to upload output PDFs, and the overwrite setting was set to alter filenames instead of overwriting existing files, when source files with the same file name were converted, the output PDF with the original filename, instead of the more recent conversion with the altered file name was sent to the FTP site.



Code updates related to how the overwrite setting and output file names were monitored resolved this issue.



 


Installation and Getting Started


Installation instructions and information on using the Meridian UI for configuration is available in the Meridian Quick Start Guide:


http://documentation.activepdf.com/Meridian/meridian_qs/index.htm