Documentation Center

Troubleshooting the crawler service

If the crawler service does not run after the installation, you can unregister and register the crawler service to fix this issue. It should be done using Invoke-ISHFullTextIndexMaintenance cmdlet available over ISHDeploy module.

Before you begin

Procedure

  1. Login into the server as an Administrator user.
  2. In a Powershell command shell, enter the following command:
     Invoke-ISHFullTextIndexMaintenance -ISHDeployment $deployment ISHDEPLOYMENT -UnRegister

    to unregister all crawlers, where ISHDEPLOYMENT is the deployment you want to use. (If you have only one deployment, you can omit the -ISHDeployment parameter and its value.)

  3. In a Powershell command shell, enter the following command:
     Invoke-ISHFullTextIndexMaintenance -ISHDeployment $deployment ISHDEPLOYMENT -Register

    to register crawler, where ISHDEPLOYMENT is the deployment you want to use. (If you have only one deployment, you can omit the -ISHDeployment parameter and its value.)

  4. If running registering Crawler results in an error message saying, System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout, you can fix this problem by increasing the maximum timeout in the machine settings of the application server. To increase this timeout, do the following:
    1. Go to %WINDIR%\Microsoft.NET\Framework\v4.0.30319\Config\.
    2. Open machine.config for editing.
    3. Ensure that the <configuration> section contains a <system.transactions> subsection, which in turn contains a machineSettings subelement with a maxTimeout attribute. Ensure that that attribute has the value 01:00:00. The resulting <system.transactions> should look as follows:
      <system.transactions>
        <machinSettings maxTimeout="01:00:00" />
      </system.transactions>
    4. Save and close machine.config.
    5. Run again.
     Invoke-ISHFullTextIndexMaintenance -ISHDeployment $deployment ISHDEPLOYMENT -Register