In some cases, SAS Remote Services fail to stop completely. As a result, ports are still in use and usually a process is still active. (Note: This problem has been observed in UNIX operating environments, and it is possible that the problem might happen in Microsoft Windows operating environments as well.)

Subsequent attempts to restart the services also fail. If they do not start, check the log for messages similar to the following:

com.sas.services.ServiceException: RMI - unable to bind remote object null to com.sas.services.storedprocess.StoredProcessService since a service is already bound by that name. [ java.rmi.AlreadyBoundException: com.sas.services.storedprocess.StoredProcessService ] 
	at com.sas.services.deployment.RMIDeployableService.deploy(RMIDeployableService.java:439)
	at com.sas.services.deployment.RMIDeployableService.deploy(RMIDeployableService.java:255)

. . .more message lines. . .

Caused by: java.rmi.AlreadyBoundException: com.sas.services.storedprocess.StoredProcessService
	at sun.rmi.registry.RegistryImpl.bind(Unknown Source)
	at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
	at sun.rmi.server.UnicastServerRef.oldDispatch(Unknown Source)

In the messages above, you can see that the SAS^® Stored Process Service failed, but you might find that other services fail as well.

Under UNIX, you can find running instances of SAS Remote Services by submitting the following ps command:

Once you locate any active services, you can terminate them with the kill -9 command. After you confirm that all instances of the services have stopped, you can restart the services normally.

Operating System and Release Information