I'm using 24x7 (v 2.4.7) with a site license to run a very simple executable via Remote Agents. I have set up the Master Scheduler and Agents, and I can verify connections to the Agents, I can even run the job using the "Run Now" test option. But when I schedule the job, I keep getting an error that the agent failed to respond. (Failed to execute remote job. No response to request.)

I've tried tweaking the connection options on both the Master and Agent programs with no luck. Is there somthing I'm missing?

Thanks in advance,
-Kevin Parsons-

Please turn on tracing in Tools/Options (Trace enabled option) and let the job to run on schedule. Let us know what you get in the trace.

: I'm using 24x7 (v 2.4.7) with a site license to run a very simple executable
: via Remote Agents. I have set up the Master Scheduler and Agents, and I
: can verify connections to the Agents, I can even run the job using the
: "Run Now" test option. But when I schedule the job, I keep
: getting an error that the agent failed to respond. (Failed to execute
: remote job. No response to request.)

: I've tried tweaking the connection options on both the Master and Agent
: programs with no luck. Is there somthing I'm missing?

: Thanks in advance,
: -Kevin Parsons-

On both the Master Scheduler and the Agent I'm getting this in the trace...

DPB30 Listener (013FC470): Start Listening: application(10013), location(), driver(WinSock).FAILED(80004005)

The settings on the Master Scheduler are
Driver: WinSock
Port / Service: 10013
Location: 172.17.15.15 (This is the IP of the Master Scheduler Machine)

The settings on the Agent are the same
Driver: WinSock
Port / Service: 10013
Location: 172.17.15.15 (This is the IP of the Master Scheduler Machine)

: Please turn on tracing in Tools/Options (Trace enabled option) and let the
: job to run on schedule. Let us know what you get in the trace.

Most likely port 10013 is already in use. Try a different number, for example try 10099. All agents can listen on the same port.

: On both the Master Scheduler and the Agent I'm getting this in the trace...

: DPB30 Listener (013FC470): Start Listening: application(10013), location(),
: driver(WinSock).FAILED(80004005)

: The settings on the Master Scheduler are
: Driver: WinSock
: Port / Service: 10013
: Location: 172.17.15.15 (This is the IP of the Master Scheduler Machine)

: The settings on the Agent are the same
: Driver: WinSock
: Port / Service: 10013
: Location: 172.17.15.15 (This is the IP of the Master Scheduler Machine)

I've already tried port 10099. I've even tried entering it into the SERVICES file on NT. This had no effect.

: Most likely port 10013 is already in use. Try a different number, for example
: try 10099. All agents can listen on the same port.

If you've entered it into the SERVICES you should use the entered service name instead of the port number, otherwise remove it from the SERVICES file and leave the number as is.

SERVICES file is used to register the number and give it some descriptive name.
The registration doesn't ensure completely number uniqness and non-sharing but still may help to prevent other applications from using the same port number.

By the way, what are the next two lines in the agent's trace window (or agent.log file)?

: I've already tried port 10099. I've even tried entering it into the SERVICES
: file on NT. This had no effect.

Yes I was using the service's name not the number... but I've sinced removed the entry from SERVICES, so I went back to using the number.

When I first start up the Agent, I get...

DPB30 Listener (013FC470): Start Listening : application(10013), location
(), driver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(2497), total(421888), alloc(297265)
, free(113092)
DPB56 Memory Proc Common : count(884), total(86016), alloc(50443), free(30498)

And when I try and run the job I get this (on the Agent still)...

SMI01 Connection(0AA40020): Create Message: (0AD60070), initial size 0 bytes
SMI03 Connection(0AA40020): Send Reply Message: (0AD60070) sequenceNumber(47) As
ynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(0AA40020): Send Reply Message: (0AD60070) sequenceNumber(47) As
ynchronous. SUCCEEDED (00000000)
SMI08 Connection(0AA40020): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(0AA40020): Disconnect: SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(0AA401A0) refCount(1)
SMI Release SMI_CONNECTION(0AA40020) refCount(2)
DPB56 Memory Proc Common : count(1), total(86016), alloc(15), free(81826)
DPB Release DPB_SESSION_SERVICE(0AA401A0) refCount(0)
WSD06 ReadHeader: Received disconnect code = FF
DPB Release DPB_Connection(0AB60760) refCount(0)
SMI Release SMI_CONNECTION(0AA40020) refCount(1)
SMI Release SMI_TRACE(013FB488) refCount(4)
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(0AA40020) refCount(0)
SMI Release SMI_TRACE(013FB488) refCount(3)
SMI Release SMI_LISTENER(013FB398) refCount(1)
SMI Release SMI_TRACE(013FB488) refCount(2)

