Release Notes (Known Issues)
for IDM Desktop, FileNet Web Services, and Open Client 4.0.1

This document describes known issues and restrictions in IDM Desktop, Web Services, and Open Client 4.0.1. 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.

Contents

Known Issues in IDM Desktop/FileNet Web Services

Known Issues in Open Client

Known Issues in IDM Desktop/FileNet Web Services

Only one Listener is active at any given point of time for Web applications having Listener Implementations

Two ASP Web applications could be an IDMWS Web application and a customized IDMWS Web application, both residing on the same Web server and each having a Listener implementation. Here only the Listener for the first Web application to be accessed would run, the Listener for the other Web application would *not* run at that particular time.

However, as a workaround, if you set the “Application Protection” property for any of the Web applications on the Web server as High, Medium, or Low, the Listener implementation will work as shown in the table below. For example, two Web applications (Web Application 1 and Web Application 2) each with Listener implementation on the same Web server will function as shown in the table below. (DTS 179584)

"Reinstall" option of IDM Desktop/Web Services 4.0 does not work properly after installing IDM Desktop/Web Services 4.0.1

After installing IDM Desktop/Web Services 4.0.1, if the user uses the "Reinstall" option, then the registry information would get updated as IDM Desktop/Web Services 4.0. However, the modules on the machine would remain to be of IDM Desktop/Web Services 4.0.1. As a workaround, if the user again installs IDM Desktop/Web Services 4.0.1 on the reinstalled IDM Desktop/Web Services 4.0, the system works properly. (DTS 184557)

Users are unable to use P8 Image Manager Application Integration when Secure Sockets Layer (SSL) is configured

In IDM Desktop/Web Services 4.0.1, when the Web server is configured with SSL using the "Require/Accept Client Certificate" option, Thin Client Application Integration does not work. However, it works properly when SSL is configured using the "Ignore Client Certificate" option. (DTS 185955)

Users are not able to Add/Remove any Components through IDM DT/WS 4.0 SplashD(W).exe

After installing IDM Desktop/Web Services 4.0.1, users can Add/Remove components using Control Panel -> Add/Remove Programs but are not able to Add/Remove components through IDM Desktop/Web Services 4.0 SplashD(W).exe -> Add/Remove link. (187488)

Users are not able to Add and Remove Components if IDM Desktop/Web Services 4.0 Installation Path is Changed

After installing IDM Desktop/Web Services 4.0.1, users are not able to add and remove components at the same time using the Add/Remove components functionality, if the IDM Desktop/Web Services 4.0 installation path is changed to another location. (DTS 187998)

Users are unable to Check-in MS Word Documents in a CS library using IDM Desktop

IDM Desktop fails to check-in MS Word document(s) in a CS library, if the document(s) contains a drawing canvas before any other picture and the value of two preferences "Determine if the file is a compound document" and "Show "Determine if the file is a compound document"" is set to Yes in the IDM Configure tool. The steps to set the value for these preferences using IDM Configure tool are as follows: (DTS 168875)

1. Click Start->Programs->FileNet IDM->Configure to open the IDM Configure window.
2. Click Additional Preferences... to open the IDM Preferences (for All Users) window.
3. Double click the Documents->Add, checkin, retrieve preference category and set the value for "Determine if the file is a compound document" and "Show "Determine if the file is a compound document"" preference to Yes.

The document is checked-in successfully if the picture is inserted before the drawing canvas and the value for "Determine if the file is a compound document" and "Show "Determine if the file is a compound document"" preference is set to No.

Microsoft is expected to provide a fix for this issue in Office 2003 post-SP 2 and Office 2002(XP) post-SP 3 hotfix packs. Until these hotfix packs become available, the issue can be resolved by applying the fix mentioned in the Microsoft Knowledge Base article KB 910282 (for Word 2003) and KB 906861 (for office 2002(XP)). You should go through these articles for more details and contact Microsoft Technical Support at 1-800-936-3500 for receiving the hotfix.

