Главная / Поддержка / Вопросы по RightFax / Вышел Хот фикс 3 для RightFax 9.3

Вышел Хот фикс 3 для RightFax 9.3

RightFax 9.3 Feature/Service Pack 1b Hotfix 3 Readme

This readme file provides late-breaking or other information that supplements the RightFax documentation. Hotfixes are the means by which RightFax product updates are distributed from the Captaris Web site. A Hotfix may contain updates for system reliability, program compatibility, performance improvements, and more. All Hotfixes are cumulative. Each contains new fixes plus all the fixes from previous Hotfixes.  

By the time you receive this software, updates to other RightFax software may be available. To obtain updates, go to http://www.captaris.com/support/downloads/rightfax/93/index.html.

IMPORTANT: Before installing any hotfix or upgrading a RightFax server, you must back up the entire \RightFax directory structure, the fax board directory (usually the \RFBoard folder), and the SQL database for RightFax. To ensure that all necessary files are properly backed up, stop all RightFax services and close all RightFax applications before beginning the backup process.

Contents

What is Included in this Hotfix?

Hotfix 3 for RightFax version 9.3 Feature/Service Pack 1b contains numerous updates to the core server components, fax board drivers, and RightFax clients. Hotfix 3 also includes updates to the Lotus Notes integration, and Exchange integration. See a complete list of updates here.  This hotfix will update both North American and International versions of RightFax.

WARNING: Applying this hotfix will overwrite all files associated with the hotfix, regardless of the dates and version numbers of those same files already installed on your server. Verify a functional backup before continuing.

Enhancements and New Features

Listed below are the enhancements and new features introduced to RightFax 9.3 Feature/Service Pack 1b with the addition of this hotfix.

  • Support for Microsoft Internet Explorer 7. The addition of this hotfix adds support for Microsoft Internet Explorer 7 with Windows XP and Windows Server 2003.

  • Support for Adobe 128-bit Encryption. The addition of this hotfix adds support for 128-bit encryption security of Adobe PDF documents.

  • Support for SAP ECC 6.0. The addition of this hotfix adds support for SAP ECC 6.0. An updated Connector for SAP Guide can be obtained at the Captaris RightFax

    documentation page located at http://www.captaris.com/support/documentation/rightfax/index.html.

     

Download Hotfix 3

From the RightFax server, download RightFax931_HotFix3.exe from http://www.captaris.com/support/downloads/rightfax/93/index.html

Applying Hotfix 3 to RightFax Servers

Apply this update to all version 9.3 Feature/Service Pack 1b RightFax servers before installing on RightFax remote servers.

IMPORTANT: To apply this update to Exchange Servers, .NET Framework 1.1 or greater must be installed.

WARNING : Before applying this update, if you have one or more Brooktrout TR1034 fax boards installed, you must confirm that the file btcall.cfg in the \RightFax\DocTransport\Brooktrout folder is not set to read-only. If it is, remove the read-only attribute from this file prior to applying the hotfix . Installing the hotfix with this file set to read-only will fail to properly update the file and in the process will render the fax boards inoperable.

Hotfix 3 setup options

The installation of Hotfix 3 for RightFax 9.3 Feature/Service Pack 1b can be customized by using the setup switches below. To use these switches you must run the RightFax931_HotFix3.exe file from a command line followed by the switches of your choosing. For example, to install the Hotfix with no user interaction and to automatically shutdown all local RightFax services, you would run the following command from the folder that contains the RightFax931_HotFix3.exe file (C:\RightFaxHotfix in this example).

C:\RightFaxHotfix\RightFax931_HotFix3.exe /quiet /shutdown

Setup switches available in Hotfix 3

/quiet  Runs setup silently with no GUI.

/repair Forces a reinstall over the same hotfix version.

/passive Run with no interactive GUI. Error or warning messages will be displayed.

/shutdown Shuts down services during a passive or quiet install.

/norestart Use this option if restarting services and processes during the install is undesirable.

/extract=”<folder>” Use this option to extract the Hotfix folders and files to a specific folder. A log file called ExtractingFiles_<date_time>.log, will also be created here.

/clientinstaller=“<clientInstallDir>” Applies the hotfix to a path containing the RightFax client installation source. See Applying Hotfix 3 to Client Computers for more information about this setup option.

Installing Hotfix 3