: If you've entered it into the SERVICES you should use the entered service
: name instead of the port number, otherwise remove it from the SERVICES
: file and leave the number as is.

: SERVICES file is used to register the number and give it some descriptive
: name.
: The registration doesn't ensure completely number uniqness and non-sharing
: but still may help to prevent other applications from using the same port
: number.

: By the way, what are the next two lines in the agent's trace window (or
: agent.log file)?

OK, it appears to be working with the number. Don't pay much attention to "FAILED (80004005)". This message only indicates that some port-in-use test failed.

The job you run from some other place was able to connect to the agent, but then it immediatelly disconnacted from the agent without performing any real processing.

Make the following 2 changes:
1. In the agent profile (on the other computer) properties set connection mode to "synchronous"
2. In the job properties set job to also run as "synchronous" job.

That should help.

: Yes I was using the service's name not the number... but I've sinced removed
: the entry from SERVICES, so I went back to using the number.

: When I first start up the Agent, I get...

: DPB30 Listener (013FC470): Start Listening : application(10013), location
: (), driver(WinSock). FAILED (80004005)
: DPB55 Memory Session : (00000000) count(2497), total(421888), alloc(297265)
: , free(113092)
: DPB56 Memory Proc Common : count(884), total(86016), alloc(50443),
: free(30498)

: And when I try and run the job I get this (on the Agent still)...

: SMI01 Connection(0AA40020): Create Message: (0AD60070), initial size 0 bytes
: SMI03 Connection(0AA40020): Send Reply Message: (0AD60070) sequenceNumber(47)
: As
: ynchronous. ... (00000000)
: WSD08 Send: result = 0
: SMI03 Connection(0AA40020): Send Reply Message: (0AD60070) sequenceNumber(47)
: As
: ynchronous. SUCCEEDED (00000000)
: SMI08 Connection(0AA40020): Disconnect: ... (00000000)
: WSD09 SendDisconnect: result = 0
: WSD04 Release: RefCount for connection object = 2
: SMI08 Connection(0AA40020): Disconnect: SUCCEEDED (00000000)
: DPB Release DPB_SESSION_SERVICE(0AA401A0) refCount(1)
: SMI Release SMI_CONNECTION(0AA40020) refCount(2)
: DPB56 Memory Proc Common : count(1), total(86016), alloc(15), free(81826)
: DPB Release DPB_SESSION_SERVICE(0AA401A0) refCount(0)
: WSD06 ReadHeader: Received disconnect code = FF
: DPB Release DPB_Connection(0AB60760) refCount(0)
: SMI Release SMI_CONNECTION(0AA40020) refCount(1)
: SMI Release SMI_TRACE(013FB488) refCount(4)
: WSD04 Release: RefCount for connection object = 1
: SMI Release SMI_CONNECTION(0AA40020) refCount(0)
: SMI Release SMI_TRACE(013FB488) refCount(3)
: SMI Release SMI_LISTENER(013FB398) refCount(1)
: SMI Release SMI_TRACE(013FB488) refCount(2)

The job still failed to run with the same errors. The agent also threw a Dr. Watson error when I exited out of it "Exception: access Violation (0xc0000005), Address: 0x112eef5f".

Here are the trace files that were generated on both machines. (Well... what I could capture of them)

AGENT

