Thursday, June 19, 2008

Error while configuring GCD during Content Engine Client Installation

Problem : Received GetDomainInfo hr = 0x8007005 error while configuring GCD during CE Client installation.
Solution : This problem is related to security access.Steps to resolve the problem:

The wizard is using DCOM to create an instance of a class on the Content Engine server. DCOM must be working for this task to complete. There are a few ways in which DCOM can be prevented from working, including but not limited to:

1. switching off DCOM using the dcomcnfg utility or registry modifications. See the following Microsoft Knowledge Base article for more information: . The server and workstation administrators should ensure that DCOM is enabled.

2. restricting ports which are available. The ports used by DCOM can be managed through the dcomcnfg utility using the Default Protocols tab. The local network folks should ensure that ports used by DCOM are available.

Enabling DCOM
Use DCOMCNFG.EXE
1. Run Dcomcnfg.exe.
2. If you are running Windows XP or Windows Server 2003, perform these additional steps:
a. Click the Component Services node under Console Root.
b. Open the Computers folder.
c. For the local computer, right-click My Computer, and then click Properties.
d. For a remote computer, right-click Computers folder, point to New, and then
click Computer.
e. Type the computer name.
f. Right-click the computer name, and then click Properties.

3. Click the Default Properties tab.
4. Click to select (or click to clear) the Enable Distributed COM on this Computer check box.
5. If you want to set more properties for the computer, click Apply to enable (or disable) DCOM. Otherwise, click OK to apply the changes and quit Dcomcnfg.exe.
6. Restart the operating system for the changes to take effect.

MORE INFORMATION
The following registry string value is used to enable or disable DCOM on all operating systems:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE\EnableDCOM
If you change this value to N, you disable DCOM after you restart the operating system. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry

Check the User being used for installation
Make sure that the user which is being used for installing Content Engine client should be :
a). Added into the Local Admin Group on the Server (Environment Dev/Cat/Stg) you are trying to connect.
b).'FilenetAdmins' group should also be a member of the Locan Admin Group on the Server (Environment Dev/Cat/Stg)
c) DCOM Configuration :
a) Goto MyComputer's Properties -> COM Security -> AccessPermission -> EditDefault
Add 'FilenetAdmins' with full permissions
b) Goto MyComputer's Properties -> COM Security -> Launch & ActivationPermission -> EditDefault
Add 'FilenetAdmins' with full permissions

Configurations settings were lost after Image Server upgrade.

Problem : After upgrading from IS 3.6 to IS 4.0 we lost the configuration settings in Capture for production repository. User were unable to scan using FileNet Capture.
Solution: Follow below mentioned steps :

1).Add an entry into Hosts file c:\windows\system32\drivers\etc to point to old IMAGE server as shown below :
XXX.XXX.XXX.XXX stgeorge-filenet-nch-server
2).Then open the repository in Capture Professional 4.1 using sysadmin username and password and copy all the configuration settings to Local repository.
3).Remove or comment out the entry done in Hosts file in step 1. Open the same Image Server repository in Capture Professional with SysAdmin credentials and copy config folder from LocalRepository to the missing production repository. Close the Capture application and log back in again with scanning user credentials.Test the application by scanning few batches. Old settings should be used by scan and other components.

Tuesday, June 17, 2008

How to get user credentials being used by Capture Manager, programmatically?

Solution: You can get the CE credentials used by Capture Manager by accessing following registry entry HKEY_LOCAL_MACHINE\SOFTWARE\FileNET\Panagon Capture\ CurrentVersion\ Capture Manager\Repositories
Find your repository name and access it through application code. If you are coding your application in Visual Basic 6.0, the following link may be of your use.
http://www.freevbcode.com/ShowCode.asp?ID=4330

Wednesday, June 11, 2008

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.

Sunday, June 01, 2008

How to use an Image Services Server on a Different Subnet?

If you will be accessing an Image Services server on a subnet that is different from the one your workstation is on, add an entry like the following to the hosts or lmhosts file:
xxx.xxx.xxx.xxx --nch-server
Where:
xxx.xxx.xxx.xxx is the IP address of the Image Services server
domainis the Image Services server domain name
organization is the organization name selected for the Image Services server during the initial installation.(Typically the organization is filenet.)

For example, your entry might look like this:
10.1.20.123 mysystem mysystem-filenet-nch-server
Note that domain names are limited to lowercase and alphanumeric characters.
For more information about Image Services access, contact your Image Services System
Administrator

How to detect Bar Code/Patch code from JPEG and Gray Scale Images in FileNet Capture 5.1?

If you are using certain Kofax controller boards or have installed the Advanced Doc Processing option, you may be able to detect bar codes and patch codes from JPEG and grayscale images.

Barcode in FileNet Capture