Follow the steps below to install Hotfix 3. These steps do not use any of the setup options listed above.

IMPORTANT: To install the hotfix in a RightFax environment that uses Windows (NT) Authentication for the RightFax database, you must login to the fax server with a Windows account that is a member of RightFax database db_owner or sysadmin roles. Verify this requirement with the SQL Administrator before continuing.
  1. If you have not already done so, back up the entire \RightFax directory structure, the fax board directory (usually the \RFBoard folder), and the SQL database for RightFax. To ensure that all necessary files are properly backed up, stop all RightFax services before beginning the backup process.

  2. Log on to the RightFax server as an Administrator.

  3. Double-click RightFax931_HotFix3.exe. The RightFax 9.3 Feature/Service Pack 1b Hotfix 3 Installer opens.

  4. Click the Start button to begin the RightFax Hotfix wizard.

  5. If you have backed up your RightFax installation, place a checkmark in the box next to the text that reads 'I have backed up my RightFax Installation'. Click Next to continue.

  6. All remote RightFax services must be shutdown. If your environment uses remote RightFax servers (e.g. – Remote Board Servers, remote Workservers, remote E-mail Gateways, remote IIS servers, and servers within a RightFax collective), you must manually shutdown all RightFax services associated with these servers. If you have shutdown all remote RightFax services, or do not use remote RightFax servers, place a checkmark in the box next to the text that reads 'All remote RightFax services have been manually shutdown'. Click Next to continue.

  7. The RightFax Hotfix wizard will scan your local RightFax server for RightFax services that are running and open applications. If RightFax services are running or if you have a RightFax application open, you must click the Shutdown button to stop all RightFax services and close RightFax applications. Click Next to begin the installation.

  8. Click Close to complete the installation.

  9. Repeat these steps on all remote RightFax servers. These will include:

  10. Remote Board Servers

  11. Remote WorkServers

  12. Remote E-mail Gateways

  13. Exchange servers that have the RightFax Connector for Exchange installed

  14. Remote IIS servers with RightFax web-based applications installed

  15. Servers within a RightFax collective

To Install Hotfix 3 on a RightFax 9.3  Cluster

  1. Stop all RightFax services on all remote RightFax servers.

  2. If you have not already done so, back up the entire \RightFax directory structure and the SQL database for RightFax.

  3. On the primary node, run Cluster Administrator and take all the RightFax resources off-line. However, do not take the RightFax file share or the entire RightFax group off-line.

  4. Double-click RightFax931_HotFix3.exe. The RightFax 9.3 Hotfix 3 Installer opens.

  5. Click the Start button to begin the RightFax Hotfix wizard.

  6. If you have backed up your RightFax installation, place a checkmark in the box next to the text that reads 'I have backed up my RightFax Installation'. Click Next to continue.

  7. Shutdown all RightFax services on Remote Board Servers,  and if necessary: Remote Workservers; Remote E-mail Gateways; Remote IIS servers; and servers within a RightFax collective. If you have shutdown all remote RightFax services, or do not use remote RightFax servers (all clusters use Remote Board Servers), place a checkmark in the box next to the text that reads 'All remote RightFax services have been manually shutdown'. Click Next to continue.

  8. Verify that the RightFax resources have been shutdown and that you are installing this update on the active node. At the Special Cluster Requirements screen, place checkmarks into the boxes confirming that you have shutdown the RightFax resources and are installing on the active node. Click Next to continue.

  9. The RightFax Hotfix wizard will scan your local RightFax server for running RightFax services (cluster resources) and open applications. All services should be shutdown using Cluster Administrator, and not the Hotfix wizard. If the Hotfix wizard displays running services, you must shutdown the RightFax services using Cluster Administrator. Failing to shutdown RightFax services with Cluster Administrator will result in a cluster fail-over. After shutting down the RightFax services, click the rescan button. The Hotfix wizard should now list no running services or open application. Click Next to begin the installation.

  10. Click Close to complete the installation.

  11. Using Cluster Administrator, move the RightFax share to the secondary node.

  12. Complete steps 4-9 on the secondary node,

  13. Bring the RightFax resources back on-line.

Applying Hotfix 3 to Client Computers

Hotfix 3 for client computers is an update to RightFax client applications. These clients include: FaxUtil; RightFax Fax Printer and Tray Icon (faxctrl); Soap Clients; and Enterprise Fax Manager. These clients may be updated by completing a local installation on each client workstation or by updating the client installation source files to this Hotfix version, followed by a global reinstall of the RightFax clients.

