Control-M/Agent Listener service terminated unexpectedly

TRAVO · Post by **TRAVO** » 12 Jun 2007 3:03

Hi,

What would cause an agent to execute and show yellow on the AJF then when the job completes it goes white 'unknown' status. The server type is a Windows NT server. There is a DMZ involved and I'm not sure if that has anything to do with the reason the agent is failing. I have Control M 6.2.01 and Control M Agent\6.2.01\Windows_32.

Thanks,

Travo

hipikll · Post by **hipikll** » 12 Jun 2007 9:16

Does it fail to update status in all of the jobs?
Can you run a job like "dir" if it returns right status?
If so, it can be, that the problem is in child process of your job on agent.
You have to set some parameter in ctmwincfg (if i remember the command).
write more.
Or it can be, that the agent is not allowed to send the status of job back because of "some strange network restriction" ... I can't say.

TRAVO · Post by **TRAVO** » 12 Jun 2007 9:21

It's only for this one server and yes it for all the jobs on that server. Right now there are only two. I tried the dir and it did the same thing. Where is this child process on the agent or with the job setup itself or server level maybe? It's a new install of the agent on this server also.

Thanks,

Travo

hipikll · Post by **hipikll** » 12 Jun 2007 10:45

Can you try this machine's agent outside the DMZ?

Can you try to run some utilities from agent like ctmcreate to discover, if the communication from agent to server is allowed?
Or try agent diagnostic tools to check the connection with server. The communication need to be initialized from agent.

just my imagination

mauriziog · Post by **mauriziog** » 13 Jun 2007 8:08

Go to the services in the windows 2003 machine, in the:
propreties\log on

1) Look if there is checked "Allow service interact to the desktop"

2) Unselect this option and restart the service.

3) Try to resubmit the job.

Hi