This readme file provides late-breaking or other information that supplements the RightFax documentation. Service packs are the means by which RightFax product updates are distributed from the Captaris Web site. A service pack may contain updates for system reliability, program compatibility, performance improvements, and more. All service packs are cumulative. Each contains new fixes plus all the fixes from previous hot fix and service pack releases.
This document describes the current update to this version of the RightFax server and fax board driver software. It provides installation instructions and a brief description of problems fixed with this release. Because Service Pack 3 is cumulative with Service Pack 2, a description of the changes in Service Pack 2 is included at the end of this document.
By the time you receive this software, updates to other RightFax software may be available. To obtain updates, go to http://www.captaris.com/customer_support.
This service pack should be installed on computers that are running version 8.7 of all types of RightFax server. Follow these steps to confirm that a computer has this version of the RightFax server installed.
From the computer desktop, select Start > Settings > Control Panel. If this computer is a RightFax server, the Control Panel includes an application called RightFax Server. If this application is not present, do not run the update program RightFax Server Update 8.70 SP3 Server Patch.exe on this computer.
Double-click RightFax Server. The Server Configuration dialog box opens. The server version number and any installed service packs are displayed in the title bar of this dialog box. If the version number is anything other than 8.7 (with or without earlier installed service packs), do not run the update program RightFax Server Update 8.70 SP3 Server Patch.exe on this computer.
This service pack should be installed on all version 8.7 RightFax servers on your network. If you are running any RightFax Web applications on IIS servers or the Exchange 2000 connector on Exchange servers that are separate from the RightFax server, this service pack must be installed on those computers as well.
To update your software, Microsoft Windows Installer patches your existing RightFax installation by replacing existing files with updated files and installing new files.
Important: Before running this installation, if you have one or more Brooktrout TR1034 fax boards installed, you must confirm that the file bos_btcall.cfg in the \RightFax\RFBoard folder is not set to read-only. If it is, remove the read-only attribute from this file prior to installing the service pack. Running the service pack installation with this file set to read-only will fail to properly update the file and the fax boards will not operate.
Log on to the RightFax 8.7 server as an administrator.
Run the program RightFax Product Suite Service Pack 3.exe located on your update CD or extracted from the downloaded .zip file.
At the introductory screen, click Update. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
After completing the service pack installation for the RightFax server, you must install the service pack for the fax board drivers (described in the next section) and the Web Client, if applicable.
IMPORTANT: If you have any Brooktrout series 1034 fax boards already installed, you must re-configure these boards after upgrading to Service Pack 3. In this case, Captaris recommends removing and then re-adding the 1034 boards in the BoardServer Control Panel application.
To update your software, Microsoft Windows Installer patches your existing RightFax installation by replacing existing files with updated files and installing new files. Follow these steps if your RightFax server has fax boards installed. If you use remote BoardServer computers, refer to the next section.
When the installation of Service Pack 3 for the RightFax Server is complete, remain logged on to the RightFax 8.7 server as an administrator.
Run the program RightFax Fax Board Driver Service Pack 3.exe that you extracted from the downloaded .zip file.
At the introductory screen, click Update. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
The installation program includes Brooktrout TR1034 fax board firmware. If you have one of these fax boards installed, the TR1034’s flash ROM will need to be updated after applying this feature pack. Follow the steps in the next section to update the TR1034's flash ROM.
Stop the RightFax BoardServer service.
If you did not
install RightFax to the default location on the C: drive, navigate to
the \RFBoard\Boston folder and edit the file flashupd.bat with a text
editor. Confirm that the "SET LOADER=" parameter has the correct
path to the file firm.exe. You must include both the path and file name
in this parameter. For example:
SET LOADER=\progra~1\rightfax\rfboard\firm.exe
This command supports short file names only, so you may need to truncate
folder names as in the example.
Open a command prompt window and change to the \RFBoard\Boston folder.
Run the following
command:
flashupd # [ENTER]
Where # is the fax board's module number. If you do not know the board's
module number, you can check by running this command:
Modinfo [ENTER]
The first 2 digits on the second line or output are the board's module
number. For example, if the board's module number is 2, "02:"
will be listed at the beginning of the second line.
Important: Do not interrupt the flash update process. Doing
so can permanently damage the fax board.
A successful flash will display "Done, result value 0" on
the last line. An unsuccessful flash will display "-1" on the
last line.
Repeat the flashupd command for each installed TR1034 fax board.
Restart the RightFax BoardServer service.
To confirm a proper flash update, run Enterprise Fax Manager and select the RightFax server name in the left pane. The ROM ID column should display "1.4.0 Build 38,38,38" for all fax channels not currently in use. When the RightFax BoardServer module running, the Board Status LED on each TR1034 board should be a slowly flashing green.
Remote BoardServer computers must be updated immediately after the RightFax server is updated. To update remote BoardServer computers, you must update both the server software and the fax board drivers according to the instructions above.
The RightFax Administrative Utilities are installed separately from other RightFax server and client components. Follow these steps to update the RightFax Administrative Utilities on all computers where they are already installed.
Log on to the computer with the RightFax Administrative Utilities installed.
Run the program RightFax Admin Utilities Service Pack 3.exe located on your update CD or extracted from the downloaded .zip file.
At the introductory screen, click Update. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
The RightFax Client Installs folder lets you store the RightFax client installation files on your network so that you can easily run all new RightFax client installations from that location. The installation files in this folder should be used for all new client installations. Existing clients should be upgraded by running the Service Pack 3 executable file directly on each client computer.
Follow these steps on the server where the version 8.7 RightFax Client Installs folder resides (described in the RightFax Installation Guide):
This update can only be run on the base-level 8.7 Client Install folder. If you have already updated the RightFax Client Install folder to version 8.7 Service Pack 2, you must delete the RightFax Client Install folder and re-copy the base-level 8.7 Client Install Folder from the RightFax 8.7 CD before upgrading to Service Pack 3. Refer to the RightFax Installation Guide for information on copying the RightFax Client Install folder from the RightFax CD.
Unzip RightFax Product Suite Service Pack 3.exe to a temporary location, e.g., the C:\temp folder.
Open a command prompt window and navigate to the existing RightFax Client Installs folder.
At the command prompt,
type:
"C:\temp\RightFax Product Suite Service Pack 3.exe " /V"/a
RightF~1.msi
Once the installer window is displayed, follow the on-screen prompts to update the client installs to service pack 3. If the installer fails to display or if you receive an error message, verify the path to the location where you installed the RightFax Product Suite Service Pack 3.exe file.
After the RightFax client installs folder on your network has been upgraded, it should be used for new client installations only. If you want to upgrade existing RightFax client installations, you should run the Service Pack 3 executable file directly on each client computer.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
39839 |
Alerting |
Fax channel monitoring reports error when last channel is selected. Monitors incorrect channels numbers. |
Fax channel monitoring correctly monitors fax channels. |
|
41470 |
BoardServer |
When analog TR1034 fax boards are in use, the BoardServer does not correctly process DTMF digits for routing. |
The BoardServer now processes DTMF digits for routing. |
|
41767 |
BoardServer |
The BoardServer module crashes if a dialing rule to disallow sending is listed after but matches the pattern of a previous rule. |
The described behavior no longer occurs. Dialing rules are executed as expected. |
|
42097 |
BoardServer |
The file Callctrl.cfg includes incorrect syntax for the num_rings parameter. |
This parameter has been corrected in Callctrl.cfg. |
|
43357 |
BoardServer |
Running the BoardServer module in debug mode through EFM pushes CPU usage to 100%. |
Debug error corrected. |
|
44160 |
BoardServer |
ECM setting for Brooktrout boards stays enabled even if disabled in the BoardServer configuration application. |
ECM setting now reads correct setting from the BoardServer configuration application as expected. |
|
40068 |
Brooktrout TR1034 |
When restarting a RightFax server installed on a Compaq machine (e.g. DL380 G3), running Compaq's Surveyor utility with Windows 2003 Server, and Brooktrout TR1034 fax boards installed, the server hangs. |
Hang on reboot problem resolved. |
|
41948 |
Brooktrout TR1034 |
TR1034 boards configured for PRI-E1 have the pcm_law parameter configured incorrectly. |
This parameter is now correctly configured as "alaw" instead of "mulaw." |
|
41951 |
Brooktrout TR1034 |
Deactivating one or more channels on the TR1034 (PRI) is not reflected correctly in callctrl.cfg. |
This value is now correctly written to Callctrl.cfg. |
|
42242 |
Brooktrout TR1034 |
TR1034 analog channels report as "Offline Permanently" when in the same machine as digital TR1034 boards configured as PRI-ISDN. |
TR1034 analog channels now function properly when in the same machine as digital TR1034 boards configured as PRI-ISDN. |
|
42841 |
Brooktrout TR1034 |
TR1034 will not dial more than 24 digits. |
Corrected. Unlimited dialing characters supported. |
|
44021 |
Brooktrout TR1034 |
TR1034 BRI boards fail to receive faxes via the Siemens HiPath PBX. |
TR1034 BRI boards now correctly receive faxes via the Siemens HiPath PBX. |
|
44089 |
Brooktrout TR1034 |
Frequent channel reset failures on inbound faxes when running one or more TR1034+P4-4L boards with RightFax 8.7 FP1 with IBM Series 235. |
Channel reset problem resolved. |
|
44220 |
Brooktrout TR1034 |
DTMF routing for a fax channel with the option "Initial Speech" set requires users to wait for the entire voice greeting to end before the system will accept entered digits. |
Routing digits can now be entered at any time during the voice prompt. |
|
44271 |
Brooktrout TR1034 |
Eccdlld.dll file not found error when running voice.exe for the TR1034 board. |
Voice.exe now finds eccdlld.dll as expected. |
|
37114 |
ChgUser.exe |
When running ChgUser.exe and the NONTSECURITY keyword is used in the command line, the "Stamp Pages of Received Faxes with Audit Stamp" option is enabled in the user record. |
The NONTSECURITY keyword in ChgUser.exe no longer automatically enables the "Stamp Pages of Received Faxes with Audit Stamp" option. |
|
41293 |
E-mail Gateways |
After a Satellite Server is bumped, the cc:Mail, MS Mail, Groupwise, and SMTP E-mail Gateways are unavailable for install. |
Bumping a Satellite Server now makes these e-mail Gateways available. |
|
42833 |
Embedded Codes |
After upgrading from RightFax 7.2 to RightFax 8.7, some embedded codes (such as NEWDEST) inappropriately generate a fax cover sheet. |
Embedded codes no longer inappropriately generate fax cover sheets. |
|
42217 |
Enterprise Fax Manager |
Selecting the option "Disallow Fax Annotation" also disables the ability to print, forward, route, and more. |
Selecting the option "Disallow Fax Annotation" no longer affects other user permissions. |
|
35668 |
Exchange Gateway |
The option to "Break up Large Faxes" sends faxes above the specified page limit. |
The option to "Break up Large Faxes" now correctly sends faxes at the specified page limit. |
|
42103 |
Exchange Connector |
Faxes routed to e-mail via the Exchange connector use full path to the attachment for the file name, which made the file unreadable by certain devices. |
Faxes routed to e-mail via the Exchange connector no longer include the full path in the file name. |
|
44119 |
Exchange Connector |
Exchange 5.5 displays warnings for every processed fax if you have Message Tracking enabled on the connector. |
Problem fixed. Warning messages no longer appear. |
|
44963 |
Exchange Connector |
Microsoft Exchange System Manager crashes when adding a user that is not in the Users container on the Delivery Restrictions tab. |
This action no longer crashes Microsoft Exchange System Manager. |
|
41685 |
Fax Control |
Print-to-Fax on a file with a long file name (150 characters or higher) fails. |
Print-to-Fax on files with long file names (150 characters or higher) work as expected. |
|
41973 |
Fax Control |
JPEG files converted to fax format appear small and compressed. |
JPEG files now convert to fax format as expected. |
|
45057 |
Fax Control |
When using the Quick Fax/Broadcast feature, users can change phonebook entries even when not assigned this permission. |
Quick Fax/Broadcast feature now correctly blocks users from changing phonebook entries if they are not assigned this permission. |
|
30461 |
Fax Reporter |
In Fax Reporter, the Folder column in the Faxes table is not populated correctly. |
Folder column in the Faxes table now reports folder names as expected. |
|
31869 |
Fax Reporter |
FaxReporter misreports scheduled send time in the FaxSendDateTime column if a fax was delayed. |
Delayed faxes now correctly report the scheduled send time in the FaxSendDateTime column. |
|
42209/ |
Fax Reporter |
Fax Reporter data does not refresh if the network protocol is set to TCP/IP and then changed to either Named Pipes or Automatic Selection. |
Fax Reporter data now correctly refreshes if network protocol setting is changed. |
|
41543 |
Fax Server |
"Fax not viewed or printed" notifications are always sent to the Group Administrator when users route faxes to an E-mail Gateway, even if option for no notifications is selected. |
The option for to disable notifications to the Group Administrator now works as expected. |
|
44243 |
Fax Server |
Applying Tracks patch 40069 causes files to be routed in 8.3.3 file format instead of an 8.3 format. |
Applying Tracks patch 40069 now correctly causes files to be routed in 8.3 format. |
|
42494 |
Fax Status |
Fax Status application crashes when viewing the status of a fax channel transmitting at V.34. |
Fax Status application no longer fails when viewing v.34 transmissions. |
|
41673 |
FaxUtil |
Odd-sized tiff images, when sent as file attachments, fail to convert. |
Attached tiff images convert as expected. |
|
41682 |
FaxUtil |
FaxUtil will not run if no RightFax server name was specified during client installation. |
Leaving the RightFax server name blank during installation no longer causes FaxUtil to fail. |
|
41742 |
FaxUtil |
After closing the Phonebook window, faxes appear to lose their corresponding filter information (sent/received, to/from/file, etc.). Deleting one of these faxes causes FaxUtil to appear to perpetually delete faxes. |
The described behavior no longer occurs and deleting faxes works as expected. |
|
41822 |
FaxUtil |
FaxUtil folders default to the order they were created, even if alphabetical order is specified. |
FaxUtil folders now correctly display in alphabetical order. |
|
41890 |
FaxUtil |
FaxUtil lists the same fax repeatedly after opening the Fax Viewer, forwarding to new number, and then using the phonebook to select a recipient. |
Corrected so that no duplicate fax entry is displayed. |
|
43987 |
FaxUtil |
FaxUtil lists the same fax repeatedly after opening the Fax Viewer, forwarding to new number, and then using the phonebook to select a recipient. |
Corrected so that no duplicate fax entry is displayed. |
|
44707 |
FaxUtil |
Faxes that are in the "Needs Approval" status will not go back to that status after printing. Status stays as "Printing" indefinitely. |
After printing a fax in the "Needs Approval" state, fax returns from status "Printing" to status "Needs Approval." |
|
44833 |
FaxUtil |
Attached text files that contain tab characters do not word wrap correctly on conversion to fax format. |
You can now customize the maximum number
of characters per line. Navigate to the registry key HKEY_LOCAL_MACHINE |
|
45841 |
FaxUtil |
When attempting to send a fax to an Outlook 2003 MAPI phonebook contact, FaxUtil generates a Dr. Watson error. Occurs only when an Outlook 2003 client has "Use cached exchange mode" enabled. |
Error no longer occurs. |
|
43661 |
FileNet Connector |
The connector fails to process jobs from multiple source servers. |
The connector now supports job processing from multiple servers as expected. |
|
41854 |
Human-Answered Fax |
Selecting the option "Always start each call in voice mode" causes the fax board to automatically hang up after 12 seconds on outbound calls. |
Selecting the option "Always start each call in voice mode" no longer causes the fax board to automatically hang up. |
|
42503 |
Human-Answered Fax |
The Human-Answered Fax feature, using TR1034 analog boards with the "Always start" option enabled, reports status "OK" when dialing times out without an answer. |
Faxes now correctly report status "No answer at fax number." |
|
42534 |
Human-Answered Fax |
The Human-Answered Fax feature, using TR1034 analog boards with the "Always start" option enabled, reports status "OK" when a busy signal is encountered. |
Faxes now correctly report status "Busy." |
|
32530 |
ImpUser.exe |
The last entry in a .csv file fails to import unless a carriage return follows. |
Fixed so that carriage return is no longer required. |
|
33203 |
ImpUser.exe |
All users exported from RightFax and re-imported using ImpUser .exe have "Delete After Routing" option enabled. |
ImpUser.exe now correctly retains "Delete After Routing" setting. |
|
41750 |
Mimesend |
Mimesend fails to send to all recipients if any single recipient in a particular group has a bad e-mail address. |
Mimesend now ignores only the bad e-mail addresses and sends to all others as expected. |
|
41611 |
Notes Gateway |
Under certain circumstances, user synchronization between Notes and RightFax was incorrectly synching changes to Notes users with the RightFax server when synchronization was specifically set to only flow from RightFax to Notes. |
Corrected directional synchronization error. |
|
37666 |
ODBCSync.exe |
When synching a new user into a group whose name contains a space, the new user is not created in RightFax. |
RightFax now correctly reformats the group name, replacing spaces with underscore characters, and adds the user to the new group. |
|
39682 |
ODBCSync.exe |
When synching a new user whose name contains a space, the new user created with an underscore replacing the space as expected, but re-running ODBCSync.exe will generate arror and fail to update these users. |
Importing user names with spaces no longer generates error and updates as expected. |
|
40310 |
ODBCSync.exe |
RightFax IDs that have been created with ODBCSync.exe and had a source ID more than 21 characters long fail to update when re-running ODBCSync.exe. |
Importing user names with more than 21 characters no longer generates error and updates as expected. |
|
41814 |
Outlook Advanced Form |
The "Delay Send" option on the Outlook Advanced form shows the Date field twice instead of Date and Time. |
The "Delay Send" option on the Outlook Advanced form now correctly shows Date and Time fields. |
|
43610 |
Outlook Advanced Form |
Some faxes appear blank when viewed with the Outlook Advanced Form with Outlook 2003. |
All faxes now display as expected. |
|
43913 |
Outlook Advanced Form |
Outlook 2003 terminates unexpectedly when opened minimized and custom user variables exist with Outlook Extensions installed. |
Outlook 2003 no longer terminates when minimized and then closed. |
|
45705 |
Outlook Advanced Form |
Outlook hangs when receiving a fax in Outlook with McAfee 8.0i enterprise installed. |
Outlook no longer hangs on receiving a fax. |
|
31969 |
|
PostScript documents that contain the PostScript command "setpagedevice" fail conversion to fax format for transmission. |
The PostScript command "setpagedevice" is now processed correctly and does not cause fax conversion failure. |
|
41573 |
|
Adobe 6 PDF images acquired using TWAIN scanners shrink to 1/3 original size. |
Adobe 6 images now attach at full size. |
|
41676 |
|
Compressed PDF file fails conversion. |
Compressed PDF files convert as expected. Requires SSA NativeDocControl PDF,2 for WorkServer. |
|
42263 |
|
PDFs with embedded Asian fonts convert incorrectly to fax format. |
Asian fonts now convert to fax format as expected. |
|
42693 |
|
The -d switch for Pssplit.exe does not cause debug information to write to the screen or event viewer. |
The -d switch for Pssplit.exe now correctly outputs debug information. |
|
43227 |
|
Converting a document that contains a barcode font to PDF using NativeDocControl fails to properly convert the barcode. |
Corrected. The font is properly converted when corresponding .TTF file is located in the Worksrv\Fonts folder. |
|
43377 |
|
PDF images generated on the HP4100 have stripes running through the image. |
Problem corrected. PDF images convert as expected. |
|
44108 |
|
PDFs created from documents with graphic images in the header or footer convert with poor image quality. |
Graphic conversion corrected to retain image quality. |
|
34653 |
PhnPrint.exe |
PhnPrint.exe commands that specify multiple users but only supply some of the users' passwords outputs data as though no passwords had been supplied. |
PhnPrint.exe now recognizes a partial list of passwords and outputs data accordingly. |
|
42555 |
PhnPrint.exe |
Level 2 output for PhnPrint.exe does not output all expected data fields. |
Level 2 output for PhnPrint.exe corrected so that it now outputs all expected data fields. |
|
35199 |
Production |
The Mailsend.exe -o switch converts all recipient e-mail address to ASCII, causing mail transmission failure. |
Mailsend.exe -o switch preserves recipient e-mail addresses correctly and mail transmits as expected. |
|
37199 |
Production |
Bumping a Business Server with the Integration Module enables no production fax channels. |
The production fax channels are now correctly enabled when a Business Server with Integration is bumped. |
|
41396 |
Production |
MapText.exe image preview does not work. |
MapText.exe image preview works as expected. |
|
42954 |
Production |
When PORTLSTN.exe is enabled in the Integration Module control panel application, a Dr. Watson error is reported when the Integration Module service is stopped. |
Corrected issue. Dr. Watson error no longer occurs. |
|
43168 |
Production |
Running NOTIFY.exe to add a new integration channel causes a Dr. Watson error when the Integration Module service is stopped. |
Corrected issue. Dr. Watson error no longer occurs. |
|
34724 |
Rescue.exe |
Running Rescue.exe causes all faxes that are currently waiting for transmission because a delay time was specified to fail to send. |
Rescue.exe now correctly preserves delayed faxes. Delayed faxes transmit at the specified time as expected. |
|
41840 |
SAP |
The ProgID parameter in the saprfc.ini file is always reset to servername.sapgate when closing configuration. |
The ProgID parameter now retains its correct setting when closing configuration. |
|
41894 |
SAP |
All faxes sent via SAPOffice are sent as high priority. |
Faxes sent via SAPOffice now send with normal priority unless otherwise specified. |
|
44203 |
SAP |
SAPGate strips out data beginning with "<who". |
SAP no longer strips invalid SAP embedded code text. |
|
44227 |
SAP |
If you add DefaultUserID as a Reg_SZ value to HKLM\Software\RightFax\SAP\SAP#\ and send a fax through that SAP Gateway, it will not send from the user specified in that key, but will send using the Default user ID instead. |
Registry setting now correctly read by SAP connector. |
|
12459 |
SecureDocs |
Non-US regional settings cause an inability to log in to SecureDocs . |
Corrected date formatting to allow login with non-US regional settings. |
|
43116 |
SecureDocs |
Under certain circumstances, user administration through SecureDocs fails. |
Corrected error so that user administration works as expected. |
|
41270 |
SMTP Gateway |
Submitting an e-mail to the SMTP Gateway that has embedded HTML in the body with embedded images causes the Gateway to stop unexpectedly. |
The SMTP Gateway now correctly processes HTML-referenced images. |
|
42990 |
SMTP Gateway |
A fax with an attachment that is sent through the SMTP Gateway and fails conversion is incorrectly deleted from FaxUtil. |
The behavior in this circumstance is now configurable in the registry. To retain these faxes in FaxUtil with a "failed" status, navigate to the registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Faxserver and set AutoDeleteFailedGatewayFaxes to 0. To retain the functionality as described, set AutoDeleteFailedGatewayFaxes to 1. |
|
43282 |
SMTP Gateway |
Fax conversion error notifications are returned to the sender via e-mail, even if all notification options are disabled. |
This behavior is now configurable in the registry. To disable these notifications, navigate to the registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Faxserver, add a new DWORD registry called NoGatewayNotify, and set the data for this new value to 1. |
|
46915 |
Standalone Fax Connector |
Standalone Fax Connector does not work with TR1034 analog boards. |
Connector now dials out as expected. |
|
40288 |
Web Client |
Attaching notes in Web Client loses all characters after 80 if manual carriage returns are not entered. |
You can now customize the maximum number
of characters per line. Navigate to the registry key HKEY_LOCAL_MACHINE |
|
35216 |
WorkServer |
WorkServer archiving of outbound documents fails when sending to an e-mail address. |
Faxes sent to e-mail addresses are now archived as expected. |
|
41911 |
WorkServer |
Autoprinting inbound faxes to an HP LaserJet 4si prints only a single black line. |
HP LaserJet 4si printers now autoprint correctly. |
|
43699 |
WorkServer |
Conversion of some JPEG images results in poor image quality, especially when converting colors to grayscale. |
You can now customize the threshold setting when converting JPEG images to grayscale. Navigate to the registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Workserver, add a new DWORD registry called RFThresh, and set the data for this new value to an appropriate setting from 3-255. The default value used is 128. Increase this value to darken color images. To change the registry value, stop all WorkServers, change the registry value on the server, then restart the WorkServers. |
|
44398 |
WorkServer |
WorkServer fails to create TIFF-G4 for certain received faxes when routing to network directory. |
Problem corrected. TIFF-G4 created as expected. |
The additions and corrections listed here apply only to the 8.7 version of the RightFax documentation.
|
Chapter |
Various |
||
|
Section |
Various |
||
|
Page |
Various |
||
|
Error |
Documentation does not state that the <SIGNATURE> embedded code is unsupported in outbound PDF documents. |
||
|
Resolution |
Please note that the <SIGNATURE> embedded code is not supported in outbound PDF documents. |
||
|
Chapter |
6, "Enabling Active Directory User Synchronization" |
||
|
Section |
"Configuring the RightFax WorkServers to Perform User Synchronization" |
||
|
Page |
103 |
||
|
Error |
Information about the WorkServer's service account is omitted, which may cause automatic Active Directory user updates to fail. |
||
|
Resolution |
The WorkServer service account must reside in the domain with which it is synchronizing so that updates to Active Directory user IDs are reflected on corresponding RightFax IDs after the initial synchronization has occurred. |
||
|
Chapter |
9, "Creating Groups of Users" |
||
|
Section |
"Editing Group Properties" |
||
|
Page |
155 |
||
|
Error |
The definition for the option Days to keep deleted fax records on the Group Edit dialog box Basic Information tab is misleading. |
||
|
Resolution |
The documentation implies that fax records will be retained in the database for the number of days specified in the Days to keep deleted fax records option after the fax image is deleted. In fact, the fax records will be retained in the database for this number of days after the fax is received. You should set the Days to keep deleted fax records value based on the received date rather than the delete date. If you have set users' faxes to be automatically deleted after 30 days, and want the fax records purged 30 days later, then set the Days to keep deleted fax records to 60 days. |
||
|
Chapter |
4, "Installing the RightFax Client Applications" |
||
|
Section |
"MAPI Print Driver," "VIM Print Driver" |
||
|
Page |
43 |
||
|
Error |
Documentation fails to mention that VIM and MAPI printing are not supported under Windows 2003 Terminal Server. |
||
|
Resolution |
Please note that VIM and MAPI printing are not supported under Windows 2003 Terminal Server. |
||
This document provides late-breaking or other information that supplements the RightFax documentation. Service packs are the means by which RightFax product updates are distributed from the Captaris Web site. A service pack may contain updates for system reliability, program compatibility, performance improvements, and more. All service packs are cumulative. Each contains new fixes plus all the fixes from previous hot fix and service pack releases.
This document describes the current update to this version of the RightFax server and fax board driver software. It provides installation instructions and a brief description of problems fixed with this release.
By the time you receive this software, updates to other RightFax software may be available. To obtain updates, go to http://www.captaris.com/customer_support.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
39669 |
Alerting |
An alert condition fails to send email. |
Now an alert condition sends email successfully. |
|
39522 |
BoardServer |
Making changes to the BoardServer configuration can add multiple instances of Boston/BFax to the RFBOARD DependOnService registry value. |
Making changes to the BoardServer configuration no longer adds multiple instances of Boston/BFax to the RFBOARD DependOnService registry value. |
|
39968 |
BoardServer |
All failed phone calls become failed faxes in PRI-E1 on TR1034. |
Failed phone calls no longer report incorrectly as failed faxes in PRI-E1 on TR1034 boards. |
|
39977 |
BoardServer |
Selecting the "Enable Overlap Receive" option in DCW for 1034-E1 board does not stick. |
The "Enable Overlap Receive" option in the Digital Configuration Wizard for 1034-E1 fax boards now properly retains its value. |
|
39996 |
BoardServer |
Atempting to open the BoardServer control panel applet results in "GetBump" errors. |
Opening the BoardServer application no longer gives "GetBump" errors. |
|
39757 |
FaxUtil |
Install of RightFax 8.7 client after installing Paperport Pro version 9 Office on XP Professional machine fails. |
First install RightFax 8.7 client and then install Paperport Pro 9. If Paperport Pro 9 is already installed, manually uninstall it, install RightFax 8.7 client, and then reinstall Paperport Pro 9 and the scanner driver. |
|
39465 |
Database/Server |
RightFax Server and Database modules fail to start in debug mode at the command prompt. |
Now RightFax Server and Database modules can run in debug mode at the command prompt. |
|
39523 |
EDC Configuration |
Cannot download Xerox 8.7 templates to WorkCenter 55. |
Now can download the Xerox 8.7 templates. |
|
42346 |
EDC Configuration |
Using Xerox 8.7, sending a fax from WalkupFax, SecureDocs, or Certified Delivery templates, ensuring you populate the ReplyTo field, the sender is not notified of the job status. |
Now when the Reply To field is used, the sender is notified of the job status. |
|
36940 |
EDC |
After sending a fax, get a Job Failure notice in RFSendStatus. FaxUtil shows it sending with no sender and no recipient. It does eventually send, although no RightFax server receives it. |
Now it processes the fax and the monitor does not indicate a job failure. |
|
40037 |
Exchange Connector |
Exchange 2003 stops the RightFax Connector from processing if too many messages are sent. |
A registry value is available to enable the initiation of a new MAPI session every time the Exchange server processes 100 messages.
Note: May need to manually create the Gateway subkey. |
|
38796 |
Exchange Gateway |
When manually address a fax from Outlook that contains a plus sign (+) as the first character in the fax number, the exchange gateway strips the entire number. |
Now the exchange gateway does not attempt to strip the plus sign, and the fax can be sent manually from Outlook. |
|
39683 |
Fax Server |
Error encountered, fax will be abandoned notifications are sending During transmission messages. |
Now Error encountered, fax will be abandoned notifications use the correct text. |
|
39695 |
Fax Server |
Automatically forwarding a fax generates a false error message in the event viewer. |
Now automatically forwarding a fax does not generate a false error message in the event viewer. |
|
39947 |
Fax Server |
Transmission error faxes received by users that route to the Exchange gateway are scheduled to be sent. |
Now received faxes are not scheduled to be sent. |
|
41330 |
Fax Server |
Having the Admin ONCE Only option disabled and Admin Notify Time set to zero results in many group administrator notifications of faxes not viewed or printed. |
Having the Admin ONCE Only option disabled and Admin Notify Time set to zero disables all group administrator notifications of faxes not viewed or printed. |
|
40407 |
Fax Viewer |
When using the CTRL key and the Up or Down arrow in the Rightfax Viewer, the Viewer does not scroll from fax to fax. |
Now can view the next fax and previous fax when using the CTRL key and the Up or Down arrow in the RightFax Viewer. |
|
40246 |
Installation |
An incorrect fax.exe is installed in the \RFBoard\Boston\ folder. |
The correct version of fax.exe is now installed in the \RFBoard\Boston folder for fax board testing. |
|
39983 |
Notes Client
|
Using French EFM Sync and creating a new default user with PRESONNE_ PAR_DEFAUT ID, cannot synchronize user into RightFax server. |
Now the localized EFM Sync does not translate system variables; DEFAULT remains default and synchronization works.
|
|
39999 |
Notes Client |
Notes users can not select the Forward button in the Notes mail template to forward messages in the Inbox to other Notes users. The error "Cannot locate Default Form" is displayed. |
For version 8.7 there is a workaround for this problem. Refer to TechNote #11528 on the Captaris Web site for instructions. |
|
39985 |
Notes Gateway |
Using French EFM Sync, creating a new default user with PRESONNE_ PAR_DEFAUT ID, and sending a fax from a user that is not an EFM Sync user, fax fails to send. |
Now the translation is handled appropriately and faxes can be sent. |
|
39788 |
Production Server |
When sending a Fax Control Language document and checking Do Not Delete Input Files, a fax is not created. |
Now a fax is created and the input file is not deleted.Note: This creates a subfolder in the monitored folder (usually the Inbox) called Archive into which processed faxes are placed. |
|
39790 |
Production Server |
Registry entries are removed when saving settings in the Integration Module Configuration GUI. |
The new control panel contains a "Download image as TIFF" checkbox that can be set. |
|
39950 |
Production Server |
The parser crashes if it receives an email document with more than 135 lines of body text. |
The parser no longer crashes with more than 135 lines of body text. |
|
37356 |
SMTP Integration |
The SMTP Gateway crashes when attempting to route a fax if communication with the SMTP server is lost. |
Now the SMTP Gateway continues attempting to process faxes. |
|
37780 |
SSA |
When using Office XP for SSA, sending Word cover sheets and/or documents in high volume can cause the WorkServer to crash. |
Now the WorkServer does not crash. |
|
40046 |
SSA |
When using SSA to convert Excel documents, instances of Excel.exe continually spawn and remain open. |
Now instances of Excel.exe spawn and close after conversion. |
|
34585 |
WorkServer |
PCL files created with Macro4 convert with what appears to be all 5 pages overlayed on one page. |
PCL files created with Macro4 now convert successfully when sent as attachments. |
|
38828 |
WorkServer |
Active directory synchronization fails if the permission to read an object or Organization Unit is removed from the Everyone group. |
Now Active Directory synchronization does not fail in this situation. |
|
39517 |
WorkServer |
Automatically printing only the history on sent faxes fails using Windows GDI printers. |
Now the history prints successfully. |
|
39873 |
WorkServer |
In certain circumstances, workservers loop on conversion when trying to use SSA, but the native document application is either not installed or could not be loaded, creating very large temporary files. |
Large temporary files are no longer created. |
|
40069 |
WorkServer |
Routing a fax to a network directory does not work when using PCX or DCX as the file format. |
Now correctly creates PCX or DCX files in the target directory. |
|
40405 |
WorkServer |
Images acquired through TWAIN scanners, e.g., BMP files, experience excessive shrinkage. |
Now scanned documents experience very little or no shrinkage of their size. |
|
41300 |
WorkServer |
PCX file attachments fail conversion. |
Now the fax converts successfully. |
The additions and corrections listed here apply only to the 8.7 version of the RightFax documentation.
|
Chapter |
3, "Installing the RightFax Connector for Microsoft Exchange 2000 and 2003" |
||
|
Section |
"Changing the mail directory paths" |
||
|
Page |
30 |
||
|
Error |
A step is missing from this procedure. |
||
|
Resolution |
Add this step after step 4: "For the second node only, remove the FAX* and RFAX* namespace." |
||
|
Chapter |
5, "Configuring Outlook Users to Send and Receive Faxes" |
||
|
Section |
"Configuring Outlook Users to Send and Receive Faxes" |
||
|
Page |
39 |
||
|
Error |
Right-click options are incorrect. |
||
|
Resolution |
The options listed in the guide are View, Delete, and Release a fax held for preview. Options should read "Refresh, View, and Delete." |
||
|
Chapter |
3, "Configuring the RightFax Server Module" |
||
|
Section |
"Installing the RightFax Server Software" |
||
|
Page |
31 |
||
|
Error |
The location of the Administrative Utilities installation is incorrect. |
||
|
Resolution |
The correct location is Support\Admin Utilities\Setup.exe. |
||
|
Appendix |
A, "Installing RightFax in a Windows 2000 or Windows 2003 Cluster" |
||
|
Section |
"Configuring the shared drive" |
||
|
Page |
56 |
||
|
Error |
The location for the Setup.ini file is incorrect. |
||
|
Resolution |
The instructions should read "Using a text editor, edit the file Setup.ini located in the folder where you placed the RightFax client installation files (described in the RightFax Installation Guide). By default, this is installed in C:\RightFax Clients. Change the RFSERVERNAME value to the name of the cluster. |
||
|
Appendix |
B, FCL Commands" |
||
|
Section |
"{{ATTACH}}" |
||
|
Page |
250 |
||
|
Error |
The guide does not mention that the {{type email}} command can not be used in combination with the {{attach}} command. |
||
|
Resolution |
The {{type email}} command can not be used in combination with the {{attach}} command. |
||
|
Chapter |
N/A |
||
|
Section |
N/A |
||
|
Page |
N/A |
||
|
Error |
Notes users can not select the Forward button in the Notes mail template to forward messages in the Inbox to other Notes users. The error "Cannot locate Default Form" is displayed. |
||
|
Resolution |
For version 8.7 there is a workaround for this problem. Refer to TechNote #11528 on the Captaris Web site for instructions. |
||
Service Pack 2 for RightFax version 8.7 includes support for the following Brooktrout fax boards:
TR1034+P2-2L (Two-port analog loop-start board)
TR1034+P4-4L (Two-port analog loop-start board)
TR1034+P8-8L (Eight-port analog loop-start board)
TR1034+P2-1B (Two-port BRI board)
TR1034+P4-2B (Four-port BRI board)
TruFax 200 BRI (Two-port BRI board reduced feature set variant of the TR1034 BRI board)
TruFax 400 BRI (Four-port BRI board reduced feature set variant of the TR1034 BRI board)
After Service Pack 2 has been installed, these fax boards may be added and configured in the RightFax BoardServer application in Windows Control Panel. For information on running the RightFax BoardServer application, refer to the RightFax Administrator's Guide.
Before installing any of the new fax boards into the server chassis, you must assign each board a unique "module number." The module number is set using a rotary switch located on the fax board. Refer to your Brooktrout documentation for the location of the rotary switch on your particular fax board model.
Warning: Do not use a pencil or any other object that conducts electricity to move the rotary switch on Brooktrout fax boards. Using graphite and other electrically conductive materials may cause severe damage to the board.
The module number must be unique for each fax board you are installing in a single computer (i.e., you cannot have two fax boards in the same computer with the same module number setting). Module numbers do not need to be sequential. Also, do not set the module number on any Brooktrout fax board to 0 or 1 (these values are reserved by Brooktrout for diagnostic purposes.) Make a note of the module numbers you assign to each installed fax board. You will need to enter this information when configuring the RightFax software to communicate with the boards.
After the module numbers have been set on each fax board, you should install them into the server chassis.
After the fax boards have been installed in the server, you must configure the boards for use with RightFax.
IMPORTANT: If you have any Brooktrout series 1034 fax boards already installed, you must reconfigure these boards after upgrading to Feature Pack 1. In this case, Captaris recommends removing and then re-adding the 1034 boards in the BoardServer Control Panel application.
If, for any reason, server-side application conversion fails, you can configure RightFax to automatically timeout, stop the conversion, and set the fax status to conversion failed.
On the RightFax server, stop all WorkServer services.
Edit the Windows Registry on the RightFax server.
For each WorkServer number (\Worksrv#) add a REG_DWORD value called KillServiceTimeout to HKEY_LOCAL_MACHINE\Software\RightFax\Workserver\Worksrv# and set the data value to the length of time you want server-side application conversion to attempt conversion before timing out, in milliseconds (i.e., set the data value to 600000 for 10 minutes).
Restart the services.
To have the WorkServers recover after being stopped by this new feature, open the Windows Control Panel and select Administrative Tools > Services > RightFax WorkServer and go to the Recovery tab to select the service's response to the shutdown.
©2005 Captaris. All rights reserved.