An InTrust agent consistently fails to start on a Windows machine, and you find the following error in the local Application event log:
InTrust agent stopped unexpectedly. Error occurred: An attempt was made to access a socket in a way forbidden by its access permissions. (Win32 error: 10013).
or the following error from the agent process is written to syslog on the Unix machine hosting an InTrust agent:
InTrust agent stopped unexpectedly. Address already in use (CRuntime error: 98).
The port the Agent is trying to access is in use by another process.
If this occurs on the InTrust server itself confirm the Agent port is 900 (default) or using some other specified port. This can be determined from the Organization properties under the top node of InTrust Manager and on the InTrust server properties itself under Configuration | InTrust servers. Both places should be checked to ensure the value is not being overridden from one place or the other.
Once the Agent port is determined check if some other process is using this port ("netsat -ab" command is useful). Dump the active connections to a text file with command like:
netstat -ab > C:\Output.log
Review the file for any processes with local port in use which matches the expected Agent port.
Reconfigure InTrust or the other process to utilize a different port.