FlexiCapture Distributed - IIS crashed, doesn't come back up properly after reboot

  • 592 Views
  • Last Post 12 July 2018
Yehuda Goldenberg posted this 03 July 2018

Please see my previous posts for how I got to this point:

http://www.capturedocs.com/thread/api-does-not-seem-to-be-able-to-detect-projects/

http://www.capturedocs.com/thread/addnewbatch-fails-with-generic-error-message/

http://www.capturedocs.com/thread/error-from-fileservice/

 http://www.capturedocs.com/thread/document-uploaded-via-api-or-via-scanning-station-is-not-available-to-verify/

 

The resolution for the upload issue was that I needed to use UTF-16LE encoding for the stream name. (See previous discussion.) I know this is correct because I was looking at the file store and whenever the file was uploaded, the name of the file had Chinese characters. After I changed the encoding, the file name was correct. I had windows explorer and the processing server monitor open and I saw that the processing server was processing the file. Then I got a popup that w3wp crashed. This popup came up several times.

Here's the error from the event log:

Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000287d38402a0
Faulting process id: 0x11d8
Faulting application start time: 0x01d412f23ccc36d0
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: unknown
Report Id: 05547c98-8d61-49ab-80d3-42a1ab759e90
Faulting package full name: 
Faulting package-relative application ID: 

I tried visiting the administration and monitoring console and I got the yellow screen of death. It also logged the following in the event log (host names and ip addresses removed):

 

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 7/3/2018 1:43:23 PM 
Event time (UTC): 7/3/2018 5:43:23 PM 
Event ID: 13c6bbd5ec35435ab7f297c214a837de 
Event sequence: 4 
Event occurrence: 1 
Event detail code: 0 

Application information: 
    Application domain: /LM/W3SVC/1/ROOT/FlexiCapture12/Login-1-131751134009347340 
    Trust level: Full 
    Application Virtual Path: /FlexiCapture12/Login 
    Application Path: C:\inetpub\wwwroot\FlexiCapture12\Login\ 
    Machine name: hostname 

Process information: 
    Process ID: 5668 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 

Exception information: 
    Exception type: InvalidOperationException 
    Exception message: The model item passed into the dictionary is of type 'System.Web.Mvc.HandleErrorInfo', but this dictionary requires a model item of type 'Abbyy.FlexiCapture.WebCommon.ServerTools.ErrorModel'.
   at Abbyy.FlexiCapture.LoginStation.VerificationApplication.Application_Error()



Request information: 
    Request URL: https://hostname:443/FlexiCapture12/Login/ 
    Request path: /FlexiCapture12/Login/ 
    User host address: x.x.x.x 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE 

Thread information: 
    Thread ID: 6 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Is impersonating: False 
    Stack trace:    at Abbyy.FlexiCapture.LoginStation.VerificationApplication.Application_Error()


Custom event details: 

I tried rebooting the server and I still got the yellow screen of death and the error in the event log. Also the processing server keeps restarting and logging the following to the event log:

 

FlexiBr: Processing Server restart: An error occurred while creating Application Server session: Cannot connect to 'http://hostname' (error code: (HTTP 503, 19, 0))..

Order By: Standard | Newest | Votes
AlexeyEfremov posted this 05 July 2018

Hello,

Please try the following:

In the Application Pools > FC 12 Web Services > Advanced Settings > Identity set Network Service and restart the pool.

If the Web Services will not start, try to change the Identity to Custom account.

 

 

If this does not help you, please contact the regional support. Here are the questions that will help them to investigate the issue:

1. gather the IIS logs

2. Get the dump with ProcDump

https://docs.microsoft.com/en-us/sysinternals/downloads/procdump

3. Which version of С# Redistributable is installed?

4. An exact version of your FC12: Project Setup Station > Help > About.

 5. Your FlexiCapture  project (Project Setup Station > Open Project from Server > Project > Export project):

 6. Ainfo diagnostic files from all the FlexiCapture machines:

 - Run AINFO.exe file from the program installation folder: ABBYY FlexiCapture 12.0 Servers\Support or  ABBYY FlexiCapture 12.0 Stations\Support;

 - Click "Save as";

 - Send us AINFO.zip.

 

 

7. Are your machune real or virtual?

8. Windows Application and System logs: 

 - Go to Control Panel > Administrative Tools > Event Viewer.

- From the log tree, select the "Application"/"System" item.

- From the "Action" menu, select the "Save log file as..." item.

- Save the *.evtx file, zip and send it to us.

 

9.  *.NFO-file which contains information about using system. You can find this file launched from the command line msinfo32 > menu File > Save As.

 

 

Yehuda Goldenberg posted this 12 July 2018

Here's how to clear the document after the crash...

First make sure the processing station is not set to start automatically.

  • In IIS Manager, under "Application Pools", start "FlexiCapture 12 Web Services" if it is not already started.
  • Log into the FlexiCapture "Administration & Monitoring" console.
  • Select "Processing Monitor", then "Sessions".
  • Select all sessions, then click "Delete".
  • Click on "Batches". Scroll to the end of the list if necessary. Find the offending batch, select it, and click "Delete".
  • You should now be able to start the processing station without having it crash.
  • If it still crashes, verify that the offending batch was deleted. You won't be able to delete it if there is an open session connected to that batch.

This still does not address what caused it to crash, but at least I can recover and move on.

Close