Supported Bar Code Types
When designing a Capture system that employs special bar code features, ensure that all parts of the system — from the scanner to the storage repository — can support the features adequately.
Consider the following to ensure adequate support by Capture:
• Your scanner, scanner interface card, or doc processing software might support bar code types that are not listed in this document. Conversely, your scanner might not support some of the bar code types supported by Capture.
• Some bar code types supported by Capture might provide features (support for control
characters, for example) that are not supported in other Capture components.
• Some bar code types might contain more characters than Capture features (such as index fields) can accommodate. For example, some wo-dimensional bar code symbols support up to 2000 characters in a single bar code. However, your index fields, configured on the server, might not be able to accept that number of characters and truncate the data.
NOTE FileNet added support for two-dimensional bar codes in Capture release 4.0. If you are using an earlier release, you must upgrade to Capture 4.0 to use the two-dimensional bar codes.
General Considerations
Using bar codes for quality assurance, batch separation, and automatic indexing can reduce cost, increase system throughput, and reduce errors. A bar code contains information – account numbers, part numbers, customer addresses, etc. - that usually corresponds to properties that are associated with the documents you are scanning.

When using bar codes, you need to determine if you are using hardware or software bar code processing. If your scanner or scanner interface board supports doc processing, you use hardware bar code processing. Hardware bar code detection takes place as you scan your documents. The scanner passes the image to the processor on the board that interprets the bar code based on configuration settings in the Scan component. The interpreted information is stored as properties of the image.

If you have optional Doc Processing (Kofax Adrenaline) software installed you use software bar code processing. This processing is performed by the DocProcessing component. Software bar code processing takes place as a separate step, after you have scanned or imported your document. Software bar code processing locates the bar code in the image and extracts the embedded information. You configure the bar code settings for post-scan software bar code detection through the DocProcessing component.

Specific characteristics of bar codes include height, width, ratio, bar code length (minimum chars per bar code setting), max bar codes per line, max bar codes per page, search direction, bar code type, quality, edge noise, quiet zone, speckling, and skew. All of these characteristics can be adjusted to maximize bar code detection
There are a number of symbologies, or bar code alphabets, available. Each symbology varies in the number of characters contained in its alphabet. For example, Code 3 of 9 includes 43 characters including letters, digits and some punctuation.

Bar Code Quality Adjustments
The quality of the bar code on the page to be scanned (or imported) will affect whether or not the bar code can be read and decoded accurately. Both hardware and software bar code detection methods may fail if the bar codes on the original images are distorted or poorly reproduced. The following suggestions apply to the bar codes on the source documents that you are scanning or importing:
• The density of the lines of the bar code can be made darker or lighter to improve detection. Increase the resolution used to print the bar code to increase crispness of the bar code and hence the reading accuracy rate. A slight adjustment in dpi can make a significant difference. Please note that increasing the dpi resolution may also create noise. You must determine the best procedure for your unique conditions.
• Print the bar code directly onto a page.
• Never affix bar codes to a page using tape. Tape interferes with the scanner’s ability to detect the bar code.
• Larger bar codes are read more accurately and tolerate skew better
• Photocopies can show speckles that can interfere with bar code detection. Use a bar code that is printed with a laser printer to ensure a crisp copy. Improving Bar Code Reading Accuracy Adjusting your scanner can improve the success and accuracy of bar code detection. Check your scanner manual for tips to improve quality. The following conditions contribute to the accuracy reading rate and speed of detection of bar codes. By adjusting these parameters, you may control the accuracy and detection speed of bar codes.

Bar Code Height Setting
The Height setting is the distance between the top of the bar code and the bottom of the bar code. The minimum bar code height (of the entire bar code) is approximately 0.15 inch, and the maximum is 1.25 inch. However, a taller bar code has a better chance of being successfully read. By increasing the search height, the speed increases while reading accuracy decreases. By decreasing the search height, the speed decreases while the reading accuracy increases.
Bar Code Length Setting
The Bar Code Length is the minimum number of bar code characters that must be found before the bar code is processed. You specify the bar code length in the Min. Chars per bar code field. Bar Code Length applies to the following bar code types:
• Codabar
• Code 128
• Code 93
• Interleaved 2 of 5
• Code 39 (Code 3 of 9)
• Linear 2 of 5
A bar code is read more accurately and quickly if it has fewer characters. As the number of characters increases, there is a higher chance for error.

For example, a 3-character Code 3 of 9 bar code contains 50 elements, while a 10-character Code 3 of 9 bar code contains 120 elements. The 3-character Code 3 of 9 bar code has a higher probability of being read successfully and quickly. The following bar codes are fixed-length bar codes. Any value in the Min. chars per bar code field
is ignored.
• UPC-A
• UPC-E
• EAN
• Postnet
• Maxi code
Bar Codes with Thin Bars When the width of the smallest element is composed of 3 or less pixels, the detail may not be distinguished.
Width Setting
The Width is the physical width of the smallest element within the bar code. You can alter width settings slightly to work with other bar code settings. Adjust the width setting from a minimum of 0.010 inch to a maximum of 0.050 inch. Most bar code widths fall within the following ranges:

