This article applies to the following current products, versions, categories and scanners (if applicable):

ProductVersionCategory
AAF3.6 Extraction
AAF3.6 Validation
AAF3.7 Extraction
AAF3.7 Validation
AAF3.8 Extraction
AAF3.8 Validation
CAPTURE6.0Installation
CAPTURE6.1Installation
CAPTURE7.0Installation
INDICIUS 5.x Completion
INDICIUS 5.x Correction
INDICIUS 5.x Recognition
INDICIUS 5.x Scripted Export

 

QAID # 6424

Question / Problem:

Opening any Ascent Capture module results in the following error: "COM error: [7001] AcLicClnt Unable to connect to license server. The license server may be down or the network may have problems. (Index was outside the bounds of the array)"
What can I do to resolve this?

Answer / Solution:

This error will occur if you are using Ascent Capture 6.x or 7.0 with .NET Framework 2.0 or 3.0. This issue became more common when Microsoft Windows XP Automatic Update installed the .NET Framework 2.0/3.0.

If you are using Ascent Capture 7.0, download and install the latest Ascent Capture 7.0 Service Pack from:
Ascent Capture 7.0 Downloads#ServicePacks. This should correct the problem.

If you are using Ascent Capture 6.x, remove .NET Framework 2.0/3.0 from the system.

If removing .NET Framework 2.0/3.0 is not possible, you may use the following Kofax-unsupported workaround.

This workaround involves the use of “.exe.config” files. These files instruct Ascent Capture 6.x to use .NET Framework 1.1 for licensing, allowing Ascent Capture 6.x to coexist with .NET Framework 2.0/3.0.

The files are in XML format, but they can be created as plain ASCII text using a text editor such as Notepad. An exe.config file for each Ascent Capture 6.x module must be placed in the same folder as the executable.

NOTE: Shut down all Ascent Capture 6.x modules before creating and saving these files.

Each file should contain exactly the same information:

<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
</configuration>
Once the first file has been created, save it under each of the following file names:
AciCfgWz.exe
ACXMLAI.exe.config
Admin.exe.config
DBUtil.exe.config
fp.exe.config
Index.exe.config
KfxPdf.exe.config
Ocr.exe.config
ops.exe.config
Qc.exe.config
Release.exe.config
Scan.exe.config
SepSheet.exe.config
Verify.exe.config
On workstations, the files should be placed in the Ascent/BIN folder. On servers, these files should be placed in the AscentSS/ServLib/Bin folder.

Advanced Forms Products

Users of Advanced Forms products such as INDICIUS, Ascent for Payables, Ascent Advanced Forms, or Xtrata, should create additional .exe.config files for each executable used by that product. The config files must be placed in the same directory that contains the executable.

The DOKuStar Validation module (DSVALAC.EXE) calls another executable (DSVAL.EXE). These two executables may be located in two different directories. For example, DSVALAC.EXE may be under Program Files\Ascent\Bin or Program Files\Ascent\Bin\Dokustar. DSVAL.EXE is located under Program Files\ODT-OCE\Ascent Advanced Forms Validation 3.7\Bin. A CONFIG file must be created for each executable and placed into the same location as the executable.

Similarly, The Extraction module (ACDOKU.EXE) calls IDIS.EXE, MIDIS.EXE and IDS.EXE. These three child modules are located under Program Files\ODT-OCE\Ascent Advanced Forms 3.7\Bin and should have corresponding .EXE.CONFIG files.

KPSG Products

Users of KPSG products such as KPSG Auto Import, should create additional .exe.config files for each executable used by that product. The config files must be placed in the same directory that contains the executable.

The executable file names for KPSG Auto Import are:
AutoImport.exe
AutoImportSetup.exe
and should have corresponding .EXE.CONFIG files.

 

Did this content prevent you from having to contact Kofax Technical Support?

Did this content help you?

Kofax Customer Portal