Users will not be able to Upload documents quickly due to OpenFileFactor Registry Key performance issues (DTS 171247)

• If the value specified for OpenFileFactor is greater than 10 then 10 will be set as the default value and if no value is specified then 1 will be set as the default value.
• The maximum character length of the selected document(s) name should not exceed 2600 characters (260 * 10) where 260 is the MAX_PATH (Windows constant variable) and 10 is the maximum value that can be set for OpenFileFactor.
• Increasing the OpenFileFactor registry key value will result into performance degradation in terms of uploading document(s) speed. The documents are first uploaded to IIS server and then added in the IS Library. Two performance issues that are encountered while adding document(s) in the IS library are as follows:
  • If the size of the document is heavy then uploading multiple documents will degrade the performance (size of the document for performance depends upon the system configuration). While uploading the document(s) temporary files are created on the local drive of the IIS server and if the local drive of the IIS server does not have enough space to copy all the temporary files then an error is generated.
  • If the memory space is not sufficient in the library cache to commit the document then the document is not committed and an error “The document couldn't be added to the library. Commit new document failed” is generated.

Users would not be able to directly interact with the ActiveX controls and applets in Microsoft Internet Explorer (DTS 175404)

• The technique of embedding ActiveX controls and applets using external script will not work if the “Disable Script Debugging" check box located at Internet Options -> Advanced tab in Microsoft Internet Explorer application is un-checked. Un-checking this check box means that the user will have to click on the ActiveX control or applet to activate it even after incorporating external JavaScript file to load the ActiveX controls and applets.
• After the user clicks on an ActiveX applet control in a program that runs the applet control by using Java Platform, Standard Edition (J2SE) 1.3 or J2SE 1.4, the focus may not go to the applet control. The user must click the control for a second time to establish focus. The focus behavior works correctly in J2SE 1.5.
• In case of Process, the user may have to explicitly click on the ActiveX controls and applets to activate them. As the support for IE ActiveX controls and applets update for eProcess will be available in eProcess 5.0 patch 18 and eProcess 5.1 patch 06.

For more information about known issues for this update, refer to KB 912945.

Known Issues in Open Client

Only one Listener is active at any given point of time for two ASP.NET Web applications each having Listener implementations

Two ASP.NET Web applications could be, an Out of the Box Open Client Web application and a custom Web application built on top of Open Client Web application, both residing on the same Web server and each having a Listener implementation. Here only the Listener for the first Web application to be accessed would run, the Listener for the other Web application would *not* run at that particular time. (DTS 179662)

For Windows 2003 server, if IDM Web Services and IDM Open Client both are residing on the same Web server and in the same application pool and each having a Listener implementation, then only the Listener for the first Web application to be accessed would run.

Users are unable to change CS library annotation security as IS library users and groups are displayed instead of CS library

If a user logs on to both the CS and IS libraries, simultaneously and later logs on to the CS library to edit the annotation security by adding new users, then Java Viewer displays users and groups corresponding to the IS library in place of CS library. (DTS 182314)

Users are not able to receive error pages having format similar to rest of Open Client pages on Windows 2003 Server

After installing Open Client 4.0.1 on Windows 2003 Server, if the user performs an operation which generated an exception. A default runtime error page may get displayed in place of an error page having format similar to rest of Open Client pages. This is due to the fact that on a Windows 2003 server "Network Service" user does not have sufficient permissions to log errors in the existing event log files or to create a new event log file. As a result, the error messages are not stored in the log file and users may receive runtime errors. The steps to avoid receiving such errors requires the following changes in the registry: (DTS 179538)

1. Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog right click to open the context menu.
2. Click Permissions from the context menu.
3. Add "Network Service" user and grant "Full Control" permission.
4. Reboot the machine.

Users are not able to install Open Client 4.0 on top of IDM Web Services 4.0.1

