When the SAS 9.4 Cache Locator process runs and is terminated before it can clean up the .locator file, the following problems occur based on the operating system of your SAS deployment:

UNIX operating systems:

• The cache locator does not start when you issue a sas.servers start command.
• The cache locator does not stop when you issue a sas.servers stop command.

Microsoft Windows operating systems:

The cache locator does not start when you use the Windows Services application, which results in an error message of the following form:

Windows could not start the SAS [SASConfig-Lev1] Cache Locator on port NNNNN service on Local Computer.

Error 1067: The process terminated unexpectedly.

 

For example, the .locator file is not cleaned up when you restart the physical machine where the cache locator is deployed while the process is running. 

To resolve this issue, complete these steps:

1. Navigate to the SAS-configuration-directory/Lev1/Web/gemfire/instances/insNNNNN directory to confirm that the .locator and locatorNNNNNstate.dat files exist. Note the names of these files.

   Note: Replace NNNNN with the port number for the SAS 9.4 Cache Locator (the default port value is 41415).

2. Delete the .locator and locatorNNNNNstate.dat files.

Once you delete those files, you should be able to start and stop the cache locator.