A SAS^® Stored Process Server cannot be started or may suddenly stop working when the client information contains unexpected characters.

The following message will be written to the Metadata Server log file.

If one of your Stored Process Servers is hung, this can cause the "Unable to read the server (server identifier) client update information" information to be written to your Object Spawner's log file. So, check the status of the port numbers that your Stored Process Severs are using (for example, 8611, 8621, 8631, 8601). See SAS Note #012516 for information about checking the status of the port numbers.

This message may also occur if your Stored Process Server was shut down as a result of the "Inactivity Timeout" setting for this server. If this is the case, the Stored Process Server will be restarted automatically and subsequent requests should be executed successfully.

If the problem persists, refer to SAS Note #012516 for tips on diagnosing an unresponsive Stored Process Server.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :