Edit Tiff image during Indexing.

Problem: The requirement was to provide users Tiff editing facility while Indexing a batch.
Environment : FileNet Capture Professional 4.1, Panagon IDM Desktop 3.2, Image Server as repository, KODAK Imaging (V 2.8)
Solution : Used KODAK Imaging (V 2.8) software which comes free with Windows Server
operating Systems. It comes as a bundle of COM(Active X) controls which can be used in Visual Basic application. Benefit of using KODAK imaging is that the Tiff image quality remains same after editing

Kodak Imaging COM components can be found at: C:\Program Files\Imaging ,if Kodak Imaging is already installed on your computer.

Session problem for multiple users while using Imaging applications through Citrix.

Problem: Consider a scenario when one user logs in to the customized Panagon application through Citrix URL, application works fine. But as soon as the second user tries to log into the same application, it kills the previous user's session.
Reason: Lack of access rights for users to Application and temporary folders being used by application.
Solution: Within Citrix presentation Server you can enable virtual IP feature. This allows each user to be allocated a unique IP address whenever they run an application from a server that has Virtual IP Addresses enabled. Citrix servers should be on a subnet that has a free IP address range to be used by the applications.

Panagon IDM Desktop 'Cache Size' Issue.

Problem: Consider a scenario when multiple users try to retrieve images from Image Server and gets 'Retrieve from cache failed' error intermittently.
Reason: The size of retrieved image file is too big for IDM cache to retrieve the image
completely.
Solution: Increased the size of Cache being configured on Citrix Server where IDM Desktop was Installed. Open FileNet IDM configure and then click 'Additional Preferences'.Expand 'Directories and Files' node and increase 'maximum cache size' & 'Maximum cached Documents’.

Unable to keep IDM Desktop running on a VM Citrix Server.

Problem: Consider a scenario where there is a requirement of preparing a Citrix Server using a Virtual Machine. We Installed FileNet IDM Desktop 4.1 and checked whether its connecting to image server, it worked fine. Then installed FileNet Capture 4.1 on this machine, configured image server repository and checked whether its functioning properly. The problem started on very next day of the installation of these softwares.When we tried to connect to Image Server from FileNet IDM Desktop 4.1 it could not connect. We uninstalled and reinstalled these software again and it started working fine, but got the same problem again on next day. So on very next day after Installation, IDM desktop was stopped working.
Reason : Unknown as of now
Solution: The solution was to install these software on a physical machine instead of a Virtual Machine.

User session locked on IS due to a network errror in Citrix environment.

Problem: Consider a scenario where user gets locked while using Imaging applications through Citrix URL and not able to continue with the work.
Reason: When user uses the application through Citrix URL, sometime session becomes expire if the application is left IDLE for a long time and it leaves the user logged into image server. Assume the user is allowed to create only session with the IS.
Solution: System administrator can be contacted to unlock the user on Image Server so that user can continue with the application.

Error ‘LDAP Server Down’ while connecting to CE 3.5.1 through Citrix after migration of existing e-Directory to a new server.

Problem: Consider a scenario where a user successfully accesses CE Server through FileNet Enterprise Manager (FEM) from a Windows 2003 server (SP1) box but gets ‘LDAP Server Down’ error while coming from Citrix URL.This error started happening after the migration of existing e-directory to a new server.The problem still remained even if the firewall rules were set to allow all incoming and outgoing traffic between e-Directory server and Citrix server hosting FEM application.
Reason: Tracing was configured on e-Directory server to track all incoming requests and outgoing responses. It was found that the requests coming through Citrix were failing while the one coming directly from the physical machine (Windows 2003 server machine) were getting processed successfully by e-Directory. It was later found that the security certificate, which was installed on the Citrix server to communicate with e-directory was meant for a user profile and not for the Local computer and that’s why not allowing anybody to launch FEM through Citrix.
Solution: Imported Security certificate through MMC console for the Local Computer not for a user profile.