The instructions under the large-scale deployment section assume you have created a client installation source on a network file share. After updating the installation source you must then re-distribute the client software by using the built-in installation functionality of RightFax and third-party automated distribution software (such as Group Policy).

Small-scale Update

This section outlines the steps needed to update RightFax clients on a small-scale.

IMPORTANT: To apply this update to client computers, .NET Framework 1.1 or greater must be installed.
  1. Login to the client workstation as an Administrator

  2. Double-click the RightFax 9.3 Hotfix 3 installer (RightFax931_HotFix3.exe).

  3. Click the Start button to begin the RightFax Hotfix wizard.

  4. The RightFax Hotfix wizard will scan your RightFax client workstation for running RightFax applications. If you have a RightFax application open, you must click the Shutdown button to close all RightFax applications. Click Next to begin the installation.

  5. Click Close to complete the installation.

Large-scale Deployment

This section outlines the steps needed to update RightFax clients on a large-scale.

  1. Copy or download the RightFax 9.3 Hotfix 3 installer (RightFax931_HotFix3.exe) to the location that contains the 9.3 client installation source folder.

  2. Open command prompt and change to the directory that contains the Hotfix 3 installer.

  3. Type the following command and press Enter: RightFax931_HotFix3.exe /clientinstaller="<client folder>"  - where "<client folder>" represents the folder containing the client installation source files. Be sure to include quotes around the client installation source folder.
    For example, to update a RightFax client installation source folder that resides at C:\RightFax, the command would be:

            RightFax931_HotFix3.exe /clientinstaller="C:\RightFax"

  1. Open installation source folder and double-click the file Setup.ini

  2. Look for the entry ProductVersion=9.31.0000. Change this value to . Change this value to ProductVersion=9.31.0100.

  3. Look for the entry 'CmdLine='. After the equals '=' sign, enter the install parameters relevant to your environment. Below is an example of a 'CmdLine='. After the equals '=' sign, enter the install parameters relevant to your environment. Below is an example of a 'CmdLine=' entry for an environment that wishes to install the client package silently and include FaxUtil, the Outlook Advanced form, and the RightFax Fax Printer. A full list of install parameters can be found in the RightFax Installation Guide.

Example for existing 9.3 installations:

Below is an example of a 'CmdLine=' entry for an environment that wishes to install the client package silently and reinstall all currently installed client applications with Hotfix 3 applied.

CmdLine=/qn REINSTALL=ALL REINSTALLMODE=vomus ALLUSERS=1 REBOOT=REALLYSUPRESS /l*v "%TEMP%\RightFax Client Install.log"

Example for new client installations:

Below is an example of a 'CmdLine=' entry for an environment that wishes to install the client package silently and include FaxUtil, the Outlook Advanced form.

CmdLine qn SERIALNUM=<serialnum> INSTALL_FAXUTIL=TRUE INSTALL_FAXCTRL=TRUE INSTALL_OUTLOOK=TRUE INSTALLDIR=C:\Progra~1\RightFax\ ALLUSERS=1 RFSERVERNAME=<servername> REBOOT=REALLYSUPRESS /l*v "%TEMP%\RightFax Client Install.log"

  1. Once the install parameters are entered, save and close the Setup.ini file.

  2. If you are installing new fax clients, you may now redistribute the client software using automated distribution software.

  3. If you are upgrading existing clients, you must execute the Windows Installer using the setup options shown below. Executing the Windows installer can be done manually at a command prompt or by an automated process that calls the Windows installer. Regardless of your method, the setup options must be include the /fvomus switch followed by the path to the RightFax client installer file (RightFax Client Applications.msi).


    msiexec /fvomus \\share\RightFax Client Applications.msi

Configuring RightFax 9.3 for Midas C++ API

The Midas C++ API by Genii Software extends the functionality of Lotus script and assists in the conversion and rendering of Lotus generated forms. Steps to implement the Midas engine include purchasing and installing the Midas Rich Text C++ API and adding a new RightFax Lotus Notes e-mail gateway. This update resolves defect 56792.

An evaluation license of the Midas C++ API is also available at the Midas website. For more information visit: http://www.GeniiSoft.com/showcase.nsf/MidasCPPEvalRequest