After installing IDM Web Services 4.0.1, if the user installs Open Client 4.0, then the installation fails. This issue can be resolved by installing Open Client 4.0 directly on top of IDM Web Services 4.0 or its patches and then applying IDM Web Services 4.0.1. (DTS 188217)

Unable to open large documents on Windows 2003 Server with SP1

Large documents do not open through the Java Viewer, IDM Viewer or the Open option on 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)

Open Client installer will not update the existing customized FnOpenClient.vbproj and FnJavaView.aspx files

The Open Client patch installer will not update the FnOpenClient.vbproj file in case of complete installation with customization and custom installation. You can get the latest .vbproj file that has been bundled with the patch by running the installation in the maintenance mode and choosing the modify option. The steps to get the modified .vbproj file are as follows. (DTS 163221)

1. Click Start->Settings->Control Panel->Add/Remove Programs.
2. Click "Change/Remove" button for FileNet Open Client installation.
3. Select "Modify" option from the FileNet Open Client Setup Maintenance dialog box and click Next to complete the installation.

For cases where any custom modifications have been made to the FnJavaView.aspx file, the patch will not override this file. To get the latest file, you need to move this file from the <Installation Directory>\FileNet\IDM\Web\FNOpenClient folder to some other location on your local machine and then run the patch installer.

Please note that any custom modifications made to the FnJavaView.aspx file will have to be made manually in the FnJavaViewHelper.js file located in the <Installation Directory>\FileNet\IDM\Web\FNOpenClient\Util\JS folder.

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. The steps to register the ADODB.dll with Microsoft .NET Framework 1.1 SP1 installed are as follows: (DTS 167607)

1. Browse to <Installation Directory>\FileNet \IDM\Web\FNOpenClient\bin folder.
2. Open another Windows Explorer instance and browse to C:\<Windows Directory>\assembly folder.
3. Drag and drop ADODB.dll file from <Installation Directory>\FileNet \IDM\Web\FNOpenClient\bin folder to C:\<Windows Directory>\assembly folder.

For further details on this issue refer to the following Microsoft KB article: (http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B810098).

Issues with the Java Viewer Quick Start feature (DTS 171081)

• Web session will not end until Quick Start feature is disabled or the user explicitly logs out of the session with the Web server. If the Quick Start feature is enabled, closing the browser window(s) will not terminate the session with the Web server.
• If Quick Start is enabled and Internet Explorer is not the default browser, then on machine re-login or reboot, a message will display asking whether you want to make Internet Explorer the default browser. The steps to avoid receiving this message after rebooting the system are as follows:
  1. Open a browser window.
  2. Select the Tools->Internet Options... menu item to open the Internet Options dialog box.
  3. Click the Programs tab and un-check the "Internet Explorer should check to see whether it is the default browser" check box.
  4. Click Apply.
  5. Click OK.
• If the "Always" button is not selected on the security dialog box of Thawte security certificate associated with the Java Viewer, then on machine re-login or reboot, the Thwate security dialog box is displayed. 
• The Quick Start option is not available for the user when an IP address is used to access the Java Viewer instead of a host name. This is because the Java Plug-in makes no attempt to resolve the server name into an IP address and it therefore, considers a server name and IP address (even if they point to the same place) as totally separate codebase locations. (DTS 179860)

Users would not be able to directly interact with the ActiveX controls and applets in Microsoft Internet Explorer (DTS 172521)

• The technique of embedding ActiveX controls and applets using external script will not work if the “Disable Script Debugging" check box located at Internet Options -> Advanced tab in Microsoft Internet Explorer application is un-checked. Un-checking this check box means that the user will have to click on the ActiveX control or applet to activate it even after incorporating external JavaScript file to load the ActiveX controls and applets.
• After the user clicks on an ActiveX applet control in a program that runs the applet control by using Java Platform, Standard Edition (J2SE) 1.3 or J2SE 1.4, the focus may not go to the applet control. The user must click the control for a second time to establish focus. The focus behavior works correctly in J2SE 1.5.

For more information about known issues for this update, refer to KB 912945.