Agent Unavailable after second job run

[Jason Javitz]

We're having an issue with the Tidal_Agent_1 service stopping after running a job a second time.  The first time the job completes normally.  When I perform a rerun the tidal service gets shut down and the job outputs "Agent Unavailable".

I have tested this with a few different simple jobs, reinstalled a stable tidal version (3.0.1.14), and still the same behavior.

We are using TES 5.2.2 and the agent uses Windows Server 2008 R2 Enterprise for OS.

Any ideas?  Working with tidal for years and first time seeing this.

Thanks

[Joe Fletcher]

Hi,

Check the agent logs and look for "out of memory" errors. You may want to tweak the config file and set the basic heap sizes to 2x or 4x basic depending on your system physical resources.

Cheers

[Jason Javitz]

Thanks for your response Joe.  I'm not sure sure the config file is for a windows system.  Do you know?  I know how to adjust this in Linux, but not windows.

thanks,

Jason