Requirements

  • RightFax 9.3 Feature/Service Pack 1b with Hotfix 3 applied

  • Installed licensed version of the Midas Rich Text C++ API

Install Midas C++ API

These instructions assume you have purchased, licensed, and added the Midas Rich Text C++ API to the RightFax server. Before attempting the steps below, verify the presence of the files midisv.dll and midisv.lic in the \RightFax\Gateway directory. If these files are not found, you must contact Genii software to purchase the Midas Rich Text C++ API. More information can be found at the Midas website at http://www.geniisoftware.com/showcase.nsf/MidasAgree.

Follow the steps below to configure the RightFax Lotus Notes e-mail gateway for use with Midas C++ API.

  1. Log on to the RightFax server as an Administrator.

  2. Stop the RightFax E-mail Gateway module.

  3. Log on to the EFMSync database using a Lotus client.

  4. Open the gateway document and change the Notes Form Export Method to Notes Native Export. This option is found under Send Outbound Faxes section

  5. Save and close the gateway document.

  6. Restart the RightFax E-mail Gateway module.

Troubleshooting the Hotfix 3 Installation

The Hotfix 3 installation creates a log file that can be referenced for troubleshooting purposes. Look for the file RightFax93Hotfix3_date_time.log, located at the root of the RightFax installation folder.

Software Fixes in RightFax 9.3 Feature/Service Pack 1b Hotfix 3 

Captaris Tracking Number

Module

Problem

Solution

57358

Com API

Fax priority is ignored when sending faxes with the Com API.

Corrected. Fax priority functions as expected.

58976

Database Module

Faxes cannot be deleted when the RightFax database is set to use Turkish collation.

Corrected. Faxes may be deleted as expected.

58076

DocTransport Module

ANI routing fails to route faxes via fax user routing numbers.

Corrected. Routing number may be used as expected.

58371

DocTransport Module

CSID numbers greater than 20 characters can be entered into the DocTransport> Legacy BoardServer > Fax Board > fax ID field when only 20 characters are supported by the fax board.

Corrected. Problem no longer occurs.

58818

DocTransport Module

TR1034 fax boards and CallXpress are incompatible.

Corrected. TR1034 fax boards and CallXpress are now compatible.

58838

DocTransport Module

Enabling Call Grouping causes outbound fax history to indicate that no pages were sent.

Corrected. Fax history reports outbound pages as expected.

56800

FaxDump

FaxDump will not report on deleted users.

This behavior is by design. Use SQL tools to acquire this information.

58096

FaxDump

FaxDump returns “EnumAllFaxes failed with error 2” when run during certain times of day.

Corrected. FaxDump runs as expected.

53780

Integration

Using Maptext.exe to create overlay templates fails and generates an error message.

Corrected. Problem no longer occurs.

57850

Integration

Sending batch faxes using the Integration Module randomly results in conversion errors.

Corrected. Faxes convert as expected.

58291

Integration

Adding TCP printer ports on RightFax Business Server with Business Integration and Business Integration+ generates a licensing error.

Corrected. Problem no longer occurs.

49563

Notes Gateway

Lotus forms fail fax conversion.

This problem is corrected with the installation of Midas LSX.

56792

Notes Gateway

Graphics within outbound faxes are not converted if the EFMSync database is configured to use the export method of: Notes Native Export.

This problem is corrected with the installation of Midas LSX.

58705

Notes Gateway

Notification of successfully sent faxes do not occur when sending faxes via a Lotus Notes client while using a RightFax no-mail integration.

To receive notification of successfully sent faxes you must enable the Return Receipt option located in the Delivery Options menu of your Lotus Notes client.

58515/

59010

 

Server Module

Changes to daylight savings time in North American (excluding Mexico) cause inaccurate inbound time stamps and significant outbound fax delays.

Issues associated with DST and Windows Server 2003 operating systems are resolved with this update.

57080

Web Access

Documentation for Web Access does not outline steps for adding additional languages for use in the Web Access interface.

Corrected. Answer ID 4561 provides instruction. Search for this ID at the Captaris online knowledgebase.

58546

Web Access

Faxes with an ampersand (&) in the coversheet notes field fail conversion.

Corrected. Faxes convert as expected.

58245

WorkServer

Fax conversions cannot be controlled by via the Control.pcl file.

Follow the steps below to resolve this issue:

