This usually only happens on diskless/dataless clients. You installed a new kernel jumbo patch on the server that exports /usr to the client and failed to read the note in the patch readme that says:
NOTE: If this patch is applied to a server, it should
also be applied to dataless clients that also
mount /usr from that server. Failure to do so will
generate this error message when openwin is started
on the client: "Binding Unix socket: Invalid argument".
The fix is to apply the same kernel jumbo patch to the client.