10.0
Table Of Contents
- Installing ABBYY FlexiCapture 10
- Standalone Installation
- Distributed Installation
- System Requirements
- General information
- Preparing the Application Server for installation on Windows 2012
- Preparing the Application Server for installation on Windows Server 2008 R2
- Preparing the Application Server for installation on Windows 2003
- Installing the servers
- External components required for the correct operation of the system
- System components in IIS and their configuration
- This section describes the IIS configuration which is necessary for the operation of FlexiCapture. This configuration is configured automatically during installation and required no manual configuration. However, in case of errors this section can help you to check the settings specified in IIS.
- Application pools
- Authentication settings for FlexiCapture 10 Web Applications
- Handler Mappings
- ISAPI and CGI Restrictions
- Checking the operation of IIS
- Switching system components to 64-bit mode
- Database server
- Interaction of the system components
- Installing the stations
- Using Active Directory
- Using SMS
- Installing Remote Stations
- Updating your earlier ABBYY FlexiCapture 10 releases to Release 6
- Upgrading from ABBYY FlexiCapture 9.0
- Upgrading from ABBYY FlexiCapture 8.0 Professional
- Upgrading from ABBYY FormReader 6.5
- Managing Your Licenses
- Setting Up FlexiCapture 10 Distributed Installation
- Logging
- Working with Clusters
- Technical Support
© 2011 ABBYY. All rights reserved.
20
During installation, Windows may require files from the setup disk, therefore be sure to have the Windows disk ready at hand.
If any of the components is missing on your computer, the setup program will display a warning message and the installation of
the Application Server will stop.
Once the installation is complete, open the Administrator Console and make sure that the IIS service is running.
Important! In Windows 2003 ASP.NET is disabled by default for security reasons. This will cause “Error 404 File not found”
when you attempt to start the Monitoring Station. To solve the problem, allow the ASP.NET v4.0 service extension in the IIS
Manager: