Error code 57

I'm sending a job to a remote agent and getting the following response

11/19/2007 08:48:54 0 324 0 BDI_Load Agent [SERVER] contacted.
11/19/2007 08:48:54 0 324 0 BDI_Load Job started.
11/19/2007 08:48:55 2 324 0 BDI_Load Failed to execute remote job. Uknown error occurred. Error code: 57
11/19/2007 08:48:55 0 324 0 BDI_Load Error message sent.

I have trace running on both agent and master to see what may be happening. The master shows an entry being written to the log file and the remote shows nothing. Any ideas on what error code 57 means?

Thanks for your help,
David

Well, 57 is an unexpected error number, that why the message says "unknown"

Can you post a bit of the trace from the agent that indicates an attempt to establish a new session?

Here is the trace from the master:

Agent: [SERVER]
Input: C:\Program Files\24x7 Automation 3\schedule.log
Date/Time Format: M/d/yyyy h:mm:ss tt
Output: F:\24x7\Reports\html

Loading log file...
Sorting records...
Generating HTML reports...
3006 log records found. Process completed in 1.094 seconds

My mistake on not reading the entire trace log, I was only watching it while I pushed the job to it. It looks like i have a conflict on the ports. Here is the trace from the agent:

Starting distributed service...
SMI10 Listener (00C0F430): Start Listening: computerName(), serviceName(1096),
driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='1096'
SMI AddRef SMI_TRACE(00C0F2E8) refCount(2)
WSD11 AddRef: RefCount for listener object = 1
SMI09 Listener (00C0F430): ERROR OCCURRED: Distributed Communications Error: Bi
nd call failed with error WSAEADDRINUSE, (CC6) (8004200D)
WSD11 Release: RefCount for listener object = 1
SMI Release SMI_TRACE(00C0F2E8) refCount(1)
SMI10 Listener (00C0F430): Start Listening: computerName(), serviceName(1096),
driverName(WinSock). FAILED (8004200D)
DPB30 Listener (00C0F088): Start Listening : application(1096), location(), dri
ver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(3593), total(606208), alloc(376722)
, free(212627)
DPB56 Memory Proc Common : count(1167), total(86016), alloc(66025), free(14597)

Using tcpview (sysinternals) we found out that it was lsass.exe bound itself to the port. We'll reboot the server after hours tonight and see what happens. Thanks for having me post the rest of the trace, I probably would've never read all of it. Have a good day.
David

Glad you found the cause. Did you know that you don't have to use the default 1096 port? You can change it to any free number. Just don't forget to change it on both ends – in agent options (Tools/Options menu; Network tab) and remote agent profile settings in the scheduler (Tools/Remote Agent Profiles)

Yeah, but I have 12 remote agents. It's easier for us to reboot this guy at night then it is to reassign the ports on all the servers. Thanks again for the help.