1. Run Regedit and open  HKLM\Software\Rightfax\WorkServer#, where # is the WorkServer # (e.g., WorkServer 1) configured for PCL conversions.

2. Create the a REG_SZ entry called ControlPCLFileName.

3. Edit the above entry to contain the file name used to control PCL text conversion. This file must be present in the \RightFax\Shared Files\PCL folder. Repeat for each WorkServer configured for PCL conversion.

58369

WorkServer Module

Text files converted by RightFax 9.3 Hotfix 1 are lighter than those converted by  RightFax 8.7 SP3.

Follow the steps below to resolve this issue:

1. Run Regedit and open HKLM\Software\Rightfax\WorkServer#

2. Create the following DWORD entries and corresponding decimal values for each WorkServer configured for fax conversion:

PCL6_NormalMode_RParam  - Value of 100 decimal PCL6_FineMode_RParam  - Value 200 decimal PCL6_TextAlphaBitsParam  - Value 2 decimal

Software Fixes in RightFax 9.3 Feature/Service Pack 1b Hotfix 2 

Captaris Tracking Number

Module

Problem

Solution

58244

Alerting and Monitoring

Alerts created by RightFax administrators cannot be view by fellow RightFax administrators.

This behavior is by design

57477

BoardServer Module

Adding or removing Brooktrout TR-114 faxboards will reset the BoardServer module service account to 'local system'.

Corrected. Adding or removing Brooktrout TR-114 faxboards will not reset the BoardServer module service account.

55990

Com API

Fax priority is ignored when sending faxes with the Com API.

Corrected. Fax priority functions as expected.

57677/
58407

Database Module

Users that require approval prior to sending faxes may forward a fax without approval.

Corrected. All faxes requiring approval must be approved prior to sending.

58148

DocTransport Module

Dots within a fax number are not purged from the dialing string.

Corrected. All dots are purged from the dialing string.

58315

DocTransport Module

Refreshing the DocTransport view causes the channel capability setting of Brooktrout 1034 analogue fax boards to revert to Dial.

Corrected. Problem no longer occurs.

58567

DocTransport Module

SR140 channels remain offline after a reboot of the fax server.

Corrected. Problem no longer occurs.

57583

E-transport Module

The E-transport Module is programmed to process data from an incorrect folder.

Corrected. E-transport now process data from the correct folder.

58060

Exchange Gateway

Error logs written to the \RFaxgate\IN\ERR folder contain no information.

Corrected. Files now contain information about the failed fax.

58009

FaxUtil

Disabling the option for 'Certified Delivery' in Enterprise Fax Manager does not remove the ability to send Certified faxes from FaxUtil.

Corrected.  Certified Delivery option functions as expected.

58243

FaxUtil

Pasting an e-mail address into the FaxUtil> Fax Information > e-mail address field allows a maximum of 31 characters, however if typed, an additional 31 characters can be added.

Corrected. A maximum of 62 characters can be entered into the FaxUtil> Fax Information > e-mail address field.

57874

Integration

Addresses a memory performance issue and conversion issues.

Corrected. Problem no longer occurs.

57695

Integration

Business Integration Servers are not licensed for XML integration.

Corrected. Business Integration Servers are licensed for XML.

58123

Integration

The MQGet fails to process data in excess of 1MB.

Corrected. Problem no longer occurs.

57600

ODBC Phonebooks

Importing an ODBC phonebook that uses a Microsoft Excel data source will append the characters .0 to the end of each fax number imported into RightFax.

Corrected. Excel based ODBC phonebooks import as expected.

57331

Outlook Forms

The 'Create Internet Mail Fax Addresses' option fails to send faxes using IETF SMTP fax addressing.

Corrected. The 'Create Internet Mail Fax Addresses' option now functions as expected.

57565

Server Module

Fax notifications of successfully sent faxes are not generated when auto delete is enabled.

Notifications cannot be generated when auto delete is enabled.

57699

Server Module

The <UNIQUEID> embedded code does not correctly populate the FaxUtil > Unique ID column.

Corrected.  The <UNIQUEID> embedded code functions as expected.

57991

Server Module

Addresses a memory performance issue associated with high volume inbound faxing and RTI stamping.

Corrected. Problem no longer occurs.

58011

Server Module

Files associated with the aged e-mails are not auto-purged when specified.
 

Corrected. Aged e-mails are purged as expected.