Because the larger elements of the bar code are calculated from the smallest using the ratio value. it may be necessary to adjust the ratio value as well.
Note that when the width of the smallest element is composed of 3 pixels or less, the detail may not be distinguishable. For the best accuracy rates, set the width of the barcode as close as possible to the actual width.
Ratio
Ratio is the ratio of the sizes of the large elements to the small elements of the bar code. When the ratio is large, the bar code is easiest to read. The ideal ratio is 3:1, indicating that the width of the largest element is three times larger than the narrowest element. Because the bars in a bar code can lose pixels during the scan process, smaller ratio bar codes, such as 2:1, are harder to detect. When using the ratio setting, you must also consider the Width parameter.
For example, if the width of the narrowest bar is 0.020 inch, the width of the largest bars would be 0.040 for a 2:1 ratio or 0.060 for a 3:1 ratio. You must decide which ratio and bar code width would give you the desired result based on all your operating conditions.

By default, many bar code types use a ratio of 3:1. The option to select a ratio of 2:1 is available for some bar code types. The following bar code types can make use of the ratio setting:
• Codabar
• Code 39
• Code 93
• Linear 2 of 5
• Interleaved 2 of 5
Maximum Bar Codes per line
The Maximum bar codes per line controls the maximum number of bar codes that appears along the same axis (row or column). The search continues along the same axis until the edge of the image is detected or the specified number of bar codes is encountered. The best performance is obtained when you use only one bar code per line, thus minimizing the duration of the search performed.
Maximum Bar Codes per page
The Maximum bar codes per page should always be set to the number of bar codes that may actually appear on your documents. Because the scanner or software searches the entire page, the system slows down if you specify a large number of barcodes. You may use a maximum of 64 bar codes per page.
Search Direction
The Search Direction determines which directions are used to search for bar codes. Select only the orientation directions that are required. With the minimum number of directions set, a faster search occurs because there are fewer directions to search. If you choose to search all four directions for bar codes, there is a large performance degradation.
Bar Code Types
The Bar Code Type determines what type of bar code to search for. You can select more than one bar code type, but you should select only the bar code types that you actually use. The more bar code types you select, the longer it takes to process each page. Some bar code types are mutually incompatible, and you cannot select their types together. The incompatible combinations are:
• Interleaved 2 of 5 and Linear 2 of 5
• UPC-A and EAN
• UPC-A and UPC-E
• Postnet and any other type
Quality
If you are processing bar codes that are smooth and free of noise, set the Quality to Good. Bar codes that are of lesser quality require the Normal or Poor setting. The Quality setting and the Height setting determine the number of searches for bar codes that are made within an area or page. For instance, increasing the bar code height and a lower quality setting causes the bar code driver to perform more searches for bar codes. The following conditions also contribute to increasing the accuracy reading rate and speed of detection of bar codes:

Edge Noise
Edge noise describes bar codes containing bars that have rough edges. This occurs when the bars acquire or drop pixels, causing a blurred bar. If the ratio setting is small, and the elements gain or lose a pixel during scanning, the ratio setting may decrease further making the bar code difficult to read. It is best to minimize Edge Noise by improving the quality of the bar code image you are using, for instance by increasing print resolution (dpi) when you print bar codes.

Quiet Zones
A quiet zone is the area immediately preceding the start character and following the stop character, which should contain no marking. A bar code must be surrounded by a noise-free quiet zone of at least 1/10 inch; a 1/4 inch area is best. A quiet zone provides a period in which no lightto- dark or dark-to-light transitions occur, making it easy to differentiate a bar code from other information. Position bar codes away from the edge of an image, making sure there are no extraneous marks within the quiet zone. Clean quiet zones, also called margins, improve the readability of the bar code image.
Speckling
Speckling refers to small pixels around the bar code region. This problem becomes serious when the pixels near a bar code interfere with the detection of quiet zones. Use the Despeckle function, if available, before you start searching for barcodes to eliminate extraneous pixels in the bar code area. You can also reduce the interference that is caused by debris on the scanner glass by cleaning it prior to scanning the bar code.
Skew
Even though scanners are capable of reading skewed bar codes, there are more detection
problems with heavily skewed bar codes. It is best to apply the bar code to the page correctly. However, you may also apply the Deskew function, if available, before you start searching for bar codes.
Paper Feed
Ensure that the page is feeding correctly into the scanner to minimize skewing. Also keep in mind that it takes longer to search along the longer side of a piece of paper for bar codes than to search the shorter side.
Using Bar Codes with Faxes
It is possible to process bar codes on inbound fax images using Capture. Note that the resolution and overall quality of the fax image must be very good. The originating and receiving fax machines must be configured carefully. Additionally, you must install DocProcessing on the receiving Capture workstation. You will need to try different settings when configuring your fax machine and Capture to ensure best results.
Fax Machine Settings
Ensure that the sensitivity of the sending fax machine is set on the most sensitive setting. For some fax machines, this may be called Details. For others, the designation may be Fine or Superfine.
Capture Bar Code Settings
Because the faxed bar code is entered into Capture as a TIFF image, the DocProcessing
component is responsible for processing the bar code information. As a result, you must configure the bar code parameters in the Bar Code tab of the Doc Processing Properties dialog box. Set the Quality setting to Poor and make sure that the remaining settings for the bar code you are using are correct.

