Knowledge Base
      Back to home
      1. Help Center
      2. DC Project Suite
      3. Knowledge Base

      Analysis Process Fails Mid-way, Causing Future Analysis to Fail

      Symptoms

      Analysis fails sporadically, and future runs of the index continue to fail.

      The key indicator will be a message in the "Analysis" log that states the following:

      "System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/Administration that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/Administration' could not be found on your local machine."

       

      Cause

      The Analysis process relies on a sub-process named "ActiveNavigation.Analysis.ConversionThematicAnalysisService (32 bit)" which can occasionally fail due to startup timeout issues.

      Resolution

      This issue was resolved in Discovery Center 4.8.0
      We recommend upgrading rather than changing the configuration as described below.

      1) Someone with access to the Discovery Center application must confirm that there is no analysis running at the time of resolution within Discover Center before proceeding.

      2) If there is no current activity, the next step would be to log into the server running the Discovery Center application and in the task manager program, check for the Active Navigation Conversion Thematic Analysis process 32 bit.

      mceclip0 (4)

      3) If this process is still running after the analysis has failed, you must end it in task manager before proceeding.

      4) Once this process is stopped, the user will navigate to the installation directory of Discovery Center on the application server, typically found under program files. Within the sub-folder named "Analysis", locate a file named "ANAnalysis.exe.config"

      5) Edit this file in a program like notepad, and find the section underlined below:
      <add key="ConvertThematicAnalysisMaxServiceStartupAttempts" value="5"/>

      6) Change the value from 5 to 10.

      7) Finally, the user can re-initiate the analysis job in Discovery Center, and monitor its progress.

      *Note that if you have Re-skim enabled in the related index configuration, you would have to wait for the skim again, which you might want to avoid. If so, update the related index configuration to not re-skim for this specific case.