58031

Server Module

Forwarding received faxes bypasses billing code requirements

Corrected. Requirements no longer bypassed

58155

SMTP Gateway

The SMTP gateway fails to send faxes with 192 characters or more in the subject line.

Corrected. Faxes with 192 characters or more in the subject line can now be sent using the SMTP Gateway.

57663

Web Access

Faxes cannot be routed to multiple users.

Corrected. Faxes can now be routed to multiple users via Web Access.

57665

Web Access

Delegate users can print faxes from the inbox of other RightFax users.

Corrected. Delegate users can only print from the inbox of other RightFax users if the permission of 'Can Print Faxes' is enabled.

57863

Web Access

Faxes sent to an e-mail address generate an error.

Corrected. Faxes can now be sent to an e-mail address.

58094

Web Access

Users that are set to "View First Page Only" can view all pages of a fax.

Corrected. The "View First Page Only" permission functions as expected.

58405

Web Access

Information specified within the user 'Cover Sheet Information' option is not reflected on cover sheets.

Corrected. The coversheet options are populated as expected.

58406

Web Access

Sending faxes to a distribution list using another users published phonebook generates an error resulting in failed fax submission.

Corrected. problem no longer occurs.

57548

WorkServer

Disabling short file names on a Windows Server 2003 computer causes all outbound faxes to fail conversion.

Corrected. Faxes now send as expected.

57917

WorkServer

Documents printed to Windows GDI printers fail with error 0x180000 if resolution is not set to 'High'.

Corrected. Problem no longer occurs.

58070

WorkServer

Certain PCL cover sheets pass conversion in RightFax 9.0, but do not with RightFax 9.3.

Corrected. PCL cover sheets convert as expected.

Software Fixes in RightFax 9.3 Feature/Service Pack 1b Hotfix 1 

Captaris Tracking Number

Module

Problem

Solution

56370

Captaris Conversion Engine

MHT files sent as faxes contain HTML header information along the top of each fax page.

Corrected. Header information is no longer displayed.

57498

Captaris Conversion Engine

HTM files sent as faxes do not contain HTML header and footer information.

The option to include headers and footer is now an option in the Captaris Conversion Engine Control Panel.

56306

Captaris Sync Module

Objects contained within Active Directory organizational units nested within the Users container are not synchronized into RightFax.

Objects contained within Active Directory organizational units nested within the Users container can now be synchronized into RightFax.

55990

Com API

Fax priority is ignored when sending faxes with the Com API.

Corrected. Fax priority functions as expected.

56255

Database Module

The DT Dialing Rules database table does not use the default database collation.

Corrected. The DT Dialing Rules database table now uses the default database collation.

56711

Database Module

DBUpgrader fails to import all phonebooks groups.

Corrected. All phonebook groups are imported as expected.

57063

Database Module

Deleted fax records are purged during database maintenance.

Corrected. Deleted fax records are purged only when specified.

53655

DBPurge

DBPurge does not clear work requests that have been generated by Lotus CC Mail users.

Corrected. Lotus CC Mail work requests can now be purged using DBPurge.

57573

Documentation

On p. 241 of the 9.3 Hotfix 3 Administrator's Guide erroneously states that the registry key HKLM\Software\RightFax\FaxServer\DeleteImagesOnPurge should be changed when it should be created. The value should be set to 0 and not false.

Corrected. Reference was removed from the Administrator's Guide.

57058

Exchange Gateway

Multiple Exchange E-mail Gateways that are configured to process messages from the same \RFGate\Out folder will fail to process messages should one of the gateways stop.

Corrected. Problem no longer occurs.

48622

FaxUtil

Adding a phonebook contact from another user's shared phonebook results in an error and the contact is not added.

Corrected. Entries from a shared phonebook can be added as expected.

56223

FaxUtil

Viewing and rotating a fax in FaxUtil allows users to annotate and save a fax even if they do not have permission to annotate faxes.

Users without the permission to annotate faxes cannot alter and save faxes using the FaxUtil annotation features.

56741

FaxUtil

Recipient contact information cannot be populated if using an Exchange MAPI phonebook.

Corrected. Recipient contact information can be populated using an Exchange MAPI phonebook.

57014

FaxUtil

Viewing a received SMS message in FaxUtil does not display the senders phone number.

