The SASSearchService.log can get very large (over 50 GB), which fills the hard drive space. When this issue occurs, the SASSearchService.log, located by default in the SAS-configuration-directory/LevN/Web/Logs/SASServer12_1 directory, shows the following error:

To circumvent this issue, ensure that the Search Interface To SAS Content version in SAS^® Management Console matches the version set in the sas.searchsas.softwarecomponent setting in the search_service_config.properties file. 

Note: The directories referenced are for UNIX, but the paths are similar for Microsoft Windows systems.

Check the Search Interface To SAS Content Version

You must check the Search Interface To SAS Content version in SAS Management Console and in the search_service_config.properties file. 

In SAS Management Console

To check the Search Interface To SAS Content version in SAS Management Console, complete these steps:

1. Log on to SAS Management Console using a SAS administrator account such as sasadm@saspw.
2. On the Plug-ins tab, go to Application Manager ► Configuration Manager.
3. Expand Configuration Manager. Note the Search Interface To SAS Content version. For example, the following shows the Search Interface To SAS Content version is 3.71.
   

In the search_service_config.properties File

Complete these steps to check the Search Interface To SAS Content version in the search_service_config.properties file, on each middle-tier system, with its own SASHome directory:

1. Go to the <SASHome>/SASVersionedJarRepository/eclipse/plugins directory.
2. Locate the sas.searchsas_105000.0.0.20190417194610_d4srchr7 directory.
3. Copy the sas.searchsas.jar file in this directory to sas.searchsas.jar.orig to back it up.
4. Copy the the sas.searchsas.jar file to a temporary work directory (such as /temp), and complete these steps:
5. Extract the contents of the JAR file to the temporary directory:

• For UNIX systems, use a command such as unzip to extract the contents of the JAR file. For example, running the following from the /temp directory extracts the contents of the JAR file to the directory: unzip sas.searchsas.jar
• For Windows, rename the unzip sas.searchsas.jar file to unzip sas.searchsas.zip file and use your favorite file compression and management utility such as WinZip to extract the contents of the ZIP file.

6. Go to the /temp/config directory and open the search_service_config.properties file:
7. Search for the following property and note the version: sas.searchsas.softwarecomponent
8. If the version for sas.searchsas.softwarecomponent is different from the results in step 3 in the Using SAS Management Console section, go to the Make the Search Interface To SAS Content Versions Match section.
9. If the version for sas.searchsas.softwarecomponent is the same as the results in step 3 in the Using SAS Management Console section, contact SAS Technical Support.

Make the Search Interface To SAS Content Versions Match

If the versions of Search Interface To SAS Content in SAS Management Console and the search_service_config.properties file do not match, complete these steps:

1. Change the version in the search_service_config.properties file to match the version in SAS Management Console. 
   For example, the following setting is different from the SAS Management Console screen capture provided above: sas.searchsas.softwarecomponent = Search Interface to SAS Content 3.7
   So, in this example, you should change this setting to: sas.searchsas.softwarecomponent = Search Interface to SAS Content 3.71. Then, it will match the version in SAS Management Console.
2. Save the change.
3. Put the file into the sas.searchsas.jar file. In UNIX, for example, run the following from the /temp directory: zip sas.searchsas.jar  "/temp/config/search_service_config.properties"
4. Put the JAR file in the <SASHome>/SASVersionedJarRepository/eclipse/plugins/sas.searchsas_105000.0.0.20190417194610_d4srchr7 directory.
5. Stop SASServer12_1 on each middle-tier node. 
   Note: If you only have one SAS web application server instance, SASServer12_1 is replaced with SASServer1_1 in these instructions. For UNIX systems, run ./tcruntime-ctl.sh stop from the SAS-configuration-directory/LevN/Web/WebAppServer/SASServer12_1/bin directory. For Windows systems, go to the Windows Services dialog box to stop the server.
6. Delete the SASSearchService.log from the SAS-configuration-directory/LevN/Lev1/Web/Logs/SASServer12_1 directory on each middle-tier node.
7. Restart SASServer12_1 on each middle-tier node. For UNIX systems, run ./tcruntime-ctl.sh start from the SAS-configuration-directory/LevN/Web/WebAppServer/SASServer12_1/bin directory. For Windows systems, go to the Windows Services dialog box to start the server.
8. After one hour, check the SAS-configuration-directory/LevN/Lev1/Web/Logs/SASServer12_1/SASSearchService.log for an entry similar to the following: INFO  [sasadm] com.sas.svcs.search.util.SearchServiceManager - AdminClientForBird - IRSTUDIO Configured for SearchService......
   Also, there should be an entry showing indexing taking place with no errors similar to the following: INFO  [sasadm] com.sas.svcs.search.impl.SearchIndexServiceImpl - 2 records extracted for indexing in irstudio engine in 283 ms

Operating System and Release Information