Troubleshooting upgrade problems

Analyzing installation logs

If something goes wrong during the upgrade, first analyze the installation logs. See the Installation problems article for more information on how to use logs to spot and fix errors.

Recovering from project backup

If some projects have not been upgraded correctly, it's possible to restore them from a backup. This can be easily done by opening the local backup of your FlexiCapture project and uploading it to the server via the Project Setup Station.

Important! If the original project is still on the server but is broken or corrupted, be sure to delete it first.

The following FCAdminTools sample command can be used:

UploadProject /Source="D:\Projects\FCProject" /Target="https://FCSRV" /U=user /P=password /CopyTrainingSamples

It uploads a project and the contents of its training batches to the server.

Recovering from file storage and database backups

If the FlexiCapture installation is experiencing problems after the upgrade, it's possible to restore the previous version from a full backup. For more information, see the Restoring your system section in this article.

Upgrading the database manually

If the regular upgrade method in the Administration and Monitoring Console fails, be sure to run Internet Explorer as administrator and try again. If the upgrade still fails, it's possible to carry out the upgrade manually if there is access to SQL Management Studio. First, check the current FlexiCapture database version in the dbo.Settings table. Then check the following path to find the needed SQL upgrade command:

(AppServer): C:\inetpub\wwwroot\FlexiCapture12\Server\Upgrade*.sql

Reconnecting to a restored system backup

If you are experiencing problems with the file storage or database after the upgrade, it's possible to restore them from a backup. Once the database is restored, connect to the database using the Administration and Monitoring Console and update it to the required version. For details, see the Connecting to a database created in an earlier version of ABBYY FlexiCapture section in this article.

Fixing FlexiCapture for Invoices upgrade issues

Generally, no problems should arise when upgrading FlexiCapture for Invoices if the standard interface is used to adjust country and language settings, create new fields and validation rules, etc.

However, if the code of existing rules or a global rule script module has been modified, customizations may be lost during the upgrade.

If the validation rule structure has been modified significantly where any of the following has been changed:

  • number of elements
  • execution order
  • launch conditions
  • rule names (including tags), etc.

then you should thoroughly investigate all errors and warnings generated by the program during the project upgrade and copy code snippets from the old Document Definition to the new one so that they are not lost in the process.

If the invoice processing Document Definition has been significantly customized and you are satisfied with its behavior, then simply delete the new Document Definition created by the upgrade and reinstate the YourDocDefName_old Document Definition instead. Remember, however, that the new version of the Document Definition also contains an upgraded version of the embedded FlexiLayout used for searching for field regions. If you discard the changes to the Document Definition or reinstate the old version of the Document Definition, the FlexiLayout will not be upgraded.

Verification Station and Scanning Station performance issues

If there are specified custom Application Pool Users in IIS or custom Application Pool Settings such as Maximum Worker Processes, it will be needed to reconfigure such settings manually after the upgrade, because the upgrade will overwrite the configuration files containing the custom settings. (For example, all custom Application Pool Identities will be reset to the default value of NetworkService.)

If some Document Definitions remained unpublished before the upgrade

Unpublished Document Definitions will not be updated by the normal project upgrade procedure. This will be recorded in the upgrade log. In order to use such Document Definitions after the upgrade, you will need to update them manually in the Document Definitions dialog box:










Have more questions? Submit a request



Please sign in to leave a comment.