This readme file provides late-breaking or other information that supplements
the RightFax documentation. Service Releases (formerly RightFax Hotfixes) are
the means by which RightFax product updates are distributed from the Captaris
Web site. A Service Release may contain updates for system reliability, program
compatibility, performance improvements, and more. Each Service Release contains
new fixes plus all the fixes from previous Service Releases.
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 updates, 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.
Service Release 6 for RightFax version 9.3 adds new features and contains numerous updates to the core server components, fax board drivers, and RightFax clients. See a complete list of new updates here. Service Release 6 will update both North American and International versions of RightFax.
WARNING: Applying Service Release 6 will overwrite all files updated by the Service Release, regardless of the dates and version numbers of those same files already installed on your server. Verify a functional backup before continuing.
Below is a cumulative list of enhancements and new features introduced to RightFax 9.3 FP2 beginning with Service Release 1.
Lotus Notes Integration. The optional Lotus Notes update includes the following new features: simplified database install and setup, multi-mail integration design, support for Notes R7 and R8, additional language support, and new online help. For more information, including install instructions, see the Lotus Notes Update Readme.
RightFax client application support for Japanese and Simplified Chinese. The following RightFax clients are available in Japanese and Simplified Chinese: FaxUtil and online help, RightFax Web Access and online help, RightFax print driver and online help (also known as the FaxCtrl client), RightFax form for Microsoft Outlook and online help, Enterprise Fax Manager and online help, and Enterprise Fax Manager, Web Edition. RightFax Control Panel applications are not translated.
NOTE: Data entry using double-byte character sets (such as Japanese and Simplified Chinese) is not available with this release.
Additional fax board support. The addition of Service Release 6 extends Cantata/Brooktrout fax board support. A list of these new boards is provided below. For a complete list of RightFax supported fax boards, see the RightFax Fax Board Guide located in the \RightFax\Docs folder on the RightFax server or online at the Captaris RightFax documentation page - http://www.captaris.com/support/documentation/rightfax/index.html.
Analog Boards
TR1034+E2-L (half-sized)
TR1034+E2-C
TR1034+E4-C
TR1034+E2-D
TR1034+E4-D
From the RightFax server, download the RightFax 9.3 Service Release 6 update for North American or International servers and clients from: http://www.captaris.com/support/downloads/rightfax/93/index.html
Installing Service Release 6 requires an existing installation of RightFax 9.3 Feature/Service Pack 2. Verify that Feature/Service Pack 2 is installed on the computer you plan to install Service Release 6 on.
If your are installing Service Release 6 to acquire Japanese and Simplified Chinese support, you must install on localized Japanese or Simplified Chinese versions of Microsoft Windows. Multilingual User Interface (MUI) packages are not supported.
Microsoft Internet Information Services must be stopped for the duration of the service release install.
The instructions below assume you have a fully licensed version of the Midas Rich Text C++ API and have integrated it with RightFax. Before attempting these steps, verify the presence of the files midisv.dll and midisv.lic in the \RightFax\Gateway directory on the RightFax server. If these files are not found, you are not using the Midas Rich Text C++ API and thus do not need to apply these steps. For more information about the Midas Rich Text C++ API see Configuring RightFax 9.3 for Midas C++ API or visit the Midas website at http://www.geniisoftware.com/showcase.nsf/MidasAgree
Log on to the RightFax server as an Administrator.
Stop the RightFax email gateway.
Create a back up copy of the midisv.dll and notesgateway.exe files located in the \RightFax\Gateway folder.
Remove the midisv.dll file from the \RightFax\Gateway folder.
Download the latest version of the midisv.dll file at http://www.geniisoft.com/showcase.nsf/MidasActionOpenAgent&RetrieveDownload=MA60v370rf.zip&DownloadID=MA60v370rf.zip.
Copy the latest version of midisv.dll to the \RightFax\Gateway folder.
Restart the RightFax email gateway.
Follow the steps below if your organization uses .DOC coversheets and has installed Word 2007 on the RightFax server. These steps can be performed before or after the installation of Service Release 6.
Log on to the RightFax server with an Administrator account.
Open Windows Explorer and browse to the \RightFax\FCS\Doc folder.
Open the FCS.doc file.
Click the Close button at the Show Repairs window.
Save and close FCS.doc.
Repeat these steps for all .DOC coversheets.
The use of Internet Explorer pop-up blockers limits the functionality of RightFax Web Access clients. Disable all pop-up blockers on all clients to ensure full Web Access functionality. This step can be performed before or after the installation of Service Release 6.
If you uninstall the RightFax Connector for Exchange 2000/2003 servers at any point after installing Service Release 6, a reboot of the Exchange Server for which you have uninstalled the connector from is required.
Installing Enterprise Fax Manager Web Edition (WebEFM) requires the Chinese, Japanese, or, English editions of Microsoft IIS servers. Additional IIS language support is not available at this time.
Importing RightFax server data (users, groups, faxes, dialing rules, etc) from another RightFax server using Administrative Utilities or by using the drag and drop functionality of Enterprise Fax Manager requires character set and code-page compatibility between the source and target servers. The operating system of both servers must be configured to use the same code-pages. For example, a server configured for English cannot import data from a server configured for Japanese.
Apply this update to all version 9.3 RightFax servers before installing on RightFax remote servers.
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 Service Release 6 . Installing Service Release 6 with this file set to read-only will fail to properly update the file and in the process will render the fax boards inoperable.
NOTE: Modifying a post Feature/Service Pack 2 installation of RightFax via the RightFax CD or by using the Windows add/remove programs Control Panel will require a reinstall of Feature/Service Pack 2 and Service Release 6.
The installation of Service Release 6 for RightFax 9.3 can be customized by using the setup switches below. To use these switches you must run the RightFax932_SR6.exe file from a command line followed by the switches of your choosing. For example, to install the Service Release with no user interaction and to automatically shutdown all local RightFax services, you would run the following command from the folder that contains the RightFax932_SR6.exe file (C:\RightFaxServiceRelease in this example).
C:\RightFaxServiceRelease\RightFax932_SR6.exe /quiet /shutdownSetup switches available in Service Release 6
/quiet Runs setup silently with no GUI.
/repair Forces a reinstall over the same Service Release 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 Service Release folders and files to a specific folder. A log file called ExtractingFiles_<date_time>.log, will also be created here.
/clientinstall=<clientInstallDir> Applies the Service Release to a path containing the RightFax client installation source. See Applying Service Release 6 to Client Computers for more information about this setup option.
Follow the steps below to install Service Release 6. These steps do not use any of the setup options listed above.
NOTE: To install the Service Release in a RightFax environment that uses Windows (NT) Authentication for the RightFax database, you must logon to the fax server with a Windows account that is a member of RightFax database sysadmin roles. Verify this requirement with your SQL Administrator before continuing.
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.
Log on to the RightFax server as an Administrator.
Double-click RightFax932_SR6.exe. The RightFax 9.3 Service Release 6 Installer opens.
Click the Start button to begin the Captaris Update Wizard.
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.
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.
Select a language from the pick-list. Your selection will affect the language used by most RightFax clients. Captaris recommends selecting the language used by your Windows installation.
The Captaris Update Wizard will scan your local RightFax server for RightFax services that are running and open RightFax applications. If RightFax services are running or if you have a RightFax application open, the wizard will stop or close all RightFax services and applications. To continue, click Next at the Services and Applications step.
To apply the service release, click Next.
To complete the installation, click Close .
Repeat these steps on all remote RightFax servers. These will include:
Remote Board Servers
Remote WorkServers
Remote E-mail Gateways
Exchange 2000 or 2003 servers that have the RightFax Connector for Exchange installed. Do not install on Exchange 2007 servers.
Remote IIS servers with RightFax web-based applications installed
If your environment uses the RightFax Shared Services Module (also know as a server collective), follow the steps below to install Service Release 6.
IMPORTANT: Installing Service Release 6 in a server collective requires downtime for all servers joined to the collective. Please plan your installation accordingly.
NOTE: To install the Service Release in a RightFax environment that uses Windows (NT) Authentication for the RightFax database, you must logon to the fax server with a Windows account that is a member of RightFax database sysadmin roles. Verify this requirement with your SQL Administrator before continuing.
Shut down all RightFax services and applications on all RightFax servers joined to the collective and on all remote servers. Remote servers will include:
Remote Board Servers
Remote WorkServers
Remote E-mail Gateways
Exchange 2000 or 2003 servers that have the RightFax Connector for Exchange installed. Do not install on Exchange 2007 servers.
Remote IIS servers with RightFax web-based applications installed
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.
Log on to the RightFax server as an Administrator.
Double-click RightFax932_SR6.exe. The RightFax 9.3 Service Release 6 Installer opens.
Click the Start button to begin the Captaris Update Wizard.
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.
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.
Select a language from the pick-list. Your selection will affect the language used by most RightFax clients. Captaris recommends selecting the language used by your Windows installation.
The Captaris Update Wizard will scan your local RightFax server for RightFax services that are running and open RightFax applications. If RightFax services are running or if you have a RightFax application open, the wizard will stop or close all RightFax services and applications. To continue, click Next at the Services and Applications step.
To apply the service release, click Next.
To complete the installation, click Close .
Repeat these steps on all others servers joined to the server collective and on all remote RightFax servers.
NOTE: To install the Service Release in a RightFax environment that uses Windows (NT) Authentication for the RightFax database, you must logon to the fax server with a Windows account that is a member of RightFax database sysadmin roles. Verify this requirement with your SQL Administrator before continuing.
Stop all RightFax services on all remote RightFax servers.
If you have not already done so, back up the entire \RightFax directory structure and the SQL database for RightFax.
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.
Double-click RightFax932_SR6.exe. The RightFax 9.3 Service Release 6 Installer opens.
Click the Start button to begin the Captaris Update Wizard.
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.
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.
Select a language from the pick-list. Your selection will affect the language used by most RightFax clients. Captaris recommends selecting the language used by your Windows installation.
The Captaris Update Wizard will scan your local RightFax server for RightFax services that are running and open RightFax applications. If RightFax services are running or if you have a RightFax application open, the wizard will stop or close all RightFax services and applications. To continue, click Next at the Services and Applications step.
To apply the service release, click Next.
To complete the installation, click Close .
Using Cluster Administrator, move the RightFax share to the secondary node.
Complete steps 4-9 on the secondary node,
Bring the RightFax resources back on-line.
Service Release 6 for client computers is an update to
RightFax client applications. These clients include: FaxUtil; RightFax Fax
Printer and Tray Icon (FaxCtrl); and Enterprise Fax Manager. To
update RightFax clients, run the Service Release installer on each client
workstation or update the client installation source files 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).
NOTE: Modifying a post Feature/Service Pack 2 installation of RightFax via the RightFax CD or by using the Windows add/remove programs Control Panel will require a reinstall of Feature/Service Pack 2 and Service Release 6.
IMPORTANT: If you are installing this update to obtain RightFax client support for Japanese or Simplified Chinese, you must install Service Release 6 using the small-scale update instructions.
WARNING: Do not install this update on RightFax SOAP client computers.
This section outlines the steps needed to update RightFax clients on a small-scale.
Logon to the client workstation as an Administrator.
Double-click the RightFax 9.3 Service Release 6 installer (RightFax932_SR6.exe).
Click the Start button to begin the Captaris Update Wizard.
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.
Select a language from the pick-list. Your selection will affect the language used by most RightFax clients. Captaris recommends selecting the language used by your Windows installation.
The Captaris Update 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.
Click Close to complete the installation.
This section outlines the steps needed to update RightFax clients on a large-scale.
Copy or download the RightFax 9.3 Service Release 6 installer (RightFax932_SR6.exe) to the location that contains the 9.3 client installation source folder.
Open command prompt and change to the directory that contains the Service Release 6 installer.
Type the following command and press Enter: RightFax932_SR6.exe /clientinstall="<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:RightFax932_SR6.exe /clientinstall="C:\RightFax"
Open installation source folder and double-click the file Setup.ini
Look for the entry ProductVersion=<version> Change this value to ProductVersion=9.3.2.600.
Look for the entry 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 Service Release 6 applied.
CmdLine=/qn REINSTALL=ALL REINSTALLMODE=vamus 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"
Once the install parameters are entered, save and close the Setup.ini file.
If you are installing new fax clients, you may now redistribute the client software using automated distribution software.
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 /fvamus \\share\RightF~1.msi
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.
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
RightFax 9.3 Service Release 6 or greater
Installed and licensed version of the Midas Rich Text 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.
Log on to the RightFax server as an Administrator.
Stop the RightFax E-mail Gateway module.
Log on to the EFMSync database using a Lotus client.
Open the gateway document and change the Notes Form Export Method to Notes Native Export. This option is found under Send Outbound Faxes section
Save and close the gateway document.
Restart the RightFax E-mail Gateway module.
|
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. |
|
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 9.3 RightFax 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 Installation Guide for RightFax 9.3 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. |
|
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. |
|
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. |
|
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 is provided below and will appear in a future release of the COM API guide. MiscPermissionModifyUserOptions |
|
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. |
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
60736 |
Database Module |
DBPurge times-out when deleting 65,000 or more fax records. |
Follow the steps below to resolve this issue: 1. On the RightFax server, open the Windows Registry and browse to the subkey: HKLM\Software\RightFax\Remoting 2. Create a new DWORD entry called CommandTimeout. 3. Set the value of the CommandTimeout entry to the number of seconds needed for SQL commands to complete. Set the value to 0 to eliminate the timeout period. 4. Close the Windows Registry. 5. Open the Windows Control Panel. 6. Double-click the RightFax Server icon. The Server configuration opens 7. Click the Advanced tab followed by the pick-list button next to the SQL Connection box. The RightFax SQL Connection Editor windows opens. 8. Click the Advanced tab followed by the pick-list button next to the SQL Connection box. The Data Link Properties window opens. 9. Click the Advanced tab and enter the number of seconds needed for SQL commands to complete. The number you enter here should match the value you entered in step 3 above. |
|
55719 |
DocTransport Module |
The DocTransport Module fails to start if a Eicon BRI faxboard is installed and does not have all channels activated. |
Corrected. DocTransport can now start if all channels are not activated. To add this functionality, open the registry subkey: HKLM/Software\RightFax\DocTransport\Transports\Eicon\Device#xx Set the 'Channel_Ability' DWORD value to 1. This must be completed for each device and channel key. |
|
59536 |
DocTransport Module |
DocTransport discards pages containing 10 or more lines of corrupted text. |
A new registry key to resolves this issue. 1. Open the Windows registry to: HKLM\Software\RightFax\DocTransport\Transports\Brooktrout 2. Add a new DWORD value called: AcceptErrorPages. Set the value to 1. 3. Close the Windows registry. |
|
60536 |
DocTransport Module |
Asterisks (*) are treated as DTMF terminators. The option to disable this function does not exist. |
Asterisks can now be treated as a non-terminating character. To add this functionality, open the registry subkey: 1. HKLM/Software\RightFax\DocTransport\Transports\Brooktrout2. Create a new DWORD entry called AsteriskTerminates. 3. To prevent asterisks from being treated as DTMF terminators, set the value to 0. To restore the default functionality, set the value to 1. 4. Close the Windows Registry. |
|
58657 |
Enterprise Fax Manager |
Commas (,) are not recognized as dialing rule characters. |
Corrected. To implement this feature: 1. Run Regedit and open: HKLM\Software\RightFax\DocTransport 2. Edit the ValidPatternChars value to contain the data of: 0123456789*#~\, 3. Close the Windows registry. |
|
60855 |
Exchange Gateway |
In a multiple Exchange Gateway environment, faxes sent from a gateway that has unexpectedly stopped, will not be processed by another gateway until 10 minutes have passed. |
Follow the steps below to remove the gateway processing timeout period. This allows any available Exchange Gateway to send faxes. 1. On the RightFax server, open the Windows Registry and browse to the subkey: HKLM\Software\RightFax\Gateway\Gateway 2. Set the PulseFileTimeout value to 0 3. Create a new DWORD entry called ProcessingTimeout. 4. Set the value to 0. 5. Close the Windows Registry.
Follow these steps set the gateway processing timeout period in minutes. 1. On the RightFax server, open the Windows Registry and browse to the subkey: HKLM\Software\RightFax\Gateway\Gateway 2. Set the PulseFileTimeout value to 0 3. Create a new DWORD entry called ProcessingTimeout. 4. Once entered, the ProcessingTimeout value will equal the time (in minutes) before another gateway will begin processing faxes. 5. Close the Windows Registry. |
|
56420/ 56611 |
FaxUtil |
Sending a fax with FaxUtil, Print-to-Fax, or Quick Fax Broadcasts will modify the Windows Foreground Lock Timeout value, thus assigning higher priority to background applications. |
FaxUtil, Print-to-Fax , and Quick Fax Broadcasts no longer modify the Windows Foreground Lock Timeout value provided the following registry setting is implemented. 1. Close FaxUtil. 2. Open the Windows Registry and browse to the subkey: HKEY_CURRENT_USER\Software/RightFax Client\FUW32\ 3. Set the ForegroundLockMode DWORD value to 1. 4. Close the Windows Registry. NOTE: To undo this behavior, set the ForegroundLockMode DWORD value to 0. |
|
59894 |
Install |
The path to the executable file that runs the Captaris Conversion Engine (located in the Windows Registry) maybe incorrect if you performed an in-place upgrade to RightFax 9.3 from version 9.0 |
Verify the correct path by checking the following Registry subkey: 1. On the RightFax server, open the Windows registry to, HKLM\System\CurrentControlSet\Services\RFISOConv 2. Verify the path to RFISOConv.exe points to \Program Files\RightFax\WorkSrv\RFISOConv.exe 3. Close the Windows registry. |
|
64555 |
Integration Module |
ParseXML generates duplicate UniqueIDs when the CurrentFile value reaches 9 digits. |
Follow the steps below to add a 3 character prefix to all unique ID's created by ParseXML processes. 1. Run Regedit and open HKLM\Software\RightFax\Production\XML 2. Create a new subkey called: 3. Create a REG_SZ entry called: UniqueIDPrefix 4. Edit the above entry to contain a 3 character identifier. If you do not enter an identifier, the default value (XML) will be used. 5. Close the Windows Registry. |
|
56279/ |
SAP Module |
Faxes without a recipient fail to send through the SAP gateway and cause the gateway to crash. |
A registry entry is required for sending faxes without a recipient. 1. On the RightFax server, open the Windows registry to, HKLM\Software\RightFax\SAP\SAP1 . Substitute SAP1 with whatever number your SAP gateway is (e.g., SAP2, SAP3, etc). 2. Add a new DWORD value called: AllowBlankRecipientName. Set the value to 1. 3. Close the Windows registry. *Note: Enabling this option will send the faxes without recipient information through the Default user account and will only contain the fax number. |
|
59315 |
SMTP Gateway |
Inbound SMTP messages, with addressing syntax errors, will re-queue indefinitely. |
Follow the steps below to disable retries for errors not related to SMTP Server connectivity: 1. Run Regedit and open HKLM\Software\RightFax\Gateway\Gateway\ 2. Create the a DWORD entry called: RetryOnNonConnectionErrors 3. Set the value of the above entry to 0 (zero). 4. Close the Windows Registry. |
|
60818 |
SMTP Gateway |
Certain Microsoft Word attachments fail to properly convert when sent through the SMTP gateway. |
Follow the steps below to resolve this issue: 1. Run Regedit and open HKLM\Software\RightFax\Gateway\Gateway\ 2. Create the a DWORD entry called: DoSubDecodeWhenDecodingBody 3. Set the value of the above entry to 0 (zero). 4. Close the Windows Registry. |
|
64034 |
SMTP Gateway |
Required coversheet fields are not enforced by the SMTP gateway. |
Follow the steps below to resolve this issue: 1. Run Regedit and open HKLM\Software\RightFax\Gateway\Gateway\ 2. Create the a DWORD entry called: EnforceRequiredCoversheetFields 3. Set the value of the above entry to 1. 4. Close the Windows Registry. |
|
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\Worksrv#, where # is the WorkServer # (e.g., WorkServer 1) configured for PCL conversions. 2. Create the a REG_SZ entry called ControlPCLFileName. 3. Set the value of the above entry to 1. 4. Close the Windows Registry. NOTE: To undo this behavior, set the ControlPCLFileName value to 0. |
|
64917 |
WorkServer |
FCL print jobs sent to a remote WorkServer computer fail. |
To resolve this issue, follow the steps below. 1. Run Regedit and open HKLM\Software\Rightfax\WorkServer\Worksrv#, where # is the WorkServer # (e.g., WorkServer 1) configured for CVL conversions. 2. Create a REG_SZ entry called: AlwaysQueueFCLPrint 3. Set the value of the above entry to 1. 4. Close the Windows Registry. NOTE: To undo this behavior, set the ControlPCLFileName value to 0. |
|
58369 |
WorkServer |
After installing Hotfix 1, all files converted by a RightFax fax printer 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\Worksrv#, where # is the WorkServer # (e.g., WorkServer 1) configured for fax conversions. 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 600 decimal PCL6_AdditionalParams - Value of -dTextAlphaBits=2 3. Close the Windows registry editor. |
The Service Release 6 installation creates a log file that can be referenced for troubleshooting purposes. Look for the file RightFax93SR6_date_time.log, located at the root of the RightFax installation folder.
©2008 Captaris. All rights reserved.
version
1.0
7/8/2008