SAS Tips

“Windows could not start the SAS config-lev1 cache locator on port 41415 service on local computer

Error 1067: The process terminated unexpectedly.”

This error can occur due to a number of reasons, the following are the possible causes:

1) When the SAS 9.4 Cache Locator process runs and is terminated before it can clean up the .locator file

To resolve this issue:

a)Navigate to the SAS-configuration-directory/Lev1/Web/gemfire/instances/insNNNNN directory to confirm that the .locator and locatorNNNNNstate.dat files exist. Make sure to 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).

b) Delete the .locator and locatorNNNNNstate.dat files.

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

2) In SAS-configuration-directory/Lev1/Web/gemfire/instances/insNNNNN/wrapper.log file you can see this error msg:

java.lang.IllegalArgumentException: The bind-address “XX.XX.XX.XXX” is not a valid address for this machine. These are the valid addresses for this machine: [/XX.XX.XX.XXX]

To resolve this issue:

a) You need to ensure that the parameter shown below is set in the location “SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/conf/warpper.conf”  appropriate to your operating environment:
-Dsas.cache.locators=virtual-DNS-host-name_compute-tier[41415],virtual-DNS-host-name_middle-tier[41415]

Note: If you have more than one web application server instance (for example, SASServer2_1, SASServer11_1, etc.), make sure to implement these changes for those web application-server instances as well.

Note: Replace virtual-DNS-host-name_compute-tier with the fully qualified virtual DNS host name of the compute-tier machine. (Or, in some cases, you need to replace it with the fully qualified virtual DNS host name of the machine on which the Web Infrastructure Platform data server is running.)

Replace virtual-DNS-host-name_middle-tier with the fully qualified virtual DNS host name of the middle-tier machine.

In this file, add the argument above to the section that is labeled # Java Additional Parameter

b) In addition, add the Java virtual machine (JVM) argument that is shown below to the JVM_OPTS arguments in the location “SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/conf/warpper.conf” that is appropriate to your operating environment.
-Dgemfire.bind-address=IP-address

Note: If you have more than one web application server instance (for example, SASServer2_1, SASServer11_1, and so on), make sure to implement these changes for those web application-server instances as well.

In this file, add the argument above to the section that is labeled # Java Additional Parameter

c) Add the additional JVM argument that is shown below to the JAVA_ARGS option in the location “SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_41415/wrapper.conf” that is appropriate to your operating environment.
-Dgemfire.bind-address=IP-address

In this file, add the argument above to the section that is labeled # Java Additional Parameter

d) Start the Cache Locator on your SAS server machine. Check the gemfire.log file to make sure that the locator starts successfully.