> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Web Station error diagnostics

> Diagnose ABBYY FlexiCapture Web Station errors with and without HTTP codes, using the Developer console, Web Station and Fiddler logging, and license checks.

## Errors without HTTP error codes

Some Web Station errors carry no HTTP error code such as 400 or 500. Collect the browser console output for those.

<Steps>
  <Step title="Open the Developer console">
    Press **F12** and go to the **Console** tab.

    <Frame>
      <img src="https://mintcdn.com/abbyy/XVEmG3cTpHwMKf5X/images/flexi-capture/TG_Proccessing_WebStation_1.png?fit=max&auto=format&n=XVEmG3cTpHwMKf5X&q=85&s=7151f63269121467feb2c29bdd55333d" alt="Screenshot of the browser developer tools open at the Console tab on the Web Station." width="864" height="583" data-path="images/flexi-capture/TG_Proccessing_WebStation_1.png" />
    </Frame>
  </Step>

  <Step title="Copy the error list">
    Copy everything the console displays.
  </Step>

  <Step title="Enable logging and reproduce the error">
    Turn on logging for the Web Station that displays the error, then reproduce it. For more information, see [Web Station logging](/flexi-capture/troubleshooting-guide/tg-logs-web-station).
  </Step>

  <Step title="Contact ABBYY technical support">
    Send the error list from the **Console** tab together with the Web Station log files.
  </Step>
</Steps>

Errors of this kind include a document layout that will not display in full or in part when you take a job, and `Parameter cannot be null.`

## Errors with HTTP error codes

Other errors appear in a window with an HTTP error code, for example `Error 400: bad request` or `Error 500 while completing task`.

<Steps>
  <Step title="Check the Application Server system log">
    Look for errors recorded around the time the Web Station error appeared.
  </Step>

  <Step title="Enable the logging that matches the error">
    If the error is intermittent, enable logging on the Web Station that reports it. For more information, see [Web Station logging](/flexi-capture/troubleshooting-guide/tg-logs-web-station).

    If the error reproduces reliably, enable Fiddler logging instead. For more information, see [Fiddler logging](/flexi-capture/troubleshooting-guide/tg-logs-fiddler).
  </Step>

  <Step title="Contact ABBYY technical support">
    Send the Web Station logs and the Fiddler logs covering the period when the error occurred.
  </Step>
</Steps>

## The `Cannot get license ticket` error on Web Stations

This error can appear when you open a job, or when you try to scan or add an image to a batch.

<Frame>
  <img src="https://mintcdn.com/abbyy/XVEmG3cTpHwMKf5X/images/flexi-capture/TG_Proccessing_WebStation_2.png?fit=max&auto=format&n=XVEmG3cTpHwMKf5X&q=85&s=f7101e175c1ad60350268fe8fb07dce0" alt="Screenshot of the FlexiCapture Verification Web Station showing a No License page with the message Cannot get license ticket and a Return to list of projects button." width="1006" height="642" data-path="images/flexi-capture/TG_Proccessing_WebStation_2.png" />
</Frame>

To resolve it, check that:

* The Processing Server is running.
* Free licenses are available. To check, launch the License Manager, select a license, and go to **Service → License Usage Statistic** in the main menu.

<Frame>
  <img src="https://mintcdn.com/abbyy/XVEmG3cTpHwMKf5X/images/flexi-capture/TG_Proccessing_WebStation_3.png?fit=max&auto=format&n=XVEmG3cTpHwMKf5X&q=85&s=e8f0c9873824e1ede080c66697b55bb7" alt="Screenshot of the License Manager main menu with Service, License Usage Statistic selected." width="839" height="311" data-path="images/flexi-capture/TG_Proccessing_WebStation_3.png" />
</Frame>

If all licenses are in use, look for frozen sessions holding them. Open the **System Monitoring → Sessions** page in the Administration and Monitoring Console.