This document describes known issues and restrictions in IDM Desktop, Web Services, and Open Client 4.0. It includes workarounds and information on fixes, when available, and corrects documentation errors.
Hot fix packs are released periodically, which may include documentation updates. See the readme file for information on how to download hot fix packs from the FileNet FTP site, and see the patch readme file for a description of the patch contents and how to install it.
Where applicable, each note includes the associated Defect Tracking System (DTS) number for reference and tracking.
Known Issues in IDM Desktop/FileNet Web Services
Clicking the Open option to view MS Word document displays a blank page with Office 2000 installed on a Windows XP SP2 client machine. The same contents can be viewed when the document is opened using the IDM Viewer. (DTS 138412)
The Add and Link state is currently displayed when checking in a compound document from a network drive. Since all the necessary components of the compound document are available at a single location, the Link and Cancel state should be displayed instead. (DTS 38076)
Following are the two workarounds to get the Link and Cancel state displayed:
Unable to register Pixel DLLs while upgrading IDM Desktop 3.3 to IDM Desktop 4.0 with Capture 4.1 installed
Installing Capture 4.1 on top of IDM Desktop 3.3 marks the common Pixel modules as Read-Only. During an upgrade from IDM Desktop 3.3 to IDM Desktop 4.0, the Read-Only attribute of these modules causes the installer to fail in registering them correctly.
To successfully upgrade from IDM Desktop 3.3 to IDM Desktop 4.0 with Capture 4.1, install Capture 4.1 patch 34. (DTS 147620)
Sticky Note annotation color changes when viewed using Java Viewer
A sticky note annotation in a document is always displayed in YELLOW in the IDM Viewer. But a sticky note annotation created and saved through the IDM Viewer is displayed in RED in the Java Viewer because the IDM Viewer incorrectly saves the annotation color as RED. (DTS 148365)
Unable to apply annotations on a long document
IDM Viewer does not allow applying annotations towards the end of a long document. (DTS 151060)
FnLocalDB.exe keeps on running after closing all IDM applications
After performing check-in and check out operations on a document, the FnLocalDB.exe keeps running even after closing all the IDM applications. This process however does not have any impact on the normal functioning of the system. But if you still want to remove this process for some reason, you can either remove it from the Windows Task Manager or consider options like logging off the current Windows user or restarting the machine. (DTS 137519)
Application Integration fails with Microsoft Outlook 2000
Application Integration fails when the selection for E-mail Service Options is set to "Internet Only" (default) while configuring an E-mail account using Microsoft Outlook 2000. You need to change the E-mail Service Options setting to "Corporate or Workgroup" in order to make the functionality work. However this issue does not occur with Microsoft Outlook XP or Microsoft Outlook 2003. (DTS 151678)
Canceling document checkout through FileNet Web Services Application Integration shows an error
When a document checkout is canceled through FileNet Web Services Application Integration with Microsoft Office, a dialog box appears that prompts the user to keep the local copy. Clicking the No button displays an error "Method '~' of object '~' failed", although the cancel checkout operation is successful. (DTS 151823)
Checking in a document through FileNet Web Services Application Integration displays a LocalDB warning
A LocalDB warning is displayed on the last screen of the Add/Checkin wizard when a checked out document is checked in through FileNet Web Services Application Integration with the "Keep local copy" option selected. The document is however checked in successfully. (DTS 152150)
Unable to check in new or unsaved document through FileNet Web Services Application Integration
When trying to check in a newly created or unsaved document through FileNet Web Services Application Integration with Microsoft Office, the user is prompted to select a checked out document from the library. After selecting a document, only the Cancel button is enabled in the Add/Checkin wizard. The user cannot perform any operation other than Cancel. (DTS 151819)
IDM Viewer supports viewing of documents under Internet Protocol Security (IPSec)
IPSec provides data privacy, integrity, authenticity, and anti-replay protection for network traffic between two Windows system. FileNet Web Services supports viewing of documents using IDM Viewer under IPSec configuration with default security policy on a Windows 2000 server.
While installing IDM Desktop/FileNet Web Services 4.0 GA or any of the subsequent patches, if the value of the environment PATH variable (including FileNet path) exceeds 1024 characters, then this value is replaced by "C:\FileNET\IDM;C:\FileNet\FNSW\CLIENT\BIN;C:\FileNet\FNSW\CLIENT\SHOBJ". This replacement of value may result in execution failure of various applications including MS Windows. It is therefore recommended that prior to the installation you must take a backup of the environment PATH variable value. Later after installation, you must append the environment PATH variable value with the backed up value.
IDM Viewer takes a long time to open an image retrieved from an optical disk with Windows Firewall enabled on Windows XP SP2. There are two possible workarounds to view an image document retrieved from an optical disk in IDM Viewer without any delay:
Workaround 1: Include the following .exe files in the Windows Firewall exception list.
Following are the steps to include an application program (.exe file) in the Windows Firewall exception list:
Workaround 2: Disable the IS server UDP notification and ask IDM Desktop to poll the server at regular intervals to see if the document is ready. For this, you need to set the value for IDM Preference "Use Server notification for IS document migration" to "No". Following are the steps to configure this preference:
Leave the value of "IS document migration timeout (seconds)" preference as 120 that is the default value.
Sending the entire IS document as attachment creates a temporary folder on the Web server to save the pages of a multi-page IS document. The temporary folder does not get deleted if message sending fails for some reason. (DTS 138903)
Logon to Open Client server fails using unified logon
Logging on to any Open Client library using unified logon, after installing JRE 1.4.2, displays a Java "Password Needed - Networking" logon dialog box. SUN Microsystems recommends specifying logon credentials as:
Username: domain\username
Password: password
For further reference click on the following link: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4856521.
Unable to open text page of a mixed format document
Java Viewer does not display the text page properly when opening a mixed format document that contains bmp, jpeg, tiff, and text formats. (DTS 150590)
Unable to save annotation after applying arrow annotation
An "Annotation Save Failed" error occurs in the Java Viewer when a user tries to save an arrow annotation after increasing its head size. (DTS 150814)
Unable to open large documents while using Windows 2003 Server with SP1
Large documents do not open through the Java Viewer, IDM Viewer or the Open option while using Windows 2003 Server with SP1. This issue might be experienced with file sizes as low as 35 KB. Microsoft is expected to provide a fix for this issue in .NET Framework 1.1 SP2. Until .NET Framework 1.1 SP2 becomes available, the issue can be resolved by applying the fix for KB902780 (http://support.microsoft.com/?id=902780). You should go through this article for more details and contact Microsoft Technical Support at 1-800-936-3500 for receiving the hotfix. (DTS 151346)
Unencoded HTML input from a client to an ASP.NET application on a server with Microsoft .NET Framework 1.1 causes an error
An error "A potentially dangerous Request.Form value was detected from the client" occurs if an unencoded HTML input (for example special characters like "<" or ">") is submitted from a client to an ASP.NET 1.1 application deployed on a server running Microsoft .NET Framework 1.1.
Microsoft .NET Framework 1.1 provides a new request validation feature that prevents script-injection attacks. You can enable or disable this feature using the "validateRequest " attribute. To disable the request validation feature and avoid receiving the error message, Microsoft suggests setting the “validateRequest” attribute in the “web.config” file to 'false'. But this may increase the vulnerability of malicious attacks due to cross-site scripting. For further details refer to Microsoft KB article: (http://support.microsoft.com/default.aspx?scid=kb;en-us;821343).
FileNet recommends having this security feature enabled and avoid using unencoded HTML input.
Unable to logon to any library from multiple virtual directories of Open Client with Microsoft .NET Framework 1.1 SP1 installed
Multiple virtual directories in Open Client causes one of them to crash when logging on to any library with Microsoft .NET Framework 1.1 SP1 installed. While installing Open Client the ADODB.dll is copied under <Installation Directory>\FileNet \IDM\Web\FNOpenClient\bin folder. The ADODB.dll gets registered in GAC with Microsoft Visual Studio installed, but this dll is not registered in GAC with Microsoft .NET Framework 1.1 SP1 installed. Following are the steps to register the ADODB.dll with Microsoft .NET Framework 1.1 SP1 installed: (DTS 167607)
For further details on this issue refer to the following Microsoft KB article: (http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B810098).