Error: sp_xport: couldn't write data to socket (4331162)

Errors similar to the following occur:

11/18/06 21:27 Error: sp_xport: couldn't write data to socket [sp_xport/18672]
11/18/06 21:27 System call error: Broken pipe Export write error [sp_xport/18672]
11/18/06 21:27 Error: sp_xport: failed to send message to import - exiting [sp_xport/18672]
11/18/06 21:27 Process exited sp_xport (to axrs17mpar36-bkup.metlife.com queue ssrsphrpg1) [pid = 18672] - exit(1)
11/18/06 21:27 Process launched: sp_xport (to axrs17mpar36-bkup.metlife.com queue ssrsphrpg1) [pid = 4180]
11/18/06 21:31 Cannot connect to host axrs17mpar36-bkup.metlife.com Connection timed out

The TCP/IP port that Shareplex uses is either being used by another application or is blocked.

Try first shutting down Shareplex and restarting it. If the issue is a result of a hung memory port, bouncing Shareplex will resolve the issue. If another application is using the Shareplex port, have Shareplex use another port.

NOTE:
netstat -an | grep <port number> should tell you what is attached to the port number. Ideally, you don't want to see more than one entry. More than one entry indicates that the port has a hung memory segment or another application is using the port.