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 3 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 3 will update both North American and International versions of RightFax.
WARNING: Applying Service Release 3 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.
Listed below are the enhancements and new features introduced to RightFax 9.3 FP2 with the addition of Service Release 3.
|
Analog Boards TR1034+E2-L (half-sized) |
From the RightFax server, download the RightFax 9.3 Service Release 3 update for North American or International servers and clients from: http://www.captaris.com/support/downloads/rightfax/93/index.html
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/MidasAction?OpenAgent&RetrieveDownload=MA60v370rf.zip&DownloadID=MA60v370rf.zip.
Copy the latest version of midisv.dll to the \RightFax\Gateway folder.
Restart the RightFax email gateway.
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.
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 3 . Installing Service Release 3 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 3.
C:\RightFaxServiceRelease\RightFax932_SR3.exe /quiet /shutdown
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_SR3.exe. The RightFax 9.3 Service Release 3 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.
The Captaris Update Wizard will scan your local RightFax server for RightFax services that are running and open applications. If RightFax services are running or if you have a RightFax application open, you must click the Shutdown button to stop all RightFax services and close RightFax applications. Click Next to begin the installation.
Click Close to complete the installation.
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
Remote IIS servers with RightFax web-based applications installed
All servers that share a RightFax database
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_SR3.exe. The Captaris Update Wizard 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.
Shutdown all RightFax services on Remote Board Servers, and if necessary: Remote WorkServers; Remote E-mail Gateways; Remote IIS servers; and servers within a RightFax collective. If you have shutdown all remote RightFax services, or do not use remote RightFax servers (all clusters use Remote Board Servers), place a checkmark in the box next to the text that reads 'All remote RightFax services have been manually shutdown'. Click Next to continue.
Verify that the RightFax resources have been shutdown and that you are installing this update on the active node. At the Special Cluster Requirements screen, place checkmarks into the boxes confirming that you have shutdown the RightFax resources and are installing on the active node. Click Next to continue.
The Captaris Update Wizard will scan your local RightFax server for running RightFax services (cluster resources) and open applications. All services should be shutdown using Cluster Administrator, and not the update wizard. If the Captaris Update Wizard displays running services, you must shutdown the RightFax services using Cluster Administrator. Failing to shutdown RightFax services with Cluster Administrator will result in a cluster fail-over. After shutting down the RightFax services, click the rescan button. The Captaris Update Wizard should now list no running services or open application. Click Next to begin the installation.
Click Close to complete the installation.
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 3 for client computers is an update to RightFax client applications. These clients include: FaxUtil; RightFax Fax Printer and Tray Icon (FaxCtrl); Soap Clients; and Enterprise Fax Manager. These clients may be updated by completing a local installation on each client workstation or by updating the client installation source files to this Service Release version, followed by a global reinstall of the RightFax clients.
The instructions under the large-scale deployment section assume you have created a client installation source on a network file share. After updating the installation source you must then re-distribute the client software by using the built-in installation functionality of RightFax and third-party automated distribution software (such as Group Policy).
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 3.
Login to the client workstation as an Administrator
Double-click the RightFax 9.3 Service Release 3 installer (RightFax932_SR3.exe).
Click the Start button to begin the Captaris Update Wizard.
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.
Copy or download the RightFax 9.3 Service Release 3 installer (RightFax932_SR3.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 3 installer.
Type the following
command and press Enter: RightFax932_SR3.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:
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.200.
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.
CmdLine=/qn REINSTALL=ALL REINSTALLMODE=vamus ALLUSERS=1 REBOOT=REALLYSUPRESS /l*v "%TEMP%\RightFax Client Install.log"
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 3 or greater
Installed licensed version of the Midas Rich Text 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 |
|
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. After 10 attempts (5 minutes) if 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. |