(), sessionId(06030120). SUCCEEDED (00000000)
SMI01 Connection(05F10020): Create Message: (06230080), initial size 0 bytes
SMI03 Connection(05F10020): Send Reply Message: (06230080) sequenceNumber(85) As
ynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(05F10020): Send Reply Message: (06230080) sequenceNumber(85) As
ynchronous. SUCCEEDED (00000000)
SMI08 Connection(05F10020): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(05F10020): Disconnect: SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(05F101A0) refCount(1)
SMI Release SMI_CONNECTION(05F10020) refCount(2)
DPB56 Memory Proc Common : count(1), total(86016), alloc(15), free(81825)
DPB Release DPB_SESSION_SERVICE(05F101A0) refCount(0)
DPB Release DPB_Connection(06030760) refCount(0)
SMI Release SMI_CONNECTION(05F10020) refCount(1)
SMI Release SMI_TRACE(013FB420) refCount(4)
WSD06 ReadHeader: Received disconnect code = FF
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(05F10020) refCount(0)
SMI Release SMI_TRACE(013FB420) refCount(3)
SMI Release SMI_LISTENER(013FB330) refCount(1)
SMI Release SMI_TRACE(013FB420) refCount(2)

MASTER

WSD11 AddRef: RefCount for listener object = 1
SMI10 Listener (013FCBC8): Start Listening: computerName(), serviceName(10099),
driverName(WinSock). SUCCEEDED (00000000)
WSD11 AddRef: RefCount for listener object = 2
WSD11 AddRef: RefCount for listener object = 3
WSD11 AddRef: RefCount for listener object = 4
WSD11 AddRef: RefCount for listener object = 5
DPB30 Listener (013FC5D0): Start Listening : application(10099), location(), dr
iver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(2536), total(421888), alloc(299649)
, free(110627)
DPB56 Memory Proc Common : count(993), total(86016), alloc(54623), free(26195)
DPB01 Connection(013FC800): ConnectToServer : application(10099), location(172.1
8.0.94), driver(WinSock). ... (00000000)
DPB01 Connection(013FC800): ConnectToServer : application(10099), location(172.1
8.0.94), driver(WinSock). SUCCEEDED (00000000)
DPB02 Connection(013FC800): DisconnectServer: ... (00000000)
DPB02 Connection(013FC800): DisconnectServer: SUCCEEDED (00000000)
DPB01 Connection(013FC800): ConnectToServer : application(10099), location(172.1
8.0.94), driver(WinSock). ... (00000000)
DPB01 Connection(013FC800): ConnectToServer : application(10099), location(172.1
8.0.94), driver(WinSock). SUCCEEDED (00000000)
DPB02 Connection(013FC800): DisconnectServer: ... (00000000)
DPB02 Connection(013FC800): DisconnectServer: SUCCEEDED (00000000)

: OK, it appears to be working with the number. Don't pay much attention to
: "FAILED (80004005)". This message only indicates that some
: port-in-use test failed.

: The job you run from some other place was able to connect to the agent, but
: then it immediatelly disconnacted from the agent without performing any
: real processing.

: Make the following 2 changes: 1. In the agent profile (on the other computer)
: properties set connection mode to "synchronous"
: 2. In the job properties set job to also run as "synchronous" job.

: That should help.

You din't change the connection mode or job run mode. The trace still says "Asynchronous" connection.

By the way, are there any errors reported in the job log on the master?

"Dr. Watson" error is not related to this problem. I think it was fixed in 2.4.15. Please upgrade if you running an older version.

: The job still failed to run with the same errors. The agent also threw a Dr.
: Watson error when I exited out of it "Exception: access Violation
: (0xc0000005), Address: 0x112eef5f".

: Here are the trace files that were generated on both machines. (Well... what
: I could capture of them)

: AGENT

: (), sessionId(06030120). SUCCEEDED (00000000)
: SMI01 Connection(05F10020): Create Message: (06230080), initial size 0 bytes
: SMI03 Connection(05F10020): Send Reply Message: (06230080) sequenceNumber(85)
: As
: ynchronous. ... (00000000)
: WSD08 Send: result = 0
: SMI03 Connection(05F10020): Send Reply Message: (06230080) sequenceNumber(85)
: As
: ynchronous. SUCCEEDED (00000000)
: SMI08 Connection(05F10020): Disconnect: ... (00000000)
: WSD09 SendDisconnect: result = 0
: WSD04 Release: RefCount for connection object = 2
: SMI08 Connection(05F10020): Disconnect: SUCCEEDED (00000000)
: DPB Release DPB_SESSION_SERVICE(05F101A0) refCount(1)
: SMI Release SMI_CONNECTION(05F10020) refCount(2)
: DPB56 Memory Proc Common : count(1), total(86016), alloc(15), free(81825)
: DPB Release DPB_SESSION_SERVICE(05F101A0) refCount(0)
: DPB Release DPB_Connection(06030760) refCount(0)
: SMI Release SMI_CONNECTION(05F10020) refCount(1)
: SMI Release SMI_TRACE(013FB420) refCount(4)
: WSD06 ReadHeader: Received disconnect code = FF
: WSD04 Release: RefCount for connection object = 1
: SMI Release SMI_CONNECTION(05F10020) refCount(0)
: SMI Release SMI_TRACE(013FB420) refCount(3)
: SMI Release SMI_LISTENER(013FB330) refCount(1)
: SMI Release SMI_TRACE(013FB420) refCount(2)

