The RightFax 9.4 release notes describes the changes in the product since RightFax 9.3
It also provides late-breaking or other information that
supplements the user documentation that is included on the DVD with the
RightFax 9.4 product suite.
1. New Features and Functionality Changes
The following is an alphabetical list of the new features and functionality that are introduced in RightFax 9.4.
· RightFax client applications supported on 64-bit operating systems. The following RightFax 32-bit client applications are supported on the x64 editions of Windows XP and Windows Vista:
· FaxUtil
· RightFax fax printer (i.e., print-to-fax)
· Outlook integration
· Enterprise Fax Manager
· SOAP fax printer (i.e., Web-based print-to-fax)
· AutoReply
· Active Directory 2008 support. User synchronization from Microsoft Active Directory 2008 is available with the Captaris Sync Module. For more information about the Captaris Sync Module, see the RightFax 9.4 Administrator's Guide located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· Administrative Utilities Installation. RightFax 9.4 Setup provides the option to install the RightFax Administrative Utilities. This replaces the previous Admin Utils Setup, which was a separate file available only via the Captaris Web site. For more information about the Administrative Utilities, see the RightFax 9.4 Administrative Utilities Guide located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· Auditing for user and group maintenance. RightFax 9.4 includes a new reporting tool called Enterprise Fax Reporter. Several pre-configured reports are provided with Enterprise Fax Reporter, including a new advanced auditing report which provides the following information:
· User and group creation date/time
· User and group creator (User ID and User Name)
· User and group modification date/time
· Who modified a user or group object (User ID and User Name)
· User and group deletion date/time
· Who deleted a user or group object (User ID and User Name)
· Client fail-over in Shared Services environment. RightFax servers joined in a RightFax Shared Services system can be configured to allow FaxUtil client fail-over. When enabled, FaxUtil clients will automatically fail-over to another server within the system in the event of a connectivity failure or interruption. To enable this feature, click the option to Enable Shared Services failover in the RightFax Server Module of each RightFax server joined to the server collective. For more information about the RightFax Server Module, see the RightFax 9.4 Administrator's Guide located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· Drag-and-drop to create a fax. Users can drag and drop files from Windows Explorer or from the desktop to create a new fax or to attach a file to a fax in FaxUtil or from the print-to-fax client application. For more information, see the FaxUtil online help (launched from the FaxUtil Help menu command).
· Documentation changes. Revisions to all RightFax guides and quick reference cards are included with RightFax 9.4. New documentation or other changes to documentation are:
· A new database schema document providing detailed information about database tables, views, procedures, and data types is included with RightFax 9.4. Look for this PDF document (RightFax 9.4 Database Schema.PDF) in the in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· Supported fax boards document. Available online at http://www.captaris.com/support/documentation/rightfax/supportedboards.html.
· New RightFax 9.4 Administrative Utilities Guide (replaces the Web readme file introduced in RightFax 9.3).
· New online help for Captaris Sync Modules, Captaris Conversion Engine, and the RightFax Remoting service. To access the new Help, click the question mark (?) in the upper right-hand corner of each service configuration dialog box.
· Push-Proxy Gateway documentation is no longer a separate guide and now is included as a chapter in the RightFax 9.4 Administrator's Guide, Chapter 16.
· Email gateway notifications may include a copy of outbound message. The Microsoft Exchange, GroupWise, Lotus Notes, and SMTP gateways include an option to include the fax with notifications. When enabled, this option will send a copy of either the first page or all pages of a sent fax with an outbound fax notification. This option is particularly useful in confirming the success or quality of an outbound message.
· Enhanced fax over IP support. Enhancements to existing fax over IP (FoIP) functionality and support are listed below. In addition to these new FoIP features, RightFax 9.4 also includes a new configuration that allows multi-router environments to enable FoIP fail-over via RightFax dialing rules. For more information about the FoIP fail-over, see the RightFax 9.4 Administrator's Guide, Chapter 5, located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· T.38 FoIP/V.34 endpoint
· T.38 FoIP/V.34 gateway
· Enterprise Fax Manager. RightFax 9.4 Enterprise Fax Manager fully supports management and configuration of a RightFax 9.4 server, however it gives limited support for RightFax 9.3 and RightFax 9.0. For example, a RightFax 9.4 Enterprise Fax Manager cannot configure RightFax services on RightFax 9.0 and RightFax 9.3 servers and cannot be used to license a RightFax 9.0 or RightFax 9.3 server. Captaris recommends using RightFax 9.4 Enterprise Fax Manager to configure RightFax 9.4 servers only.
·
IP v6 support. Support for the
IPv6-literal namespace format is a new and inherent function of RightFax 9.4.
To access resources on an IP v6 network, you must configure RightFax to use the
IP v6 host name to resolve an IP v6 address. For more information, see
Microsoft knowledge base article 944007 at http://support.microsoft.com/kb/944007.
NOTE: IPv6 support of any kind is
not available with RightFax Web Access.
· Improved OCR performance. A new, robust OCR engine by RecoStar is introduced in RightFax 9.4. The RecoStar OCR settings are configured via the Captaris Conversion Engine control panel. At least one WorkServer module must be configured for OCR processing, however no additional WorkServer configuration is required. This replaces the former configuration which was performed entirely within a WorkServer configuration. For more information about the OCR conversion, see the RightFax 9.4 Administrator's Guide, Chapter 22, located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server or the online help that ships with the Captaris Conversion Engine.
· Service account configuration. Selecting and managing RightFax service accounts in RightFax 9.4 is done via a new, centralized tool called the RightFax Service Account Editor. The editor is launched when a user clicks the Select Service Account button within a configurable RightFax service. Services affected by this change include:
· Captaris Conversion Engine
· DocTransport module
· Email Gateway module
· Remoting service
· Server module
· WorkServer module
· Simplified installation. The RightFax 9.4 Setup program provides a simplified and improved workflow and the following new features:
· A single installation DVD replaces the three CDs of previous releases. The RightFax Product Suite DVD includes most of the RightFax prerequisite software, all server and client product software, fax board drivers, and the Administrative Utilities software. Any or all of these can be installed by running Setup.exe on the root of the RightFax Product Suite DVD.
· Option to check online for product and Setup updates.
· Setup includes a new feature set page which provides brief descriptions of all possible Setup options.
· RightFax port reservations can be made during Setup. This previously was unavailable with Setup and required manual, post-install configuration.
· Windows authentication or SQL authentication may be defined during Setup. Previous Setup architecture required SQL authentication.
· Local RightFax service accounts are defined via a single Setup step versus the three-step process of past versions, which required WorkServer, e-mail gateway, and e-transport account information.
· Integrated product activation.
· RightFax Web application Setup may be done manually or via an automated Setup process, which creates IIS virtual directories and defines directory security and permissions. For more information about Web application setup, see the RightFax 9.4 Installation Guide, Chapter 5, located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· Advanced database selection page provides four options for installing or integrating the RightFax database, including the option to add RightFax schema and design elements to an empty, pre-configured database.
· Software fixes. All previous fixes from RightFax 9.3 are included with RightFax 9.4.
· SQL compatible reporting tool. A new application in the suite of RightFax Administrative Utilities called Enterprise Fax Reporter replaces the legacy Fax Reporter program. This new tool provides improved SQL query performance, a new interface, and new built-in reports. For more information, see the RightFax 9.4 Administrative Utilities Guide, Chapter 3, located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· SQL service account. Improvements to the RightFax SQL connection string editor provide a simple and convenient tool for modifying the SQL connection string and changing the database authentication method (i.e., Windows or SQL authentication) for all RightFax services and applications.
·
Unassisted online product licensing.
The Captaris Product Licensing Utility replaces
the RightFax legacy “bump code” architecture and introduces an unassisted
online licensing process. The Product Licensing Utility is fully-integrated
into the RightFax Setup program and allows installers to activate RightFax
during Setup. Adding, upgrading, or changing your feature set requires
only your product licensing information and an active Internet connection. The Product
Licensing Utility is accessible from the RightFax Server Module configuration and
from the Windows programs Start menu. For more information about licensing RightFax
products, see the RightFax 9.4 Installation Guide, Chapter 9,
located in the \RightFax\Docs folder on the RightFax Product Suite DVD and on
the RightFax server.
NOTE: Previous versions of
RightFax cannot use the Product Licensing Utility to license RightFax or its
modules.
· VMware ESX server support. The RightFax 9.4 server supports VMware ESX server 3.0.1 or later. VMware Workstation and all other virtualization software is not supported. In addition to the server requirements outlined in the RightFax 9.4 Installation Guide, a virtual RightFax server must conform to the following:
· Virtual RightFax servers must be installed on ESX platforms that meet the minimum requirements as documented by VMware. Captaris recommends a virtual machine dedicated to each RightFax server.
· No virtual RightFax server may contain fax board hardware. Sending and receiving fax documents requires a boardless solution (such as FoIP) or dialing rules to route faxes to and from a physical server that contains one or more fax boards. For more information about creating dialing rules, see the RightFax 9.4 Administrator’s Guide.
· RightFax Web Access functionality improvements. A revised RightFax Web Access log on page improves automatic language selection by using the Internet Explorer requested culture setting. If the requested culture setting is not configured or otherwise not available, RightFax Web Access will localize its content based the parent culture setting. Other changes include the new inbox search (i.e., sort) filters of:
· Start date/time
· End date/time
· ANI
· CSID
· Windows Server 2008 x64 support. The RightFax 9.4 Connector for Exchange 2007 supports the following 64-bit versions of Microsoft Windows Server 2008:
· Windows Server 2008 Standard x64
· Windows Server 2008 Enterprise x64
Updates have occurred since the RightFax product suite DVD was manufactured. Note the following errata and updates.
· Updates to the RightFax software may be available as a service release. To obtain updates, go to http://www.captaris.com/support/downloads/rightfax/94/index.html.
· The RightFax 9.4 Installation Guide has been updated to include instructions for installing the RightFax client applications from a command line. See Chapter 6, “Installing RightFax Client Applications.” To obtain the updated guide, go to http://www.captaris.com/support/documentation/rightfax/index.html.
· RightFax 9.0 Feature Pack 2 or later or RightFax 9.3 Feature Pack 2 Service Release 5 or later is required to upgrade to RightFax 9.4 server and client applications. Earlier versions cannot be upgraded.
Following is a list of features and functionality that are removed in RightFax 9.4.
· Additional SMS Transactions. Licensing and support for additional SMS transactions ends with the release of RightFax 9.4.
· Eicon Diva SoftIP. Eicon Diva SoftIP is not supported in RightFax 9.4.
· Exchange 2000. Support for the RightFax Connector for Exchange 2000 ends with the release of RightFax 9.4.
· Fax board support. Certain legacy fax boards are not supported by RightFax 9.4. For a complete list of fax boards supported by RightFax 9.4, see the supported fax boards document at http://www.captaris.com/support/documentation/rightfax/supportedboards.html.
· Interaction client integration. The RightFax client integration with Interaction software reaches end-of-life in RightFax 9.4.
· RightFax Workflow Wizard. The RightFax Workflow Wizard reaches end-of-life in RightFax 9.4.
· SecureDocs Configuration. The SecureDocs configuration tool has been replaced by a built-in HTML-based configuration. For more information, see the RightFax 9.4 SecureDocs Guide in the \RightFax\Docs folder on the RightFax Product Suite DVD and on the RightFax server.
· Service Release Deployment. Typically, the first step in a corporate deployment of RightFax client applications is to create a network installation point. In previous versions, RightFax service releases and feature packs could be installed at the network installation point and then distributed by reinstalling on client computers. Unlike previous versions, you cannot deploy updated client installation source files on computers that have RightFax 9.4 client applications already installed.
· Single Click Entry. Previous installations of Single Click Entry are not supported in RightFax 9.4.
· Windows 2000. Support for all versions of Windows 2000 server and client operating systems ends with the release of RightFax 9.4.
Issues in previous RightFax releases that were reported by customers are fixed and included in this release. RightFax 9.4 includes all the fixes from previous service releases and some issues fixed since the last available service release.
RightFax 9.4 includes the following customer issues that have been fixed since the last available service release, RightFax 9.4 Feature Pack 2 Service Release 6.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
47048 |
RightFax Web Access |
German translations were not
available in the DocumentRouteForward dialog box. |
Corrected. Translations are
now available. |
|
48517 |
RightFax Web Access |
After uninstalling RightFax
Web Access, files that are shared with Captaris
Workflow are removed. |
Corrected. Files that are
shared with Captaris Workflow are no longer
removed. |
|
56163 |
DocTransport |
Dialing rules do not
correctly route faxes from a remote BoardServer
back to the RightFax server. |
Corrected. Fax routing is
correctly routing faxes. |
|
57567 |
Exchange Gateway |
The Exchange Gateway cannot
be installed unless the administrative group includes a servers
container. |
Corrected. The Exchange Gateway
can be installed when the administrative group does not include a servers container. |
|
57912 |
Fax Server |
If a fax with
an attachment is sent through an SMTP e-mail gateway and fails conversion, then
the fax recipient's name and fax number do not appear in FaxUtil. |
Corrected. If a fax with an attachment is sent through
an SMTP e-mail gateway and fails conversion, then the fax recipient's name
and fax number appear in FaxUtil |
|
58898 |
Documentation |
The IBM WebSphere
MQ section in the RightFax Integration Module
Guide is outdated. |
Corrected. The chapter describing setup and
configuration of IBM WebSphere MQ was removed,
because IBM now provides such documentation for its product. |
|
59177 |
DocTransport |
Cannot install the Push
Proxy Gateway on a remote Boardserver. |
Corrected. The Push Proxy
Gateway can now be installed on a remote Boardserver. |
|
59894 |
Install |
During an upgrade, the
install program does not update the path to the RFISOConv.exe in the Windows registry,
thus subsequent updates are applied in an incorrect path. |
Corrected. The install
program updates files in the correct path. |
|
59937 |
Documentation |
The Push Proxy Gateway Guide incorrectly states that the feature is
automatically installed during installation of the RightFax server
installation. |
Corrected. The Push Proxy
Gateway must be installed via the Custom install method. |
|
60690 |
Enterprise Fax Manager |
Help > About Enterprise
Fax Manager displays incorrect information about the operating system. |
Corrected. Information about
the operating system is updated. |
|
61216 |
Exchange Connector |
All faxes sent from Outlook
2003 via the RightFax connector for Exchange 2007 fail if Exchange Cached
Mode is enabled. |
Answer ID 6009 in the Captaris product support knowledgebase provides more information about this Microsoft issue. |
|
61898 |
Install |
During installation, using a
SQL account with the role db_owner fails to create
the RightFax database. |
Corrected. Db_owner SQL Server role is sufficient to create the
RightFax database. |
|
61909 |
DocTransport |
Installing a remote DocTransport server disables the fax board in the main RightFax
server. |
Corrected. When
installing a remote DocTransport, the DocTransport on the main RightFax server will continue to
send faxes. |
|
62491 |
SOAP client |
After installing RightFax
9.3 Feature Pack 2 SOAP server and client application and selecting Quick Fax
Broadcast, the SOAP client reports "Error 10009," and faxes cannot
be sent. |
Corrected. After installing
RightFax 9.4, faxes can be sent with Quick Fax Broadcast via the SOAP client
and server application. |
|
62588 |
Fax Reporter |
Enterprise Fax Reporter does
not report correctly in a RightFax Shared Services system. |
Corrected. Enterprise Fax
Reporter reports data correctly in a RightFax Shared Services system. |
|
62621 |
Brooktrout Fax Boards |
After installing RightFax
9.3 FP2 SR1 on a RightFax server with Dialogic Brooktrout
TR1034 fax boards, boards that have been feature locked to v.17 cease
functioning. |
Corrected. After installing
RightFax 9.4 on a RightFax server with Dialogic Brooktrout
TR1034 fax boards, boards that have been feature locked to v.17 do not cease
functioning. |
|
62637 |
DocTransport |
When SQL connectivity is
lost and fax channels set to both send and receive, the RightFax server is unable
to receive faxes on those channels. |
Corrected. If the SQL
connection is down and channels are set to both send and receive, the
RightFax server will receive faxes on those channels. |
|
63279 |
Install |
Install program doesn't
check for the correct RightFax database version. |
Corrected. The install
program checks for the correct RightFax database version. |
|
64560 |
Integration Module |
FCL that works in RightFax
9.3 no longer works in RightFax 9.3 Feature Pack 2 Service Release 4. |
Corrected. The FCL is
functional. |
|
64739 |
Documentation |
The Integration Module Guide includes errors in its discussion of the
LOOKUP FCL code. |
Corrected. Errors in the
documentation are fixed. |
|
65622 |
SAP |
After applying RightFax 9.3
Feature Pack 2 Service Release 5, authentication fails for notifications to
SAP. |
Corrected. Notifications
back to SAP systems do not fail. |
|
66334 |
DocTransport |
When Human Answered Fax is
enabled and dialing rules are scheduling faxes to a remote DocTransport module that is stopped, the remote DocTransport will terminate unexpectedly. |
Corrected. The remote DocTransport module will not terminate unexpectedly when Human
Answered Fax is enabled and dialing rules are scheduling faxes to a remote DocTransport module that is stopped. |
|
66589 |
Exchange Gateway |
Adding the
ExchangeMsgs_0 REG_SZ ~1< text> Windows registry key to the gateway,
the system is unable to locate the Exchange
mail files directory. |
Corrected. The system is able to locate the Exchange mail files directory. |
RightFax 9.4 includes all of the fixes from RightFax 9.4 Feature/Service Pack 2 Service Release 6.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
59473 |
Admin Utilities |
Fax Reporter does not
provide reporting data for local, client based print jobs. |
Corrected. Local print job
report data now exists. |
|
59452 |
Captaris Sync |
User accounts that are
disabled and deleted from Active Directory are not deleted from RightFax
during synchronization. |
Corrected. Users are deleted
as expected. |
|
62444 |
Captaris Sync |
Active Directory user
account names that begin with the special characters are imported into
RightFax without the number sign (e.g., #User imports as User). |
Corrected. Users and user
names are imported as expected. |
|
64771 |
COM API |
COM API calls do not return
full phonebook entry data - only published entries. |
Corrected. Full data is
returned. |
|
59901 |
Database Module |
Information Incomplete fax notifications are generated after running database
maintenance. |
Corrected. If the user
option of "remains incomplete" is not checked, Information
Incomplete fax notifications are generated immediately following initial
send attempt and do not reoccur. |
|
59557 |
DocTransport |
Fax channels that are set to
Answer attempt to send, thus causing the timed ability option to fail. |
Corrected. Channels set to
Answer do not attempt to send. |
|
59697 |
DocTransport |
Fax channels cannot be set
to Dial. |
Corrected. Problem no longer
occurs. |
|
62502 |
DocTransport |
Faxes forwarded to an
account with InterConnect enabled, contain
duplicate fax history. |
Corrected. Problem no longer
occurs. |
|
64125 |
DocTransport |
IPK files created by
outbound SMS messages are not purged from the \Doctransport
folder. |
Corrected. IPK files are
purged as expected. |
|
64126 |
DocTransport |
Outbound SMS messages that
have failed due to message size requirements are retried per the global retry
settings in the Server Module. |
Corrected. Outbound SMS messages
that have failed due to message size requirements are not retried. |
|
64584 |
DocTransport |
In an environment with
Remote Board Servers and weighted dialing rules, some dialing rules may be
incorrectly disabled. |
Corrected. Problem no longer
occurs |
|
63341 |
E-mail Gateways |
SMS messages can be sent by
users without the permission of "Can Send
SMS Messages". |
Corrected. SMS messages are
blocked as expected. |
|
64323 |
Enterprise Fax Manager |
Duplicate delegate entries
are created when using the drag-and-drop functionality of Enterprise Fax
Manager to create new users. This issue occurs only if the option to Append
Delegates Only is selected. |
Corrected. Duplicates are
not created. |
|
64484 |
Exchange Gateway |
Faxes sent via the Outlook
form in an multiple Exchange Gateway environment
will contain only a coversheet, if the fax is processed by a secondary
Exchange gateway. |
Corrected. Faxes send as
expected. |
|
61493 |
FaxUtil |
Phonebook
ID's containing apostrophe's cannot be added to phonebook groups. |
Corrected. Phonebook ID's containing apostrophe's, can be added to
phonebook groups. |
|
61793/ |
FaxUtil |
The Reset to Defaults
option (under List > View), does not restore FaxUtil
columns to their default setting. |
Corrected. Columns are
restored as expected. |
|
62546 |
FaxUtil |
A delegate user who prints a fax from another user mailbox, is not
recorded in the fax history as the user responsible for printing the fax. |
Corrected. Print jobs
initiated by delegate users are recorded as expected. |
|
64277 |
FaxUtil |
Addressing a fax to a MAPI
phonebook contact does not populate e-mail addressing information. |
Corrected. Addressing
information is populated as expected. |
|
64724 |
FaxUtil |
Renaming an existing
phonebook entry to another ID that is already in use will generate a
duplicate ID warning, but deletes the existing ID. |
Corrected. Problem no longer
occurs. |
|
64935 |
FaxUtil |
Importing a phonebook that
contains duplicate entries results in an error. |
Corrected. Problem no longer
occurs. |
|
65370 |
FaxUtil |
Faxes cannot be viewed via
terminal services if the fax viewer is configured to gray scale, 4 or 16
shades. |
Corrected. Faxes are viewed
as expected. |
|
63999 |
Integration |
Notifications derived from an notification channel show a discrepancy between the
time a fax was sent and when it was received. |
Corrected. Sent and received
times are now consistent. |
|
64350 |
Integration |
Certain characters may cause
notify.exe to crash. |
Corrected. Notify.exe no
longer crashes. |
|
64463 |
Integration |
Separate documents are not
created when more than one e-mail address is specified by separate {{fax}}
commands. |
Corrected. New documents are
created as expected. |
|
64854 |
Integration |
Using backslash (\) or
double-quotes (") in the {{Subject}} FCL code causes mimesend
to fail with errors. |
Corrected. Mimesend jobs send as expected. |
|
64539 |
Notes Gateway |
Before the Auto Mail
Connections Document agent is run, the User_NotesID
field is not populated with the Notes (user) name. |
Corrected in the Lotus
Notes update. |
|
64410 |
Outlook Forms |
Faxes viewed using the
Outlook form via terminal services, are opened at maximum scale and must be
resized to view. |
Corrected. Screen resolution
is now determined by bits per pixel. |
|
63851 |
Server Module |
In a server collective,
faxes may be lost during a network outage. |
Corrected. Faxes in process
during a network outage are flagged as Information Incomplete and must
be resent. |
|
64440 |
Server Module |
Retry attempts do not follow
defined retry intervals. |
Corrected. Fax history
displays the correct retry intervals. |
|
64855 |
Server Module |
Using the <ATDATE:>
embedded code without entering a valid date format will cause the Server
Module to crash |
Corrected. Problem no longer
occurs. |
|
65041 |
Server Module |
Faxes requiring
administrator approval are not blocked by matching dialing rules once
approval is issued. |
Corrected. Faxes are blocked
as expected. |
|
63874 |
SMTP Gateway |
The performance of inbound
message processing is adversely affected if the gateway is configured for in
and outbound messaging. |
Corrected. Inbound messages
are processed as expected. |
|
64957 |
SMTP Gateway |
RTF or HTML formatted
messages sent from Outlook 2003 or 2007 clients creates
an additional page. |
Corrected. Problem no longer
occurs. |
|
62764 |
Web Access |
Faxes that contain an ampersand (&) in the Comments,
Account, or Matter field of the new fax dialog produces an error. |
Corrected. Faxes send as
expected. |
|
64336 |
Web Access |
Switching between delegate
and owner mailboxes generates an error. |
Corrected. Error no longer
occurs. |
|
64840 |
Web Access |
Unpublished phonebook
entries requiring a user password are not viewable. |
Corrected. Unpublished
delegate phonebook entries are viewable when a password is provided. |
|
62718 |
WorkServer |
Certain JPG files, if sent
through an e-mail gateway fail fax conversion. |
Corrected. JPG files convert
as expected. |
|
63458 |
WorkServer |
Short body documents are
printed as full page documents. |
Corrected. Short body
documents print as expected. |
|
64626 |
WorkServer |
SMS messages are not
available to RightFax servers via InterConnect. |
Corrected. Problem no longer
occurs. |
|
64837 |
WorkServer |
SMS messages do not route to
network folders. |
Corrected. Messages route as
expected. |
|
64972 |
WorkServer |
Equitrack archiving logs failed faxes as successful. |
Corrected. Problem no longer
occurs. |
|
65502 |
WorkServer |
Additional blank pages are
added to PCL documents. |
Corrected. PCL documents
convert as expected. |
RightFax 9.4 includes all of the fixes from RightFax 9.4 Feature/Service Pack 2 Service Release 5.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
62060 |
DocTransport |
The initial tone setting of
TR1034 fax channels configured for DTMF routing cannot be disabled. |
Corrected. The initial tone
setting can be disabled as expected. |
|
62904 |
DocTransport |
Outbound faxes over 999
pages are not blocked. |
Corrected. Outbound faxes
over 999 pages are blocked as expected. |
|
63653 |
DocTransport |
Outbound faxes that exceed
the number of pages allowed by a fax channel are not blocked
. |
Corrected. Faxes are blocked
as expected. |
|
63751 |
DocTransport |
Messages in the MSMQ are
lost if SQL connectivity is lost and the SQL server is rebooted. |
Corrected. Messages remain
in the queue and are processed as expected. |
|
63811 |
DocTransport |
The fax server name, as
shown in fax history, will contain unreadable characters if the server name
is 15 or more characters. |
Corrected. Problem no longer
occurs. |
|
63895 |
DocTransport |
Outbound faxes are delayed
if submitted to the fax server while the DocTransport
is stopped. Restarting DocTransport does not
resolve the issue. |
Corrected. Messages are
processed as expected. |
|
62568 |
Documentation |
P. 213 of the RightFax 9.3 Administrator's Guide
provides inaccurate instructions for configuring DocTransport
call blocking. |
Corrected. A revision of the
Administrator's Guide is included
with this release. |
|
64385/ |
Documentation |
The RightFax 9.3 Installation Guide provides inaccurate instructions
for installing and configuring RightFax in a Windows 2003 cluster. |
Corrected. A revision of the
Installation Guide is included with
this release. |
|
63393 |
FaxUtil |
Users with editor delegate
permission can delete faxes that have been split. |
Corrected. Users with editor
delegate permission cannot delete split faxes. |
|
63549 |
Integration |
FCL codes appear on PDF FFP
documents sent via e-mail. |
Corrected. FCL codes are
converted as expected. |
|
62056 |
Outlook Forms |
Faxes printed using the
Outlook form do not print as displayed, if the fax
was previously rotated using the Outlook form. |
Corrected. Rotating and
printing faxes using the Outlook form functions as expected. |
|
59774 |
Print to Fax |
Changing the print processor
used by RightFax Fax Printer from RightFax to Windows, does not change the
printer port, as required. |
Corrected. Problem no longer
occurs. |
|
63577 |
Print to Fax |
The Fine Mode option, found
in the Fax Information dialog box does not render outbound faxes in 200x200
resolution as expected |
Corrected. Fine mode renders
faxes in 200x200. |
|
61194 |
Push Proxy Gateway |
Changing the message
encoding format in the Push Proxy Gateway requires a restart of the DocTransport Module. |
Corrected. Changing the
message encoding format no longer requires a DocTransport
restart. |
|
63359 |
SAP |
Messages sent through the
SAP Gateway do not contain the correct sender metadata. |
Corrected. Faxes include
correct metadata as expected. |
|
63443 |
Server Module |
RightFax services, requiring
a password, will terminate if the password is 26 characters or more. |
Corrected. Problem no longer
occurs. |
|
63645 |
Server Module |
In a collective with 2 or
more nodes, fax retry settings may cause a fax to send twice. |
Corrected. Problem no longer
occurs. |
|
63709 |
Server Module |
Data input fields in the
Data Sharing tab of the Server module configuration are limited to 50 characters. |
Corrected. Input fields in
the Data Sharing tab now auto scroll, thus allowing additional character
input. |
|
59749 |
SMTP Gateway |
Auto-print jobs and SMTP
notifications, if enabled, will re-queue indefinitely if an SMTP notification
fails due to name resolution issues or addressing syntax errors. |
Corrected. Auto-print jobs
execute only if a SMTP notification is successful. |
|
63787 |
SMTP Gateway |
SMTP gateway reports
informational messages as errors in the Windows application event log. |
Corrected. Informational
messages are logged as informational. |
|
62491 |
SOAP Integration |
Attempting a Quick
Fax/Broadcast using the SOAP client generates an error. |
Corrected. Faxes send as
expected. |
|
63398 |
Web Access |
Recipient information cannot
be removed from the Web Access > Document Recipients window. |
Corrected. Recipients can be
removed. |
|
63510 |
Web Access |
Delegates configured with
the option to View First Page Only, cannot forward faxes |
Corrected. Forwarding faxes
is now possible. |
|
63578 |
WorkServer |
Some ArtLinePrinter.ttf font
characters do not convert as expected. |
Corrected.
ArtLinePrinter.ttf fonts convert as expected. |
RightFax 9.4 includes all of the fixes from RightFax 9.4 Feature/Service Pack 2 Service Release 4.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
62675 |
Admin Utilities |
PHNPrint generates a memory exception when the
-P switch is not used. |
Corrected. Memory exception
no longer occurs. |
|
61779 |
Captaris Sync |
Users may be deleted if
synchronizing with an LDAP server and the connection to the LDAP server is
lost. |
Corrected. Users are not
deleted. |
|
63335 |
COM API |
Fine Mode cannot be set
using the IsFineMode parameter. |
Corrected. The IsFineMode parameter functions as expected. |
|
63808 |
DocTransport |
DocTransport generates an error when starting after configuring a
TR1034 T1/E1 PCIe fax board using the Brooktrout config tool. |
Corrected. Error no longer
occurs. |
|
60513 |
DocTransport |
IPK files are delayed after
the \RightFax\Image folder exceeds 300,000 images. |
Corrected. Problem no longer
occurs. |
|
62214 |
DocTransport |
Sending faxes to a group 2
fax machine from a RightFax server configured with an Eicon
fax board causes DocTransport
to crash. |
Corrected. DocTransport does not crash. |
|
62671 |
DocTransport |
Call Grouping may cause
scheduling delays for faxes sent via the Integration module. |
Corrected. Faxes send as
expected. |
|
63870 |
DocTransport |
B channel does not reset
after a glare condition. |
Corrected. Problem no longer
occurs. |
|
61498 |
E-transport |
The reported sent time on
messages sent through E-Transport is off by one hour if the RightFax server
is configured to adjust for daylight savings time. |
Corrected. Problem no longer
occurs. |
|
62566 |
Exchange |
Exchange bound faxes and
notifications are lost if Exchange server connectivity is interrupted.
|
Corrected. Faxes and
notifications are routed once connectivity is reestablished.. |
|
62622 |
Exchange Gateway |
Using more than 39
characters in From Message field of the Exchange Gateway causes the
gateway to crash. |
Corrected. Problem no longer
occurs. |
|
62587 |
Integration |
Folder names that include a hyphen, create invalid command line parameters. |
Corrected. Folder names may
now include hyphens. |
|
62732 |
Integration |
FCL command elements with
more than 256 characters within “{{“ and “}}” causes
parse.exe to crash. |
Corrected. Problem no longer
occurs. |
|
62075 |
Notes |
Faxes sent in landscape
format are converted to portrait format if using the Midas C++ API and you
have configured the EFMSync to use the Notes Native
Export method. |
To resolve this issue,
install Microsoft Word on the RightFax server and enable the option to Force
Landscape Mode in the EFMSync > Gateway
document. |
|
63245 |
Notes |
Midas C++ API conversion
errors are not logged correctly. |
Corrected. Errors are logged
as expected. |
|
62394 |
Outlook Forms |
An error will occur when
choosing the Deny option of a notification
that is held for preview. This issue is know only to occur with Outlook 2003 SP3. |
Corrected. Errors no longer
occur. |
|
61437 |
SAP |
SAP gateway uses excessive
memory when connectivity to a SAP server is lost. |
Corrected. Problem no longer
occurs. |
|
61204/ |
Server Module |
The status of large faxes
does not update in a reasonable time frame. |
Corrected. The status of
large faxes is updated as expected |
|
62747 |
Server Module |
Fax servers with dialing
rules to send faxes through another server, may generate scheduling errors. |
Corrected. Problem no longer
occurs. |
|
62901 |
Server Module |
When forwarding a fax,
coversheets are not included. |
Corrected. Coversheets now
send with fax as expected. |
|
63040 |
Web Access |
German regional settings
cause the RightFax Remoting service to crash. |
Corrected. Problem no longer
occurs. |
|
61922 |
WorkServer |
Server-based (Windows GDI)
print jobs to a Xerox DT6135 PS3 fail to print. |
Corrected. Faxes print as
expected. |
|
62569 |
WorkServer |
A 12-hour timestamp
discrepancy exists for faxes sent using the PeopleSoft integration. |
Corrected. Timestamps are
now accurate |
|
62792 |
WorkServer |
Some PCL-6 documents do not
convert as expected. |
Corrected. Problem no longer
occurs. |
|
63073 |
WorkServer |
Outbound archiving fails to
create fax image files for all fax recipients. |
Corrected. Fax image files
are created and archived for each recipient. |
|
63272/ |
WorkServer |
Some FCL jobs do not convert
as expected. |
Corrected. FCL jobs convert
as expected. |
|
64934 |
WorkServer |
Multi-page .TIF files
containing different page widths do not convert properly or fail conversion. |
Corrected. Faxes convert as
expected. |
RightFax 9.4 includes all of the fixes from RightFax 9.4 Feature/Service Pack 2 Service Release 3.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
60534 |
API |
Faxes fail to expire when
using the lExpiresIn function. |
Corrected. Faxes now expire
when using the lExpiresIn function. |
|
62621 |
Brooktrout Fax Boards |
Brooktrout 1034 fax boards that are feature locked to v.17 fail
to send and receive faxes after installing Feature Pack 2. |
Corrected. Faxes send and
receive as expected. |
|
60615 |
Database Module |
A memory leak occurs when
the Database Module loses SQL connectivity. |
Corrected. Problem no longer
occurs. |
|
61611 |
Database Module |
Only the first 20 users as
shown in Enterprise Fax Manager can be selected using the DBPurge
utility. |
Corrected. All users are
shown and can be selected. |
|
62195 |
Database Module |
The RightFax Remoting service fails to clear statistic data from the dbo.statvalues table. |
Corrected. Statistic data is
now purged. |
|
61723 |
DocTransport Module |
DocTransport generates event log errors when
RightFax has over 20 dialing rules and is configured to use a SQL
server. |
Corrected. Errors no longer
occur. |
|
61784 |
DocTransport Module |
DocTransport generates an erroneous timeout causing dead air on
inbound calls. |
Corrected. Problem no longer
occurs. |
|
61933 |
DocTransport Module |
Brooktrout fax boards permit 911 calls. |
Corrected. 911 calls are
blocked. |
|
61915 |
External Document Connector |
Applying Feature/Service
Pack 2 causes .JOB files to contain incorrect JobTime
values. |
Corrected. Problem no longer
occurs. |
|
61728 |
Enterprise Fax Manager |
Saving a dialing rule on a
Remote BoardServer reports and error (2) in
transacting named pipe in the Windows > Event Viewer > Application log.
|
Corrected. Problem no longer
occurs. |
|
61930 |
Enterprise Fax Manager |
Removing a value from a
destination table in Enterprise Fax Manager removes the same value from all
other destination tables. |
Corrected. Problem no longer
occurs. |
|
60106 |
Exchange 2000/2003 Connector |
All inbound messages and
notifications are discarded if the 'Administrator' account is not valid. |
Page 17 of the Exchange Module Guide now documents
this requirement. |
|
62554 |
Exchange 2000/2003 Connector |
Partial faxes may become
stuck in the MTS-IN queue when the Connector automatically stops and restarts
to avoid server limits. |
Corrected. Faxes process as
expected. |
|
61806 |
FaxUtil |
FaxUtil and FaxCtrl.exe generate exception errors and terminate
when addressing a fax from a MAPI personal address book. |
Corrected. Problem no longer
occurs. |
|
62318 |
FaxUtil |
Faxes routed to a network
directory show an erroneous time information in the
fax history page. |
Corrected. Faxes routed to a
network directory now have an accurate timestamp. |
|
61742 |
Integration Module |
Faxes fail to send via the
XML/Java API after applying Feature/Service Pack 2. |
Corrected. Faxes send as
expected. |
|
61398 |
Server Module |
Using the Server Module to
change the "Record DNIS Information" field from Fax DID to Billing
Code 1 does not populate fax history > Billing Code 1 field with DNIS
information. |
Corrected. DNIS information
records as expected. |
|
61830 |
Server Module |
Automated database
maintenance cannot be disabled. |
Corrected. Automated
database maintenance can be disabled as expected. |
|
61866 |
Server Module |
Faxes with a status of
"Problem Scheduling" do not generate "Error Encountered"
notifications. |
Corrected. Notifications are
generated as expected. |
|
61885 |
Server Module |
Times specified on the
Forced Scheduling option in the Enterprise Fax Manager > Groups
configuration are not converted from GMT time. |
Corrected. Time is converted
as expected. |
|
58890 |
Web Access |
Users without delegate
permission can view the contents of the 'All' folder. |
Corrected. Problem no longer
occurs. |
|
59221 |
Web Access |
Folders with Japanese
characters cannot be deleted. |
Corrected. Folders can be
deleted. |
|
61659 |
Web Access |
Using Web Access to split a
fax generates the erroneous fax status message of, 'Invalid Characters'. |
Corrected. Splitting a fax
with Web Access generates the correct fax status of 'Information Incomplete'. |
|
61660 |
Web Access |
Searching for contacts in
Web Access displays unpublished phonebook entries. |
Corrected. Only published
phonebook entries are shown when searching for contacts using Web Access. |
|
61706 |
Web Access |
Renaming folders with
special characters (e.g., {} , | ,~)
generates errors. |
Corrected. Problem no longer
occurs. |
|
61904 |
Web Access |
Routing or forwarding multiple
faxes with Web Access generates an error. |
Corrected. Routing and
forwarding multiple faxes functions as expected. |
|
61913 |
Web Access |
After applying
Feature/Service Pack 2, recipients added via phonebook entries do not display
in the recipient field. |
Corrected. Problem no longer
occurs. |
|
62350 |
Web Access |
Searching phonebook entries
returns wrong results. |
Corrected. Search results
return as expected. |
|
60156 |
WorkServer |
Some diacritical characters
do not convert as expected. |
Corrected. Problem no longer
occurs. |
|
60808/ |
WorkServer |
PCL documents containing
large font sizes do not convert as expected. |
Corrected. Problem no longer
occurs. |
|
61386 |
WorkServer |
A seven hour discrepancy is
reported in the history record of faxes that are sent or received via
Interconnect. |
Corrected. Interconnect
history records as expected. |
|
61889 |
WorkServer |
The "date and time
printed" macros shown on the time strips are shown in GMT time instead
of local time. |
Corrected. Data and time
printed macros show local time as expected. |
|
62046 |
WorkServer |
Sending G3 format TIFF that
was saved using the FaxUtil viewer, causes WorkServers to terminate. |
Corrected. Problem no longer
occurs. |
RightFax 9.4 includes all of the fixes from RightFax 9.4 Feature/Service Pack 2 Service Release 1.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
61202 |
API |
The RFaxGetNewFaxCount()
parameter does not function as expected. |
Corrected. RFaxGetNewFaxCount() parameter now functions as expected. |
|
59445 |
COM API |
The 'Can modify user
options' delegate permission property is not included in the COM API
documentation. |
The 'Can modify user
options' delegate permission property (MiscPermissionModifyUserOptions)
will appear in a future release of the COM API
guide. |
|
59621 |
COM API |
Outbound faxes set to high
priority using the COM API are sent with the default (normal) priority. |
Corrected. Faxes are now
sent with high priority. |
|
59589 |
Captaris Sync Module |
A memory performance issue occurs when Captaris Sync
processes reach 2GB or more or memory. |
Corrected. Problem no longer
occurs. |
|
60637 |
Captaris Conversion Engine |
Word documents containing
macros fail to convert and are not sent. |
Corrected. Word documents
convert as expected. |
|
58706 |
Database Module |
RightFax generates 'Error 2'
when integrated with Captaris Workflow. |
Corrected. Problem no longer
occurs. |
|
59555 |
Database Module |
Deleting a user from
RightFax does not remove user fax records from the database. |
Corrected. Fax records and
image files are permanently deleted when the "Days to keep deleted fax
records" expires for the Everyone group. |
|
52141 |
DocTransport Module |
SMS messages cannot be
relayed to other RightFax servers using least-cost routing. |
Least-cost routing now
supports SMS message routing. |
|
61160 |
DocTransport Module |
The elapsed transmission
time of any fax greater than 16 seconds is reported as 16 seconds and not the
actual transmission time. |
Corrected. Elapsed
transmission time is reported as expected. |
|
61226 |
DocTransport Module |
Sent fax history does not
contain the name of the originating fax server. |
Corrected. Outbound fax
history now displays the originating fax server name. |
|
43992 |
Enterprise Fax Manager |
If the 'Enable duplicate
routing code warning' is enabled and a duplicate routing code is
detected, the option to 'Not be prompted again' fails to disable the
'Enable duplicate routing code warning'. |
Corrected. Problem no longer
occurs. |
|
59561 |
Enterprise Fax Manager |
User fax priority cannot be
accurately configured in Enterprise Fax Manager. |
Corrected. Problem no longer
occurs. |
|
60476 |
Exchange 2000/2003 Connector |
The connector service may
stop faxing when Exchange server limits are reached. |
When Exchange server limits
are reached, Exchange will attempt to shut down the connector service, and
wait 30 seconds before checking the status. If, after 10 attempts (5 minutes)
the service has not shut down it will attempt to kill the process and continue
to check the status. |
|
60263 |
Exchange Gateway |
Sending faxes through
Outlook increases the Exchange Gateway memory usage. |
Corrected. Problem no longer
occurs. |
|
61247 |
FaxAge |
FaxAge assumes an end date of 12/31/2010 and ignores the -e
switch if an NT User is specified with the -P Switch. |
Corrected. Problem no longer
occurs. |
|
59103 |
FaxUtil |
The German version of FaxUtil includes incorrect GUI translations. |
GUI is now correct. |
|
59771 |
FaxUtil |
The Italian version of FaxUtil includes incorrect GUI translations. |
GUI is now correct. |
|
60155 |
FaxUtil |
Combining faxes in FaxUtil generates 'Incomplete Information"
notification. |
Corrected. Notification is
no longer generated. |
|
60431 |
FaxUtil |
Disabling the 'Native Attach
Document Checkbox' option, permanently removes the Native column from the FaxUtil attachment dialogue. |
Corrected. Problem no longer
occurs. |
|
60518 |
FaxUtil |
While in 'Administrative
Mode', Administrators who do not have the 'Administrator Can Bypass Privacy
Restrictions' permission enabled can view the faxes of users. |
Corrected. Administrative
mode functions as expected. |
|
60722 |
FaxUtil |
FaxUtil tooltips do not display on mouse-over. |
Corrected. Tooltips are
displayed as expected. |
|
60747 |
FaxUtil |
Sending a previously sent
fax to a new fax number and adding a contact via a RightFax phonebook
automatically adds the original recipient to the list of current recipients. |
Corrected. This behavior is
now controlled via the FaxUtil sending options. From the FaxUtil
menu bar choose: Tools > Options > Sending, and disable to the option
to 'Prepopulate fax information on forward'. |
|
60380 |
Integration Module |
Uncompressed TIF files sent
through the integration module convert to black pages. |
Corrected. Uncompressed TIF
files convert as expected. |
|
60451 |
Integration Module |
The FCL code '{{imagetype PCX}}' fails to include a PCX attachment when
used with the {{type mime}} FCL code. |
Corrected. PCX attachments
are now included. |
|
60489 |
Integration Module |
A fax containing a subject
line over 255 characters causes mimesend.exe to crash. |
Corrected. Problem no longer
occurs. |
|
57487 |
Server Module |
'Held for Preview'
notifications resend when database maintenance is run. |
Corrected. Notifications are
no longer sent. |
|
62188 |
Server Module |
Faxes will not send during
the first hour of daylight savings time on 4 November 2007. |
Corrected. Problem no longer
occurs. |
|
60654 |
SMTP Gateway |
Fax routing fails when
attachments over 100 MB are sent through an SMTP server hosted on a Lotus
Domino server. |
Corrected. Problem no longer
occurs. |
|
59596 |
Web Access |
Changing the default
coversheet in Enterprise Fax Manager or FaxUtil is
not reflected in Web Access. |
Corrected. Problem no longer
occurs. |
|
59663 |
Web Access |
Italian regional clients
display the Main, Trash, and All folders in English. |
Corrected. Folders are
displayed in Italian. |
|
60208 |
Web Access |
Faxes with a status of 'Held
for Preview' can be edited in Web Access. |
Corrected. Faxes can no
longer be edited with a 'Held for Preview' status. |
|
60285 |
Web Access |
Turkish regional clients
generate an error when clicking on the outbox and
options views. |
Corrected. Problem no longer
occurs. |
|
60784 |
Web Access |
Users without the 'Can
Edit/Add Library Docs' permission are able to create library documents using
Web Access. |
Corrected. Users must have
the 'Can Edit/Add Library Docs' permission enabled to create library
documents. |
|
61092 |
Web Access |
The 'Can Create Fax'
delegate permission does not function with Web Access. |
Corrected. The 'Can Create
Fax' delegate permission functions as expected. |
|
61200 |
Web Access |
Received fax history cannot
be viewed in Web Access. |
Corrected. Received fax
history can now be viewed. |
|
60630 |
WorkServer |
LPR conversions fail after a
WorkServer has processed 509 or more LPR work
requests. |
Corrected. LPR jobs convert
as expected. |
|
60753 |
WorkServer |
Some JPG attachments are
flagged a blank files and are thus not converted. |
Corrected. JPG attachments
convert as expected. |
|
60836 |
WorkServer |
Some multi-page PCL forms
convert to single page documents. |
Corrected. Problem no longer
occurs. |
|
61093 |
WorkServer |
TIF files created via an
IMECON print driver fail to convert as expected. |
Corrected. Files convert as
expected. |
|
61246 |
WorkServer |
Faxes routed to a network
directory, using Unique ID's, and separated pages, have different naming
convention for 0-9 and A-F Hex values. |
Corrected. Problem no longer
occurs. |
© 2008 Captaris,
Inc. All rights reserved.
version 1.0
12/04/2008