The SAS^® Stored Process Server requires use of port 8621. However, if the SAS^® PC Files Server is installed as a service, it might incorrectly use port 8621. If the SAS PC Files Server is incorrectly configured in this manner, the SAS Stored Process Server does not function properly.

The following errors might occur when the SAS PC Files Server uses port 8621 and you run requests that use the SAS Stored Process Server:

• The SAS Object Spawner log file might contain the following message:

  Load balanced server listen port 8621 is in use.
  This may cause future load balanced server launches to fail.
  

• If you attempt to run two SAS^® Stored Processes requests at the same time, the first request might run successfully while the second request fails.
• When you run two requests using the SAS Stored Processes web application, the second request might fail with the following error messages. These errors occur when you use the option _DEBUG=TRACE,LOG when you submit the request.

  >>> Executing stored process object
  
  Stored Process Error
  Unable to execute stored process.
  Unable to connect to a SAS server. 
  
  com.sas.services.storedprocess.ExecutionException: 
  A connection could not be obtained. at
  com.sas.services.storedprocess.Execution2.(Execution2.java:250)
  
  Caused by: com.sas.services.connection.FatalConnectionFactoryException: 
  An exception was thrown while receiving the requirements status from 
  the peer.
  
  Caused by: org.omg.CORBA.COMM_FAILURE: An exception was thrown while
  receiving the requirements status from the peer.  vmcid: 0x0  
  minor code: 0  completed: No
  
  Caused by: java.io.IOException: An existing connection was forcibly 
  closed by the remote host
  

• When you execute two requests using the SAS^® Add-In for Microsoft Office, the second request might fail with the following error message:

  An error occurred executing the SAS Stored Process job "<stored process name here>".
  The SAS Stored Process library failed to provide a data set event interface.
  Connection reset by peer.  An existing connection was forcibly closed by
  the remote host.  This normally results if the peer application on the
  remote host is suddenly stopped, the host is rebooted, or the remote
  host used a <hard close>.
  

If you experience any of these errors, you need to stop any processes or applications that are using port 8621, as follows:

1. Stop all of your SAS Stored Process Server processes that run using the SAS General Servers logon account (which, by default, uses the sassrv user ID). If you have any of these processes running that use this account, you can remove them as follows:
   • In Microsoft Windows operating environments, use the Windows Task Manager to stop the processes.
   • In UNIX operating environments:
     1. Submit the following command:
        > ps -ef | grep sassrv

        This command displays a list of your processes that are currently running with the sassrv user ID.

     2. To stop a process, use the following kill command with the name of the process that you want to stop:
        > kill process-name
2. Check to see whether port 8621 is still being used, as follows:
   • Under Windows, issue the following command from a DOS shell:
     > netstat -nao | find "8621"
   • Under UNIX, issue the following command from a UNIX shell:
     > netstat -na | grep "8621"

   If port 8621 is still in use, the netstat command displays that information in a port status list. Otherwise, you should receive no output. If port 8621 is in use, it is being used either by the SAS PC Files Server or by another application. You can tell if the port is used by the SAS PC Files Server if you see the executable file pcfservice.exe or pcfserver.exe listed in the port status.

   If SAS PC Files Server is using port 8621, you need to change it to a different port number. To change the port number, follow the steps outlined in SAS Note 36974, "Changing the default port that the SAS^® 9.2 PC Files Server uses when it is installed as a service."

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Integration Technologies	Microsoft Windows Server 2003 Standard Edition	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows Server 2003 Enterprise Edition	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows Server 2003 Datacenter Edition	9.2 TS2M0	9.3 TS1M0
		Microsoft® Windows® for x64	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows XP 64-bit Edition	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows Server 2008 for x64	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows Server 2003 for x64	9.2 TS2M0	9.3 TS1M0
		Microsoft® Windows® for 64-Bit Itanium-based Systems	9.2 TS2M0	9.3 TS1M0
		Microsoft Windows XP Professional	9.2 TS2M0	9.3 TS1M0
		Windows Vista	9.2 TS2M0	9.3 TS1M0
		Windows Vista for x64	9.2 TS2M0	9.3 TS1M0

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

The SAS® Stored Process Server requires use of Port 8621. However, if the SAS® PC Files Server is installed as a service, it might incorrectly use port 8621. If the SAS PC Files Server is incorrectly configured in this manner, the SAS Stored Process Server does not function properly.

Type:	Problem Note
Priority:	high

Date Modified:	2012-10-25 11:21:30
Date Created:	2010-02-16 17:19:17