Using Bar Codes In Capture
In Capture, bar codes can be used to optically acquire such information as account numbers,Invoice numbers, and dates. Bar codes can also be used to trigger events, in much the same way as patch codes are used.
Bar Code Dates
Data fields obtained from bar codes are stored as strings. You can use string selection in the Index component of Capture to change a string date collected from a bar code into a date field against which computations can be performed. When bar codes are used for auto indexing, the date mask format of the bar code must be the same as the format in the date field. When preparing bar codes for autoindexing, use bar code date formats that are supported by Capture, and consider using one of Capture’s four-digit year formats.
If a two-digit year format is used in a bar code, the century selected for the date field applies to the date. This is true whether the century is the default current century or the stated century. Capture cannot obtain the century from the scanned date since the scanned date is stored as a string, not a true date. To create bar codes from which dates can be read:

• Match the date formats of the bar codes to the formats supported in Capture.
• Use a four-digit year format in the bar code. This action will make sure that the Capture uses
the correct century.

Supported Bar Codes
The following examples of bar codes are for definition and clarification only. Note that these example bar codes are not to scale and are unsuitable to use as test samples.
-----------------------------------------------
Standard (One-Dimensional) Bar Codes
-----------------------------------------------
The following bar codes are supported in all Capture releases.
Codabar
Codabar is a self-checking, variable-length bar code that can encode sixteen data characters (0 through 9, plus six special characters). Each character is represented by seven elements within the bar code (four bars and three intervening spaces). An intercharacter gap separates each character within the bar code. Codabar symbols can vary in length. Codabar is useful for encoding dollar quantities and mathematical figures.
Code 3 of 9 (39)
Code 3 of 9 is an alphanumeric, self-checking, variable-length bar code that uses five black bars and four white bars to define a character. Three bars are wide and six are narrow. A character is represented by nine elements. An intercharacter gap separates each character. Start and stop characters are depicted as asterisks (*) and are used to delineate the bar code. The bar code is preceded and followed by quiet zones. A check character is optional. Code 3 of 9 supports 26 uppercase letters, 10 digits, and 7 special characters which include:
- . $ / + % (space)
Code 93
Code 93 is a variable-length bar code that encodes 47 characters. Each character is composed of nine elements arranged into three bars with their adjacent spaces. Code 93 is a compressed version of Code 3 of 9.
Code 128
Code 128 is an alphanumeric, high-density, compact, variable-length bar code that can encode the full 128-ASCII character set. Each data character is represented by six elements. There must be an even number of black elements and an odd number of white elements.
EAN
EAN is used for products that are required to be identified by their country of origin. It is a fixed length bar code that can encode 13 characters. The first two characters identify the country of origin, the next 10 are data characters, and the last character is the checksum. It is a superset of the UPC-A character set. EAN is incompatible with UPC-A.
Interleaved 2 of 5
Interleaved 2 of 5 is a high-density, self-checking numeric bar code that uses five black bars and five white bars to define a character. Two digits are encoded in every character—one in the black bars and one in the white bars. Two of the black bars and two of the white bars are wide. The other bars are narrow. Each Interleaved 2 of 5 bar code must contain an even number of encoded digits and must be of a fixed length. A check character is optional.
-78/43
AA7777
Postnet
Postnet is the Zip+4 postal bar code that is placed on envelopes or postcards to expedite delivery. Each code may consist of five, six, nine, or twelve digits plus a correction code. Note that the Postnet bar code is not compatible with other bar code types and there may be only one per page.
UPC-A
UPC-A is a bar code that encodes a twelve-digit number. The first digit is the number system character. The next ten digits are data characters. The last digit is the checksum. This is the standard bar code used on merchandise to identify the product and manufacturer. UPC-A is incompatible with EAN.
UPC-E
UPC-E is a bar code that is a zero-suppressed version of UPC-A. The data characters and checksum are compressed into six characters. The original ten data characters must have at least four zeros and the number system must be zero.