The phone number of an received SMS message can now be viewed in the FaxUtil > Fax Number/E-mail/ID column.

56042

GroupWise Gateway

Faxes sent via the GroupWise gateway that contain body text or attachments will fail conversion.

Corrected. Faxes convert as expected.

52074

Integration

If an MQ server connection is lost, the MQGet command is unable to restore the connection without being restarted.

Corrected. Problem no longer occurs.

52075

Integration

The MQGet command does not recognize a "Quiesce" request from MQ Servers during maintenance cycle.

Corrected. Problem no longer occurs.

56610

Integration

Cover sheet text will not word wrap on faxes sent through the Integration module.

Corrected. Coversheet text will word wrap up to 70 characters.

57353

Integration

PCX files are not converted properly when sent via the Integration Module.

Corrected. PCX files are converted as expected.

56979

Notes Gateway

Faxes sent using manual fax addressing causes user outbound fax settings to be ignored.

Corrected. Faxes send as expected.

56899

Outlook Forms

Opening a fax using the Outlook Advanced form while in a Citrix or Remote Desktop session results in a 'drawing error'.

Corrected. Faxes viewed with the Advanced Form can be viewed as expected.

51075

PDF Module

Line items within certain PDF attachments are not readable.

Improvements to the PDF conversion process have been implemented.

57220

RightFax Fax Printer

Local system administrator accounts are unable to install the RightFax Fax Printer.

Corrected. Local system administrator accounts can install the RightFax Fax Printer.

56286

Server Module

The <WHO> embedded code is not processed as PCL code if not formatted as plain text.

Corrected.  The <WHO> embedded code is interpreted if not formatted as plain text.

56816

Server Module

Installing RightFax on a Windows server configured for Turkish Regional Settings causes outbound faxing to fail.

Corrected. Faxes send as expected.

56775/

52954

Server Module

Users configured to receive the SMTP or Exchange notification of 'a fax has not been viewed or printed', also receive the notifications, 'a new fax has arrived from <user>' and 'a fax has not been viewed or printed.'
 

Corrected. Problem no longer occurs.

57482

Server Module

Auto forwarding received faxes bypasses billing code requirements

Corrected. Requirements no longer bypassed

57571

Server Module

Faxes received via a Remote Board Server have a time stamp that is one hour ahead of the parent RightFax server.

Corrected. Faxes received via a Remote Board Server possess the correct time stamp.

56796

SMTP Gateway

HTML embedded codes are not recognized if faxing via Outlook Express 6 and through the SMTP gateway.

Corrected. HTML embedded codes are now correctly interpreted. However, the mail message format must be set to HTML.

57594

SMTP Gateway

Should a loss in connectivity to the SMTP server configured to integrate with RightFax occur, SMTP fax notifications are not queued and thus are lost.

Corrected. SMTP notifications are queued at the RightFax server and will be resent upon reconnecting to the SMTP server.

56740

Web Access

Sending a fax from Web Access while logged in as a delegate is incorrectly sent from the account that has granted delegate access and not the account that is logged in as a delegate.

Corrected. Faxes are now sent from the account that is logged in as a delegate.

56916

WebEFM

Users listed in WebEFM are not sorted in alphabetical order.

Corrected. Users are now sorted alphabetically.

52647

WorkServer

Converted 7x3 inch TIF files are condensed to thumbnail size.

Corrected. 7x3 inch .TIF files are converted as expected.

55906/ 57097

WorkServer

Using the NativeDocControl of 'PDF,2' fails to correctly convert landscape format faxes.

Corrected. PDF files in landscape format are converted as expected.

56789

WorkServer

Visio 2003 documents are not formatted correctly when converted to fax.

Corrected. Visio 2003 documents are formatted as expected.

56976

WorkServer

Only the first 8 characters of a billing code can be viewed if the billing code text is formatted with Hebrew characters.

Corrected. All characters can be viewed.

57286

WorkServer

Sending multi-page .TIF files that contain both legal and letter sized pages causing a conversion issue where letter sized pages are blank.

Corrected. All pages convert as expected.

57301

WorkServer

Sending faxes that contain the <BREAK> embedded code and attachments causes fax conversion to fail.

Corrected. Faxes convert as expected.

57590

WorkServer

Text contained within plain text attachments is converted to low resolution.

Corrected. Text contained within plain text attachments is converted as expected.

 

Для добавления комментария необходима регистрация