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 (220.127.116.11), 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.
Here are some commonly asked questions and answers to help with your adoption of Cisco ACI solution. Subscribe to this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.
Join us for this #CiscoChat focused on how you can unlock the power of your hybrid cloud infrastructure. A panel of Cisco and industry experts will discuss Cisco’s hybrid cloud strategy and dive deep into the future-ready infrastructure behind it all.