While requesting a build of an event handler, the following message may be displayed if the script manager could not start:
An error occurred while communicating with the script manager. Socket Error - Socket not connected.
If you are debugging an event handler and the debugger stops at a breakpoint, you can resume the debugger and retry the communication. Otherwise, press Abort to restart the script manager.
If you press Abort and continue to see this error, it is usually due to a port conflict. The default port for the Script Manager is 9653, with a range of 9653 - 9669. Change the port number and try the event handler build again.