: MASTER

: WSD11 AddRef: RefCount for listener object = 1
: SMI10 Listener (013FCBC8): Start Listening: computerName(),
: serviceName(10099),
: driverName(WinSock). SUCCEEDED (00000000)
: WSD11 AddRef: RefCount for listener object = 2
: WSD11 AddRef: RefCount for listener object = 3
: WSD11 AddRef: RefCount for listener object = 4
: WSD11 AddRef: RefCount for listener object = 5
: DPB30 Listener (013FC5D0): Start Listening : application(10099), location(),
: dr
: iver(WinSock). FAILED (80004005)
: DPB55 Memory Session : (00000000) count(2536), total(421888), alloc(299649)
: , free(110627)
: DPB56 Memory Proc Common : count(993), total(86016), alloc(54623),
: free(26195)
: DPB01 Connection(013FC800): ConnectToServer : application(10099),
: location(172.1
: 8.0.94), driver(WinSock). ... (00000000)
: DPB01 Connection(013FC800): ConnectToServer : application(10099),
: location(172.1
: 8.0.94), driver(WinSock). SUCCEEDED (00000000)
: DPB02 Connection(013FC800): DisconnectServer: ... (00000000)
: DPB02 Connection(013FC800): DisconnectServer: SUCCEEDED (00000000)
: DPB01 Connection(013FC800): ConnectToServer : application(10099),
: location(172.1
: 8.0.94), driver(WinSock). ... (00000000)
: DPB01 Connection(013FC800): ConnectToServer : application(10099),
: location(172.1
: 8.0.94), driver(WinSock). SUCCEEDED (00000000)
: DPB02 Connection(013FC800): DisconnectServer: ... (00000000)
: DPB02 Connection(013FC800): DisconnectServer: SUCCEEDED (00000000)

I'm running version 2.4.7 I'm not sure if any upgrades or patches are available.

I did change the connection mode of the job and the remote agent profile. There is no option for synchronous, just the ability to deselect (turn off the check box) asynchronous. I don't believe that I'm missing the option to run synchronously anyplace; I search pretty thoroughly (on both master and agent).

But now, let me ask this... I know we have a site license for this product, but I just realized that we have the same serial number on all the installs (I believe we only received one serial number). Could this be the issue?

: You din't change the connection mode or job run mode. The trace still says
: "Asynchronous" connection.

: By the way, are there any errors reported in the job log on the master?

: "Dr. Watson" error is not related to this problem. I think it was
: fixed in 2.4.15. Please upgrade if you running an older version.

Using the same serial number could be an issue only if you use not your site license number but perhaps another number for single installation license.

Please upgrade to 2.4.15. This upgrade is free and can be found on http://www.24x7automation.com downloads page.

: I'm running version 2.4.7 I'm not sure if any upgrades or patches are
: available.

: I did change the connection mode of the job and the remote agent profile.
: There is no option for synchronous, just the ability to deselect (turn off
: the check box) asynchronous. I don't believe that I'm missing the option
: to run synchronously anyplace; I search pretty thoroughly (on both master
: and agent).

: But now, let me ask this... I know we have a site license for this product,
: but I just realized that we have the same serial number on all the
: installs (I believe we only received one serial number). Could this be the
: issue?

The upgrade to version 2.4.15 worked. I'm able to run remote jobs now with no problem.

Thanks for all your help.

: Using the same serial number could be an issue only if you use not your site
: license number but perhaps another number for single installation license.

: Please upgrade to 2.4.15. This upgrade is free and can be found on
: http://www.24x7automation.com downloads page.