Skip to main content
Work through these checks when you suspect a problem with the Application Server. Each step assumes the previous one succeeded.

​
Verify that the Application Server responds

1

Open the IIS starting page

On the machine where the Application Server is installed, go to https://localhost or https://127.0.0.1. The IIS starting page should appear.
If the page does not open, IIS itself is at fault. Verify that the IIS server is running. If it is running but not working, see the IIS documentation.
2

Open the WSDL endpoint

Go to https://localhost/FlexiCapture12/Server/API/v1/WSDL. A page of XML code should appear.
If the page does not open, check the following:
  • In the IIS settings, confirm that the Application Server has been launched.
  • Verify that your machine satisfies the minimum system requirements.
  • Check the error messages in the system log on the Application Server machine.
If none of that restores the Application Server, contact ABBYY technical support with:
  • The web.config files from C:\inetpub\wwwroot\FlexiCapture12\Server, C:\inetpub\wwwroot\FlexiCapture12, and C:\inetpub\wwwroot
  • Any messages shown when you tried to open the IIS starting page
  • System log messages
3

Reach the Application Server from another machine

From a different machine, such as one running a Processing Station, open https://AppServer.If that page does not open, access to the Application Server machine is blocked. Incorrect firewall or proxy settings are the usual cause.

​
Extended Application Server diagnostics

Failed request tracing saves information about Application Server errors automatically. For setup instructions, see the IIS documentation on failed request tracing.