This readme file provides late-breaking or other information that supplements the RightFax documentation. Hotfixes are the means by which RightFax product updates are distributed from the Captaris Web site. A Hotfix may contain updates for system reliability, program compatibility, performance improvements, and more. All Hotfixes are cumulative. Each contains new fixes plus all the fixes from previous Hotfixes.
By the time you receive this software, updates to other RightFax software may be available. To obtain updates, go to http://www.captaris.com/support/downloads/rightfax/9/index.html.
IMPORTANT: Before installing any hotfix or upgrading a RightFax server, you must back up the entire \RightFax directory structure, the fax board directory (usually the \RFBoard folder), and the SQL database for RightFax. To ensure that all necessary files are properly backed up, stop all RightFax services and close all RightFax applications before beginning the backup process.
Updating Microsoft Exchange Integrations
Hotfix 3 for RightFax version 9.0 SP2 contains numerous updates to the core server components, fax board drivers, and RightFax clients. Hotfix 3 also includes updates to the RightFax administrative utilities, Lotus Notes integration, and Exchange integration. See a complete list of updates here.
WARNING: Applying Hotfix 3 will overwrite all files associated with the Hotfix, regardless of the dates and version numbers of those same files already installed on your server. Verify a functional backup before continuing.
IMPORTANT: Before applying this update, the RightFax 9.0 server, RightFax Client Install folder, and existing client installs must have service pack 2 applied. Service pack two can be downloaded here.
From any computer on your network, download RightFax9sp2_HotFix3.zip from http://www.captaris.com/support/downloads/rightfax/9/index.html
Extract the contents of RightFax9sp2_HotFix3.zip to any folder accessible by the RightFax associated servers. A common practice is to create a temporary folder on the RightFax server to house the Hotfix files (e.g., C:\rfhotfix3).
RightFax Clients: Updates clients and client installation sources
GAC_GlobalAssemblyCache\Assemblies: Updates the Windows assembly files on all RightFax associated servers
MS Exchange: Updates Exchange integrations
RightFax: Updates the core RightFax components
Script Updates: SQL scripts used to update the RightFax database
IMPORTANT: Before applying this update, 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 applying the Hotfix . Running the service pack installation with this file set to read-only will fail to properly update the file and in the process will render the fax boards inoperable.
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.
Stop all RightFax services.
Close all RightFax applications.
Using Windows Explorer, open the folder containing the Hotfix 3 files.
In the Hotfix 3 folder, right-click the RightFax folder and choose Copy.
Using Windows Explorer, browse to the RightFax installation folder (e.g., C:\Program Files\RightFax).
Right-click one folder above the RightFax installation folder and choose Paste followed by Yes to All when prompted with the 'Confirm Folder Replace' message. If you did not receive the 'Confirm Folder Replace' message, you have pasted the new RightFax folder to an incorrect location. In the example of C:\Program Files\RightFax, you would paste the new RightFax folder into the 'C:\Program files' folder.
Log on to the RightFax server as an administrator.
Open the Windows Control Panel > Add/Remove Programs
Choose Add/Remove Windows Components and select Message Queuing Services.
For the MSMQ type, select only Message Queuing Server. On the following screen, select Message Queuing will not access a directory service.
Complete the installation.
Log on to the RightFax server as an administrator.
Open the Windows Control Panel > Add/Remove Programs.
Choose Add/Remove Windows Components.
Select Application Server > Details and check Message Queuing.
Complete the installation.
Open the \RightFax\Worksrv folder.
Rename the file worksrv.iso to worksrv.exe.
In the Hotfix 3 folder, double-click the UpdateRegistry.bat file. If you have installed RightFax to a location other than C:\Program Files\RightFax, you must edit the RightFax_Hotfix.reg file to include the correct installation folder.
Right-click the RightFax_Hotfix.reg file and choose Edit.
Look for the entry "RFControlPanelHost"="C:\\Program Files\\RightFax\\Shared Files\\RFControlPanelHost.cpl".
Replace C:\\Program Files\ \ with the folder you have installed RightFax to, e.g., D:\\RightFax. Save and close the RightFax_Hotfix.reg file.
Double-click the UpdateRegistry.bat file. Skip steps 8-12 if you have applied a previous 9.0 Hotfix.
Use Notepad to open the RightFax Remoting service configuration file. Typically, "C:\ProgramFiles\RightFax\Bin\Captaris.RightFax.RemotingService.exe.config.
In the configuration file, look for the line: <add key="SqlConnectionString" value="user id=sa;datasource=ServerName;initial catalog=RightFax;password=password" />
Copy the portion of the line inside the double-quotes following "value=". Do not include the double quotes.
Use RegEdit to create the key: HKEY_LOCAL_MACHINE\SOFTWARE\RightFax\Remoting. Create a new string value named sqlConnectionString and set its value by pasting what was copied from Notepad.
Close the registry.
Open a command prompt and change to the RightFax\CapaSync folder (where \RightFax is the local RightFax installation folder).
At the command prompt type, "Capasync.exe /Install" and hit enter. When prompted, enter the service account and password. This can be the same account and password used to run the RightFax WorkServers.
At the command prompt, change to the RightFax\ISOConv folder (where \RightFax is the local RightFax installation folder).
At the \RightFax\ISOConv command prompt type, "RFIsoconv.exe /Install" and hit enter. When prompted, enter the service account and password. This can be the same account and password used to run the RightFax WorkServers.
Use RegEdit to browse to the subkey HKLM\Software\Rightfax\Boardserver\.
Create a new REG_SZ value called CallXpressChannels
Edit this new value and enter the value data to contain all CallXpress channels in the string. This value can be a single value or a comma delimited list of channels. .
Close the registry
Download the GUI-based Fax Diagnostic Test for Windows
(for driver v4.9 only) from the Cantata (formerly Brooktrout) web site: http://www.cantata.com/support/productinfo.cfm?frmProduct=TR1034&frmCategory=Download
Copy
the FaxVoiceDiag_forDriver_v4.9.exe into a temporary directory and run the
executable. This will unzip the files into the current directory.
Open the FAXVOICEDIAG.HLP file and click on Quick Start. Follow the directions to confirm the board is working correctly. Close the Brooktrout test utility when complete.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Open the folder named GAC_GlobalAssemblyCache\Assemblies. This folder should possess 12 .dll files and five .config files.
Open a second instance of Windows Explorer and browse to the <system root>\Assembly folder (e.g., C:\Windows\Assembly).
Position the 2 Windows Explorer windows so that they are both viewable on screen. All other windows should be closed or minimized.
In the GAC_GlobalAssemblyCache\Assemblies folder, sort the files by Type. This can be done by right-clicking any open area within the GAC_GlobalAssemblyCache\Assemblies folder and choosing Arrange Icons By > Type. All files should now be grouped by their corresponding extension.
In the GAC_GlobalAssemblyCache\Assemblies folder, use your mouse to select the 12 .dll files. Do not select the .config files.
With these files selected, click and hold your right mouse button and drag the 12 .dll files to the <system root>\Assembly folder located in the second Explorer instance. You will not receive a prompt to replace the existing assembly files, however, the Hotfix 3 files will be copied into the <system root>\Assembly folder.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Open the folder named Script Updates. This folder should possess the file UpdateScripts.bat and a folder SQL_scripts.
Right-click the UpdateScripts.bat file and choose Edit.
Scroll to the end of the file and look for the entry %%f in (SQL_scripts\*.sql) DO osql -D RightFax -i %%f
Edit this line to contain switches that are relevant to your environment. Do be aware that a login switch(s) must be entered in conjunction with this command (see examples below). It is also important to note that these examples show the default database name (RightFax). If you have changed your database name from 'RightFax', you must edit this line to include your database name. A complete list of switches is provided in the UpdateScripts.bat file.
Save the UpdateScripts.bat file after making the necessary changes.
Open a command prompt and change to the \Script Updates folder (e.g., C:\rfhotfix1\Script Updates).
At the command prompt, type UpdateScripts.bat and hit Enter on your keyboard. This will execute the provided SQL script according to the previously entered parameters. Alternatively you can browse to the \Script Updates folder and double-click the UpdateScripts.bat file.
Once completed, bring the RightFax services back on-line. This completes the RightFax server Update.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Copy the folder named Script Updates to the SQL server.
Open the Script Updates folder on the SQL server. This folder should possess the file UpdateScripts.bat and a folder SQL_scripts.
Right-click the UpdateScripts.bat file and choose Edit.
Scroll to the end of the file and look for the entry %%f in (SQL_scripts\*.sql) DO osql -D RightFax -i %%f
Edit this line to contain switches that are relevant to your environment. Do be aware that a login switch(s) must be entered in conjunction with this command (see examples below). It is also important to note that these examples show the default database name (RightFax). If you have changed your database name from 'RightFax', you must edit this line to include your database name. A complete list of switches is provided in the UpdateScripts.bat file.
Save the UpdateScripts.bat file after making the necessary changes.
Open a command prompt and change to the \Script Updates folder (e.g., C: \Script Updates).
At the command prompt, type UpdateScripts.bat and hit Enter on your keyboard. This will execute the provided SQL script according to the previously entered parameters. Alternatively you can browse to the \Script Updates folder and double-click the UpdateScripts.bat file.
Once completed, bring the RightFax services back on-line. This completes the RightFax server Update.
Right-click Resources, and then select New > Resource. The Generic Resource wizard opens.
In the Name and Description boxes, enter Captaris Conversion Engine.
Set Resource Type to Generic Service.
Select the RightFax group.
In the Possible Owners box, enter the names of both nodes in the cluster by selecting them and clicking Add.
In the Resource Dependencies box, add the RightFax file share name of - RightFax File Share.
In the Generic Service Parameters box, type RFISOCONV. Do not select the use network name for computer name checkbox.
Click Finish to add the resource to the group.
Right-click Resources, and then select New > Resource. The Generic Resource wizard opens.
In the Name and Description boxes, enter Captaris Sync Module.
Set Resource Type to Generic Service.
Select the RightFax group.
In the Possible Owners box, enter the names of both nodes in the cluster by selecting them and clicking Add.
In the Resource Dependencies box, add the RightFax file share name of - RightFax File Share.
In the Generic Service Parameters box, type CapaSync. Do not select the use network name for computer name checkbox.
Click Finish to add the resource to the group.
Stop all RightFax services on all remote RightFax servers.
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.
If you have not already done so, back up the entire \RightFax directory structure and the SQL database for RightFax.
On the active node, use Windows Explorer to open the folder containing the Hotfix files.
In the Hotfix 3 folder, right-click the RightFax folder and choose Copy.
Using Windows Explorer, browse to the RightFax installation folder (e.g., E:\RightFax).
Right-click one folder above the RightFax installation folder and choose Paste followed by Yes to All when prompted with the 'Confirm Folder Replace' message. If you did not receive the 'Confirm Folder Replace' message, you have pasted the new RightFax folder to an incorrect location. In the example of E:\RightFax, you would paste the new RightFax folder into the 'E:\' folder.
Browse to the folder containing the Hotfix 1 files.
Open the folder named GAC_GlobalAssemblyCache\Assemblies. This folder should possess 12 .dll files.
Open a second instance of Windows Explorer and browse to the <system root>\Assembly folder (e.g., C:\Windows\Assembly).
Position the two Windows Explorer windows so that they are both viewable on screen. All other windows should be closed or minimized.
In the GAC_GlobalAssemblyCache\Assemblies folder, sort the files by Type. This can be done by right-clicking any open area within the GAC_GlobalAssemblyCache\Assemblies folder and choosing Arrange Icons By > Type. All files should now be grouped by their corresponding extension.
GAC_GlobalAssemblyCache\Assemblies folder, use your mouse to select the 12 .dll files. Do not select the .config files.
With these files selected, click and hold your right mouse button and drag the 12 .dll files to the <system root>\Assembly folder located in the second Explorer instance. You will not receive a prompt to replace the existing assembly files, however, the Hotfix 1 files will be copied into the <system root>\Assembly folder.
Repeat steps 8-14 on the secondary node.
Apply the SQL Scripts update that is relevant to your environment.
Using Cluster Administrator, bring all the RightFax resources online.
On the active node, double-click the UpdateRegistry.bat file in the Hotfix 1 folder.
Apply Hotfix 1 to all Remote Board servers, Remote WorkServers, and IIS servers according to the instructions listed below.
Restart the remote servers.
Follow these steps to apply Hotfix 3 to all Remote Board servers, Remote Workservers, and IIS servers that are hosting RightFax web applications on your network.
If you have not already done so, back up the entire \RightFax directory structure and the fax board directory (usually the \RFBoard folder). To ensure that all necessary files are properly backed up, stop all RightFax services before beginning the backup process.
Log on to the Remote Board server as an administrator.
Stop all RightFax services and close all RightFax applications.
Copy the Hotfix 3 files to the Remote Board server.
Using Windows Explorer, open the folder containing the Hotfix 3 files.
In the Hotfix 3 folder, double-click the RightFax folder.
Select and copy the directories listed below.
\Bin
\Client
\Docs
\DocTransport
\RFBoard
\Shared Files
Using Windows Explorer, browse to the RightFax Remote Board server installation folder (e.g., C:\Program Files\RightFax).
Right-click the RightFax Remote Board server installation folder and choose Paste followed by Yes to All when prompted with the 'Confirm Folder Replace' message. If you did not receive the 'Confirm Folder Replace' message, you have pasted the new RightFax folder to an incorrect location. In the example of C:\Program Files\RightFax, you would paste the new RightFax folder into the 'C:\Program files\RightFax' folder.
Open Windows Explorer, and browse to the folder containing the Hotfix files.
Open the folder named GAC_GlobalAssemblyCache\Assemblies. This folder should possess 12 .dll files and five .config files.
Open a second instance of Windows Explorer and browse to the <system root>\Assembly folder (e.g., C:\Windows\Assembly).
Position the 2 Windows Explorer windows so that they are both viewable on screen. All other windows should be closed or minimized.
In the GAC_GlobalAssemblyCache\Assemblies folder, sort the files by Type. This can be done by right-clicking any open area within the GAC_GlobalAssemblyCache\Assemblies folder and choosing Arrange Icons By > Type. All files should now be grouped by their corresponding extension.
In the GAC_GlobalAssemblyCache\Assemblies folder, use your mouse to select the 12 .dll files. Do not select the .config files.
With these files selected, click and hold your right mouse button and drag the 12 .dll files to the <system root>\Assembly folder located in the second Explorer instance. You will not receive a prompt to replace the existing assembly files, however the Hotfix 3 files will be copied into the <system root>\Assembly folder.
If you have not already done so, back up the entire \RightFax directory structure. To ensure that all necessary files are properly backed up, stop all RightFax services before beginning the backup process.
Log on to the Remote Workserver as an administrator.
Stop all RightFax services and close all RightFax applications.
Copy the Hotfix 3 files to the Remote Workserver.
Using Windows Explorer, open the folder containing the Hotfix 3 files.
In the Hotfix 3 folder, double-click the RightFax folder.
Select and and copy the directories listed below.
\Bin
\Inso
\Shared Files
\Worksrv
Using Windows Explorer, browse to the RightFax Remote Workserver installation folder (e.g., C:\Program Files\RightFax).
Right-click the RightFax Remote Workserver installation folder and choose Paste followed by Yes to All when prompted with the 'Confirm Folder Replace' message.If you did not receive the 'Confirm Folder Replace' message, you have pasted the new RightFax folder to an incorrect location. In the example of C:\Program Files\RightFax, you would paste the new RightFax folder into the 'C:\Program files\RightFax' folder.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Open the folder named GAC_GlobalAssemblyCache\Assemblies. This folder should possess 12 .dll files and five .config files.
Open a second instance of Windows Explorer and browse to the <system root>\Assembly folder (e.g., C:\Windows\Assembly).
Position the 2 Windows Explorer windows so that they are both viewable on screen. All other windows should be closed or minimized.
In the GAC_GlobalAssemblyCache\Assemblies folder, sort the files by Type. This can be done by right-clicking any open area within the GAC_GlobalAssemblyCache\Assemblies folder and choosing Arrange Icons By > Type. All files should now be grouped by their corresponding extension.
In the GAC_GlobalAssemblyCache\Assemblies folder, use your mouse to select the 12 .dll files. Do not select the .config files.
With these files selected, click and hold your right mouse button and drag the 12 .dll files to the <system root>\Assembly folder located in the second Explorer instance. You will not receive a prompt to replace the existing assembly files, however the Hotfix 3 files will be copied into the <system root>\Assembly folder.
If you have not already done so, back up the entire \RightFax directory structure. To ensure that all necessary files are properly backed up, stop all RightFax services before beginning the backup process.
Log on to the IIS as an administrator.
Stop all RightFax services and close all RightFax applications.
Copy the Hotfix 3 files to the IIS server.
Using Windows Explorer, open the folder containing the Hotfix 3 files.
In the Hotfix 3 folder, double-click the RightFax folder. Select and copy the directories listed below.
\Shared Files
\WebApps
Using Windows Explorer, browse to the RightFax IIS installation folder (e.g., C:\Program Files\RightFax).
Right-click the RightFax IIS installation folder and choose Paste followed by Yes to All when prompted with the 'Confirm Folder Replace' message. If you did not receive the 'Confirm Folder Replace' message, you have pasted the new RightFax folder to an incorrect location. In the example of C:\Program Files\RightFax, you would paste the new RightFax folder into the 'C:\Program files\RightFax' folder.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Open the folder named GAC_GlobalAssemblyCache\Assemblies. This folder should possess 12 .dll files and five .config files.
Open a second instance of Windows Explorer and browse to the <system root>\Assembly folder (e.g., C:\Windows\Assembly).
Position the 2 Windows Explorer windows so that they are both viewable on screen. All other windows should be closed or minimized.
In the GAC_GlobalAssemblyCache\Assemblies folder, sort the files by Type. This can be done by right-clicking any open area within the GAC_GlobalAssemblyCache\Assemblies folder and choosing Arrange Icons By > Type. All files should now be grouped by their corresponding extension.
In the GAC_GlobalAssemblyCache\Assemblies folder, use your mouse to select the 12 .dll files. Do not select the .config files.
With these files selected, click and hold your right mouse button and drag the 12 .dll files to the <system root>\Assembly folder located in the second Explorer instance. You will not receive a prompt to replace the existing assembly files, however the Hotfix 3 files will be copied into the <system root>\Assembly folder.
Hotfix 3 for client computers is an update to RightFax client applications. These clients include; FaxUtil, RightFax Fax Printer and Tray Icon (faxctrl), Soap Clients, and Enterprise Fax Manager. These clients may be updated by either manually placing the files from the Hotfix 3 folder into their respective folders on each client workstation or by updating the client installation source files with the Hotfix 3 files, followed by a reinstall of the RightFax clients.
The instructions below outline how to manually update existing RightFax client installations (see instructions under small-scale deployment) and how to update a RightFax installation source folder (see instructions under large-scale deployment). 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).
IMPORTANT: Hotfix 3 contains two updates to the RightFax SOAP client (tracking ID's 49739 and 49743). To implement these updates you must apply both the client and IIS server updates.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Browse the \RightFax Clients folder and copy the Clients and Shared Files folders.
Browse your network the client workstation that contains a RightFax installation.
Close all RightFax applications including the RightFax Tray Icon. To close the RightFax Tray Icon, go to the Windows systray or notification area and right-click the RightFax Tray Icon and choose exit.
Open the folder you have installed RightFax to (e.g., C:\Program Files\RightFax).
Right-click this folder and choose paste.
Open the folder or network share that contains the existing client installation source files.
Open Windows Explorer, and browse to the folder containing the Hotfix 3 files.
Open the RightFax Clients folder and copy the Clients and Shared Files folders.
Browse to the folder that contains the existing client installation source files (e.g. C:\RightFax Clients\Program Files\Rightfax\)
Right-Click this folder and choose paste. This updates the client installation source. Proceed to part II below.
Open the folder or network share that contains the existing client installation source files.
Open the file Setup.ini
Look for the entry ProductVersion=9.00.0000. Change this value to ProductVersion=9.00.0300.
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 Answer ID 2155- RightFax 9.0 Client Quiet & Silent Install Component Keywords.
CmdLine=/qn REINSTALL=ALL REINSTALLMODE=amus 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.
You may now redistribute the client package.
Hotfix 3 includes several updates to the RightFax Connector for Microsoft Exchange. This update should be applied to all Exchange servers using the RightFax 9.0 SP2 Connector for Microsoft Exchange. A list of software fixes associated with the RightFax Connector for Microsoft Exchange can be found here.
To apply Hotfix 3, you must have administrator access to those Exchange servers you plan on updating.
Log-in to the Exchange server as an administrator.
Stop the RightFax Connector for Exchange service (rfaxgate.exe).
Browse to the folder containing the Hotfix 3 files.
Open the MS Exchange folder and copy its contents. Do not copy the folder itself.
On the Exchange server, locate the RightFax Connector for Exchange installation folder. Default installations are placed at C:\Program Files\RightFax\RFaxGate.
Paste the contents of the MS Exchange folder into the RightFax Connector for Exchange installation folder.
Restart the RightFax Connector for Exchange.
Log-in to the Exchange server as an administrator.
Stop the RightFax Connector for Exchange service (rfaxgate.exe).
Browse to the folder containing the Hotfix 3 files.
Open the MS Exchange folder and copy its contents. Do not copy the folder itself.
On the Exchange server, locate the RightFax Connector for Exchange installation folder. Default installations are placed at C:\program files\RightFax\RFaxGate.
Paste the contents of the MS Exchange folder into the RightFax Connector for Exchange installation folder.
If you wish to increase the number of MAPI client requests (such as those used by the RightFax Connector), follow the steps below as well as those outlined in Microsoft Knowledge Base article 830829. You need only add the values for objtMessage and objtAttachment. Should you not wish to implement this change, you may finish the install by restarting the RightFax Connector for Exchange. Tracking ID 49091 address this issue.
Open Regedit and browse to the subkey: HKLM\Software\RightFax\Gateway. If the the Gateway subkey isn't present, create it by right-clicking the HKLM\Software\RightFax\ subkey and choose New > Key.
Add a DWORD value of AvoidServerLimits. Set this value to 1.
Follow the steps outlined in Microsoft Knowledge Base article 830829 for increasing the number of objtMessage and objtAttachment MAPI client requests.
Restart the RightFax Connector for Exchange.
Listed below are the enhancements and new features introduced to RightFax 9.0 SP2 with the addition of Hotfix 3. Some of these enhancements or new features will require minor registry changes.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
51745 |
Eicon Fax Boards |
Inbound faxes cannot be routed via DID numbers. |
Eicon fax boards now provide the ability to route inbound faxes via DID numbers using T1/E1 with either ISDN or Robbed-bit. Environments using Robbed-bit must set the DID drop-down within the Diva Server configuration to 'Yes'. ISDN environments need not make this change. |
|
46631 |
FaxDump |
Date formatting of FaxDump output is in U.S. format, i.e. MM/DD/YYYY. |
Added a second faxdump.exe called faxdump_int.exe. This new version uses the international date format. To use the new functionality of FaxDump: 1. Rename the existing faxdump.exe file to faxdump.old. 2. Rename the newly created faxdump_int.exe to faxdump.exe. FaxDump can now be used with an international date format. |
|
52366 |
FaxUtil |
The ability to populate fax coversheets with the data found in the Company and City/State fields is not available. |
This functionality is now available with .PCL, .DOC, and .HTML coversheets. Utilize the FROMCOMPANY and FROMCITYSTATE embedded codes to implement this enhancment. |
|
50264 |
SMTP Integration |
Fax coversheets sent via the SMTP gateway do not possess user associated meta-data. |
Coversheets now include the data found within each users 'outbound settings'. To implement this new feature, open Enterprise Fax Manager-> open the SMTP gateway configuration and check the new box 'Use FaxUtil User Information'. Click OK. |
|
50183 |
Server Module |
'Custom Type' notifications are ignored when the
pertaining fax was sent via an email gateway. |
Notification options have been created to change this default behavior. To add this new functionality edit the registry subkey below to contain a DWORD value. HKLM/Software/RightFax/FaxServer/GatewayNotificationMethod DWORD parameters: 0= default behavior 1= a notification will be sent via the gateway method and the user's selected notification method. 2= a notification is not sent through the gateway but is sent via the user's selected notification method. |
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
51172 |
BoardServer |
The option to "Disable Loop Current Detection" is listed when using Brooktrout 1034 faxboards even though 1034 faxboards do not support this feature. |
Corrected. Check box is no longer available. |
|
51173 |
BoardServer |
After configuring an ISA board with an IRQ higher than 9 the IRQ setting drops by 1 after opening the BoardServer control panel. |
Corrected. Problem no longer occurs. |
|
52503 |
BoardServer |
Inbound routing of faxes through a CallXpress server fail when using a TR-114 or TR-1034 faxboard. |
Corrected. Faxes now route as expected. |
|
52504 |
BoardServer |
In the event of a WAN link failure, faxes sent via LCR generate erroneous fax history and are rescheduled. |
Corrected. Faxes now send as expected. |
|
53043 |
BoardServer |
Documents sent via the Stand Alone Fax Connector fail to send outbound faxes after applying SP2. |
Corrected. Faxes now send as expected. |
|
49653 |
ChangeUser |
Users with NT authentication enabled are unable to log-in to the RightFax database when using ChangeUser. |
Corrected. Users with NT authentication enabled are now able to log-in. |
|
51313 |
Com API |
Faxes sent as emails using the Com API are discarded. |
Corrected. Faxes now send as expected. |
|
51574 |
Database module |
Setting system clock to the time zone of GMT+/- n:30 results in inaccurate "CreationTime" in the RightFax database. |
Corrected. Time is now displayed as expected. |
|
51658 |
Database module |
Faxing to a large phonebook group causes the database module to stop. |
Corrected. Database module no longer stops. |
|
51707 |
Database module |
DBPurge generates a SQL error when purging deleted fax records having the same DocFileDBA. |
Corrected. SQL error no longer occurs. |
|
52199 |
Database module |
DBPurge generates an exception error if the date format has been changed to anything other than MM/DD/YY. |
Corrected. Date format can now be changed without causing an exception error. |
|
52463 |
Database module |
The Database and DocTransport Modules fail to start when a RightFax database is installed to a SQL server and is not named 'RightFax'. |
Corrected. Database and DocTransport Modules start as expected. |
|
53353 |
Database module |
Applying Service Pack 2 replaces the the data source and password in RightFax.Api.Remoting.Service.exe.config file thus causing DBPurge to generate a runtime error. |
Corrected. DBPurge no longer
generates a runtime error. Edit the
\RightFax\Bin\RightFax.Api.Remoting.Service.exe.config file with
notepad and confirm that the data source and password fields are correct.
Look for the line: |
|
55659 |
Database module |
DBupgrader hangs when attempting to upgrade a database that contains a RightFax phonebook(s). |
Corrected. DBupgrader now works as expected. |
|
53866 |
Database module |
Addresses a performance issue with nightly database maintenance. |
Corrected. Performance issue no longer occurs. |
|
55659 |
Database module |
DBupgrader hangs when attempting to upgrade a database that contains a RightFax phonebook(s). |
Corrected. DBupgrader now works as expected. |
|
51656 |
DocTransport |
The Windows application event log displays the RightFax database password in clear text should the DocTransport module fail to contact or log-in to the SQL server. |
Password no longer displayed. |
|
51786 |
DocTransport |
Outbound faxes fail with Problem Scheduling Fax when part of a multi BoardServer environment that has one Remote BoardServer stopped. |
Corrected. Faxes now send as expected. |
|
52285 |
DocTransport |
Making changes to the DocTransport configuration causes the DocTransport and BoardServer modules to restart without warning. |
Corrected. DocTransport and BoardServer modules no longer restart without warning. |
|
52507 |
DocTransport |
Faxes sent using a 1034 faxboard and an ISDN line may result in recipient transmission errors. |
Corrected. Faxes are received as expected. |
|
52654 |
DocTransport |
Faxes sent in an environment using 9.0 SP2 with a Remote BoardServer(s) ignore the Channel Availability Index and are not evenly distributed across all channels. |
Corrected. Faxes are now sent using the channel with the highest Channel Availability Index. |
|
52655 |
DocTransport |
Sent fax history does not correctly reflect daylight savings time. |
Corrected. Sent faxes now possess the correct time sent. |
|
52870 |
DocTransport |
Dialing rules fail if the setting within the 'Time and Day ' tab is not set to use GMT. |
Corrected. Dialing rules may now use non-GMT times. |
|
54534 |
DocTransport |
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. |
|
54869 |
DocTransport |
Broadcast faxes do not utilize all available channels when scheduled to be sent via an Eicon faxboard. |
Corrected. Faxes now send as expected. |
|
49910 |
External Document Connector |
Documents scanned from a Xerox device incorrectly display the document scan time. |
Corrected. Scan time is displayed as expected. |
|
51700 |
External Document Connector |
Fax numbers blocked by dialing rules do not generate notifications until the predefined timeout period expires (24 hrs by default). |
Corrected. Notifications are now generated immediately after reaching a blocked status. |
|
47126 |
Enterprise Fax Manager |
Identical billing codes can be created |
Corrected. Billing codes must now be unique. |
|
48939 |
Enterprise Fax Manager |
Environments with 20 or more printers added to the printers container with in Enterprise Fax Manager, may experience a per user issue that causes the Default Printer selection to change each time a user is opened for editing. |
Corrected. The Default Printer field now maintains the printer selection. |
|
49741 |
Enterprise Fax Manager |
The Bypass Privacy Restrictions permission is not available to Group Administrators. |
Corrected. Permission is now available for Group Administrators. |
|
49879 |
Enterprise Fax Manager |
Creating a 'Duplicate' dialing rule overwrites the parent dialing rule. |
Corrected. Parent dialing rule is no longer over-written. |
|
50001 |
Enterprise Fax Manager |
After applying service pack one for Windows Server 2003, RightFax Administrators and RightFax Group Administrators cannot login to RightFax. |
Corrected. RightFax Administrators and RightFax Group Administrators can login to RightFax after applying SP1 for Windows Server 2003. |
|
50129 |
Enterprise Fax Manager |
The Group column displays erroneous group associations. |
Corrected. Groups column now displays the correct group association. |
|
50156 |
Enterprise Fax Manager |
Group administrators are unable to log-in if their account is using NT authentication. |
Corrected. Group administrators can now log-in as expected. |
|
50278 |
Enterprise Fax Manager |
Copying dialing rules from a RightFax server to a Remote BoardServer and choosing to Save Dialing Plan, does not save dialing rules. |
Corrected. Dialing rules are now saved. |
|
51805 |
Enterprise Fax Manager |
An error occurs when attempting to add a Group ID to the signature, Authorized Users list. |
Groups can now be added to the Authorized Users list. |
|
51822 |
Enterprise Fax Manager |
The word Availability is
misspelled as Availability in global, RightFax,
SMS, Eicon, FOIP, & DOCPlus
queues. |
Corrected. |
|
51848 |
Enterprise Fax Manager |
Editing a user causes group association to change. |
Corrected. Problem no longer occurs. |
|
52408 |
Enterprise Fax Manager |
The Reroute Received Fax
Notification drop-down list does not list users
alphabetically. |
Corrected. Users are now listed alphabetically. |
|
52447 |
Enterprise Fax Manager |
Using the 'Secure RPC' option
prevents all remote installations of Enterprise Fax Manager from managing
Dialing Rules. |
Corrected. Remote installations can now manage dialing rules as expected. |
|
52530 |
Enterprise Fax Manager |
The Group ID field drop-down
list does not list available groups
alphabetically. |
Corrected. Available groups are now listed alphabetically. |
|
54357 |
Enterprise Fax Manager |
Creating dialing
rules using the 'duplicate rule' option fails to all new dialing
rules. |
Corrected. Duplicate rule options now works as expected. |
|
51314 |
ETransport Module |
Failed faxes are reported as Email sent to <email> |
Failed faxes are no longer reported as sent. |
|
Exchange 2003 disallows the RightFax Connector from
processing messages if 'objAttachment' limit is exceeded.
|
Corrected. Problem no longer occurs. See Exchange 2003 installation steps for more information. | ||
|
50249 |
Exchange Connector |
Changes made to
the 'Delivery Restrictions' tab are not maintained after closing the
connector properties window. |
Changes are now maintained. |
|
50250 |
Exchange Connector |
Users who have
been added to the 'Delivery Restrictions' list are able to send
faxes. |
Corrected. Restricted user can no longer send faxes through the Exchange Connector. IMPORTANT: The steps outlined in Microsoft knowledgebase article 277872 must be followed if using Exchange delivery restrictions. |
|
50824 |
Exchange Connector |
Custom address spaces cannot be created. |
Corrected. Custom address spaces can now be created. |
|
54341 |
Exchange Connector |
Distribution groups cannot be added to the 'Delivery Restrictions' tab of the Exchange Connector MMC. |
Corrected. Distribution groups can now be added to the 'Delivery Restrictions' tab of the Exchange Connector MMC. |
|
52687 |
Exchange Gateway |
Manually addressed faxes sent from Microsoft Outlook fail to send. |
Corrected. Faxes now send as expected. |
|
50216 |
FaxAge |
Using FaxAge with an account using NT authentication produces a login error: "login failed with error -9902, the password is incorrect." |
Corrected. Accounts using NT authentication can now login as expected. |
|
50067 |
FaxUtil |
Column headers show incorrect data in the ODBC billing code look up window. |
Corrected. Column data appears as expected. |
|
50980 |
FaxUtil |
Users that are do not belong to the local administrators or powers users receive the following error when attempting to configure the RightFax Tray Icon: Unable to set print destination on RightFax Fax Printer to D:\Documents and Settings\All Users\Application Data\RightFax\SpoolJob. You may not have proper permissions |
Corrected. Error no longer occurrs. |
|
51047 |
FaxUtil |
MAPI phonebook
entries incorrectly populate the Business Fax number field with the data
found in the Other Fax field. |
Contact information is now populated as expected. |
|
51415 |
FaxUtil |
Using the 'Received and In-Process Faxes' filter displays faxes from other users. |
Corrected. 'Received and In-Process Faxes' filter now works as expected. |
|
51748 |
FaxUtil |
The History Change Date/Time field is not updated after viewing fax. |
Corrected. The History Change Date/Time field is now updated after viewing fax. |
|
53238 |
FaxUtil |
The time field cannot be populated within the 'Cheap Time' options. |
Corrected. The time field can now be populated as expected. |
|
53695 |
FaxUtil |
Selecting a Groupwise personal contact from a MAPI phonebook causes FaxUtil to crash. |
Corrected. Problem no longer occurs. |
|
52549 |
FaxUtil |
Using MAPI phonebooks with a Groupwise 6.5.4 client causes FaxUtil to crash. |
Corrected. Problem no longer occurs. |
|
53022 |
FaxUtil |
The FaxUtil 'fax status' field does not update correctly when refreshed. |
Corrected. The FaxUtil 'fax status' field updates as expected. |
|
51571 |
FaxViewer |
Saving a fax using the FaxViewer defaults to the 'My Documents' folder regardless of previous save locations. |
The FaxViewer now defaults to the previous save location. |
|
51659 |
GammaLink Adapters |
Installing a GammaLink faxboard creates verbose log files. |
Corrected. Verbose log files are no longer created by default. |
|
48186 |
Impuser |
Importing users via Impuser enables the option to 'Delete After Routing'. |
Corrected. Delete After Routing is not enabled when importing users with the Impuser utility. |
|
Installation |
On Italian versions of Windows XP, the SOAP Client is configured to use an incorrect path to the print queue. |
Corrected. SOAP Client now points to the correct path. | |
|
52927 |
Installation |
International installations do not include the .R2 configuration files necessary for E1- R2 integration. |
Corrected. .R2 configuration files are now included. |
|
50118 |
Java API |
Attaching files to outbound faxes using the Java API causes memory exception. |
Corrected. Java API now sends faxes as expected. |
|
49058 |
Notes Gateway |
Users with 'Auto-OCR New Faxes' enabled receive OCR document without an extension. |
Corrected. OCR documents are now created with an extension. |
|
49336 |
Notes Gateway |
Synchronizing users from Notes to RightFax does not include the 'Allow OCR use' permission. |
Corrected. 'Allow OCR use' permission now included. |
|
49714 |
Notes Gateway |
Duplicate billing codes can be created in the EFM Sync database. |
Duplicate billing codes can no longer be created. |
|
50785 |
Notes Gateway |
Faxes are not deleted from the mail router when the 'Delete Sent Faxes From Router' option is enabled. |
Corrected. Faxes are now deleted from the mail router. |
|
52181 |
Notes Gateway |
Faxes that fail conversion are not purged from the mail router. |
Corrected. Failed faxes are now purged. |
|
54565 |
Notes Gateway |
Fax notifications sent through the Lotus Notes gateway are truncated at 32 characters. |
Corrected. Notifications are no longer truncated. |
|
54589 |
Notes Gateway |
Forwarding an existing memo from a Notes client to a new fax number incorrectly formats the 'To:', 'From:', and 'Subject:' fields vertically. |
Corrected. 'To:', 'From:', and 'Subject:' fields are displayed horizontally. |
|
54766 |
Notes Gateway |
Faxes containing an unsupported file format attachment sent from a Lotus client cause duplicate failed fax notifications. |
Corrected. Duplicate notifications are no longer sent. |
|
54809 |
Notes Gateway |
Setting the EFMSync database > real-time fax status to 'Debug' fails to create debug log file (Gatewayprocessing.txt). |
Corrected. Gatewayprocessing.txt is now created. |
|
48522 |
Outlook Advanced form |
Faxes received from an 8.5 server cannot be opened by the 9.0 Advanced form. |
Corrected. Faxes open as expected. |
|
51058 |
Outlook Advanced form |
Faxes printed from the Outlook Advanced Form are reformatted to letter regardless of paper selection. |
Print jobs can now be formatted to different sizes, such as legal and A4. |
|
53055 |
Outlook Advanced form |
Faxes listed in the real time fax status view display an incorrect receive time of 12:00 AM. |
Corrected. Faxes now display the correct time. |
|
53190 |
Outlook Advanced form |
Faxes viewed using the Outlook Advanced Form cause Outlook to crash. |
Corrected. Faxes can now be viewed as expected. |
|
53218 |
Outlook Advanced form |
Opening faxes via the real time fax status view causes Outlook to crash. |
Corrected. Fax can now be opened via the real time fax status view. |
|
52279 |
Paging Service |
The Paging service crashes if the "recipient notify address" field (in FaxUtil) is populated and the Push Proxy Gateway is not installed. |
Corrected. Paging service no longer crashes, instead an error message is written to the Windows application event log. |
|
53599 |
PDF Module |
PDF documents created with Doc1 cannot be converted |
Corrected. Documents convert as expected. |
|
41314 |
Production |
TIF files are distorted when after using the Tog3 -4 command. |
Corrected. Tog3 -4 command no longer distorts images. |
|
47109 |
Production |
Production module will terminate if a message contains an invalid or blank '{{include}}' statement. |
Corrected. Production module now writes bad input to the \Production\Errors folder. |
|
49392 |
Production |
Sending simultaneous jobs directly to the HFLPR queue will cause the Windows print spooler service to stop. |
Corrected. Print jobs are now queued as expected. |
|
50004 |
Production |
Buffer.exe cannot be run in 'debug' mode. |
Added the ability to run Buffer.exe to run in debug mode. |
|
50171 |
Production |
Buffer.exe discards all documents within an input file if the first document parsed is missing the '{{begin}}' statement. |
Corrected. only the first document will be discarded. All subsequent files are processed. |
|
51683 |
Production |
POSTFILE.EXE will not use HTTPS (SSL) even with -S switch. |
Corrected. HTTPS can now be used. |
|
54950 |
Production |
Pfilter adds BEGIN and END codes that are considered invalid PCL code. |
Corrected. Pfilter functions as expected |
|
53061 |
RightFax Sync Module Hotfix |
Selecting multiple OU's with the same name causes the RightFax Sync Module to crash. |
Corrected. Please the Captaris Sync Module Readme for more information. |
|
49561 |
RightFax Tray Icon |
The <signature> embedded code is not processed when sending a fax to the RightFax fax printer. |
Corrected. The <signature> embedded code is now processed. |
|
RightFax Tray Icon |
The 'Client Configuration' view doesn't not display the HTTP protocol when using the SOAP printer. |
Corrected. HTTP protocol is now displayed. | |
|
50096 |
RightFax Tray Icon |
On German versions of Windows XP, the RightFax fax printer is configured to use an incorrect path to the print queue. |
Corrected. RightFax fax printer now points to the correct path. If the RightFax Fax Printer is already installed, it must be deleted and recreated. |
|
53307 |
RightFax Tray Icon |
Using Print-to-Fax via a Spanish installation of Office 2003 or XP on a Windows 2000 Professional workstation causes FaxCtrl to crash. |
Corrected. Crashes no longer occur. |
|
49960/ |
SAP Gateway |
In a multiple SAP connector environment, changing the values of one SAP connector results in global change. |
Corrected. Changes made to a SAP connector are no longer global. |
|
50878 |
SAP Gateway |
SAP gateway doesn't re-register the RFC destination after losing network connectivity. |
Corrected. SAP gateway will re-register the RFC |
|
54172 |
SAP Gateway |
When running as a service, SAP gateway writes SapAttachX.txt file to the C:\temp folder. |
Corrected. SAP gateway will only write SapAttachX.txt if running as an application (debug mode). |
|
54287 |
SAP Gateway |
9.0 SP2 Enterprise Server with Business Integration, or Business Integration Server installations cannot add more than one SAP connectors. |
Corrected. Two SAP connectors can now be added. |
|
48125 |
Server Module |
Using the <Who> embedded code with with a space between the code and the User name results in the creation of an erroneous account. Example: <Who: UserName> creates the account
'_UserName' |
Corrected. Erroneous user accounts are no longer created. |
|
48198 |
Server Module |
Retry and Interval settings are not used when sending SMS messages. |
Corrected. SMS messages now use the Retry and Interval settings. |
|
50008 |
Server Module |
Viewing a converted, yet unsent fax results in an erroneous retry entry in the RightFax database. |
Corrected. Viewing a converted, yet unsent fax no longer counts as a retry attempt. |
|
50086 |
Server Module |
Using the NewLib embedded code fails to update
existing library documents |
Corrected. The NewLib embedded code now updates existing library documents as expected. |
|
50192 |
Server Module |
Using the '<break>'
command in conjunction with the '<who>' command causes faxes to be
sent from unintended user account. |
Corrected. Faxes now send as expected. |
|
50828 |
Server Module |
The Server and DocTransport Modules will not start
automatically after an MSDE database has completed database
recovery. |
Corrected. The Server and DocTransport Modules will now start automatically upon completion of MSDE database recovery. |
|
50880 |
Server Module |
DBPurge fails to remove database records from deleted RightFax user accounts. |
Corrected. DBPurge will now remove database records from deleted RightFax user accounts. |
|
50914 |
Server Module |
Faxes sent from FaxUtil generate SMS notifications regardless of the notification type setting. |
Corrected. Notifications are generated as expected. |
|
51371 |
Server Module |
Upgrading an 8.5 database using a 9.0 FP1 version of DBUpgrader causes duplicate faxes and deletes FaxUtil folders. |
Corrected. Faxes are no longer duplicated and folders are not deleted. |
|
51764 |
Server Module |
Fax numbers containing only a slash (/) are scheduled to be sent. |
Corrected. Fax numbers containing only a slash (/) will now reach a status of 'Invalid Characters in Phone Number'. |
|
51909 |
Server Module |
Faxes scheduled for auto-printing and to be routed through the Exchange gateway appear hang at the status of "Queued for printing". |
Faxes now reach an 'OK' status when both auto-printing and routing through an Exchange gateway are enabled. |
|
52314 |
Server Module |
Received fax history fails to show the server name in which the fax was received on. |
Corrected. Server name is now displayed |
|
52433 |
Server Module |
Server maintenance runs one additional time when set to 'None Set'. |
Corrected. Maintenance now longer runs when set to 'None Set'. |
|
52685 |
Server Module |
Addresses an conversion performance issue with HTML coversheets. |
Corrected. HTML coversheets convert as expected. |
|
52871 |
Server Module |
Nightly back-up maintenance causes excessive Windows application event logging. |
Corrected. Errors no longer occur. |
|
53383 |
Server Module |
Addresses a compatibility issue with tracking number 49561 that allows faxes to send if a user has selected an unauthorized signature. |
Corrected. Faxes fail to send if a user attempt to send a fax using an unauthorized signature. |
|
53706/ |
Server Module |
Partially received faxes (due to transmission errors) are routed to RightFax users. |
Partially received faxes can now be set to not route. To add this new functionality edit the registry subkey below to contain a DWORD value. HKLM/Software/RightFax/FaxServer/DoNotRoutePartialFaxes DWORD parameters: 0= default behavior (faxes will route) 1= Partially received faxes will not be routed |
|
53794 |
Server Module |
Addresses a blast fax performance issue associated with a large database. |
Corrected. Blast faxes send as expected. |
|
53919 |
Server Module |
Addresses a compatibility issue with tracking number 49561 that allows faxes to send if a user has selected an unauthorized signature. |
Corrected. Faxes fail to send if a user attempt to send a fax using an unauthorized signature. |
|
48332 |
SMS Module |
Sending SMS messages with Greek characters are displayed as question marks on receiving device. |
Corrected. SMS messages with Greek characters are now displayed as expected. |
|
50267 |
SMTP Integration |
Spaces are removed from outbound user names when sending faxes via the SMTP gateway and the SMTP server is Exchange 5.5. 'User Name' is changed to 'UserName'. |
Corrected. Spaces are now included. |
|
51816 |
SMTP Integration |
The <FromPhone:> embedded code is not recognized by the SMTP gateway. |
Corrected. <FromPhone:> embedded code is now recognized. |
|
52532 |
SMTP Integration |
Time stamp of incoming SMTP messages is incorrect when using GMT + 5:30. |
Corrected. Time stamp is now correct. |
|
50981 |
Web Access |
The 'Update Status' button fails to refresh the Web Access client. |
Web Access is now refreshed by using the 'Update Status' button. |
|
51627 |
Web Access |
Selecting to option to 'View History' generates an exception error. |
Corrected. Fax history can now be viewed as expected. |
|
53302 |
Web Access |
Web Access does not allow date range filter in some foreign language locales. |
Corrected. Date range filter works as expected. |
|
54198 |
Web Access |
Faxes cannot be viewed after choosing the rotate button. |
Corrected. Faxes are displayed as expected. |
|
47114 |
WorkServer |
Organizational Units exceeding 20 are not available in the Active Directory Domain(s) and/or Organizational Unit(s) pick-list. |
Corrected. All OU's are now available. Please the Captaris Sync Module Readme for more information. |
|
47117 |
WorkServer |
Adding a new Active Directory group to an existing Active Directory group causes the previous group(s) to be removed. |
Corrected. New groups can be added to existing groups as expected. Please the Captaris Sync Module Readme for more information. |
|
47122 |
WorkServer |
Users created via Active Directory synchronization are not deleted upon removal from Active Directory. |
Corrected. Users removed from Active Directory are subsequently removed from RightFax upon the next synchronization event. Please the Captaris Sync Module Readme for more information. |
|
47935/ |
WorkServer |
Active Directory synchronization fails to populate user notification information when using the default Exchange profile. |
Corrected. All notification information is now populated as expected. Please the Captaris Sync Module Readme for more information. |
|
48175 |
WorkServer |
Workservers utilizing server-side application conversion with MS Word, Excel, PowerPoint, and Internet Explorer may randomly terminate. |
Corrected. Workservers no longer terminate. Please see Captaris Conversion Engine Readme for more information. |
|
49965 |
WorkServer |
Conversion is attempted for those faxes that contain .ZIP files (an unsupported file format). |
Corrected. ZIP files are no longer queued for conversion and will reach status of 'Problem Converting Fax Body or Coversheet'. |
|
50003 |
WorkServer |
Duplicate pages may result when sending .PDF attachments via the Internet Link module. |
Corrected. Duplicate pages are no longer created. |
|
50048/ |
WorkServer |
Address various HTML conversion related issues. |
HTML documents now convert as expected. Please see Captaris Conversion Engine Readme for more information. |
|
50103 |
WorkServer |
The WorkServer allocated to Active Directory synchronization must be restarted in order to synchronize users created in or added to a new child domain group. |
Corrected. Users are synchronized in real-time. Please the Captaris Sync Module Readme for more information. |
|
50274 |
WorkServer |
Fax conversion may cause incorrect page order. |
Corrected. Fax conversion no longer affects page order. |
|
50890 |
WorkServer |
The index file created by archiving sent faxes displays the fax status incorrectly. |
Corrected. Index file now contains the correct fax status. |
|
51130 |
WorkServer |
PDF files may fail conversion when using Adobe Acrobat 7 to convert attachments. |
Adobe Acrobat 7 can now be used to convert PDF attachments. |
|
51743 |
WorkServer |
Some PCL code is lost during conversion. |
Corrected. PCL code is now converted as expected. |
|
52684 |
WorkServer |
Enabling 'Archive Sent Faxes' and a corresponding index file results in the creation of an invalid entry in the index file. |
Corrected. Index file contains correct data. |
|
53391 |
WorkServer |
Active Directory Synchronization will not import a user if their full name contains a comma "," followed by a forward slash "/". |
Corrected. Issue no longer occurs. Please the Captaris Sync Module Readme for more information. |
|
53227 |
WorkServer |
Visio attachments fail to convert. |
Corrected. Visio documents convert as expected. |
|
53751 |
WorkServer |
Postscript conversions consume excess memory. |
Corrected. Postscript conversions no longer consume excess memory. |
|
53811 |
WorkServer |
Certain PCL documents fail to convert properly. |
Corrected. PCL documents convert as expected. |
|
54361 |
WorkServer |
Certain TIF and JPG files are not purged from the \RightFax\Outgoing directory. |
Corrected. Issue no longer occurs. |
|
54509 |
WorkServer |
Formatting issues occur when users are set to the default auto-print resolution of 'normal' and attempt to auto-print inbound faxes. |
Corrected. Issue no longer occurs. |
|
54515 |
WorkServer |
Active Directory Synchronization causes erroneous event logging should an Active Directory user name possess an apostrophe. |
Corrected. Issue no longer occurs. Please the Captaris Sync Module Readme for more information. |
|
54620 |
WorkServer |
BMP files convert to blank pages. |
Corrected. BMP files convert as expected. |
|
54737 |
WorkServer |
Active Directory Synchronization causes will restart if an Active Directory user name possess an apostrophe. |
Corrected. Issue no longer occurs. Please the Captaris Sync Module Readme for more information. |
©2006 Captaris. All rights reserved.