The following error can occur when executing a stored process that produces graphics output:

Stored process did not run successfully: 
Generic IOM error occurred.!

When the stored process fails, the back-end SAS^® Stored Process Server or Workspace Server might terminate abnormally or not respond. If this problem occurs, the server log will contain a "Write Access Violation In Task [ xxxx )" error message, with various tasks reported in the error. The traceback for the Write Access Violation error begins with task traces from the sasxkern routine.

Check the log for the SAS client application (if one is produced) for an error similar to the following:

SAS 19:42:26,190 ERROR [SAS Demo User] com.sas.services.storedprocess.Execution -
 Generic IOM error occurred. org.omg.CORBA.COMM_FAILURE: sam.S235.ex.msg: An 
 exception was thrown while reading a packet header from the socket.  vmcid: 0x0 
 minor code: 0  completed: No

This problem has been reported to occur when GOPTIONS DEVICE=ACTIVEX is specified in the autoexec file for the server and GOPTIONS DEVICE=ACTXIMG is specified in the stored process code.

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: