Tidal Win Agent crashing with .NET Runtime 2.0 Error

[michael.scrivo]

While running the Tidal Windows agent 3.0.1.18 we are getting .NET Runtime 2.0 Error – with a description - Faulting application tidalagent.exe, version 3.0.0.0, stamp 4d5ad33f, faulting module triagt.dll, version 0.0.0.0, stamp 4d5ad33e, debug? 0, fault address 0x00046160.

We have been seeing this happen intermittently across most of our Windows servers. The error is reported in the Windows application event log but the agent log even in high debug mode does not report anything - the agent just dies. We have worked around this by setting the Windows service to auto restart but the running jobs get clobbered and some jobs get stuck in launch.

Has anyone encountered this issue?

Thanks,

Mike

[miguel.aliaga]

Hi Michael,

We got same incident Today;

Faulting application tidalagent.exe, version 3.0.0.0, stamp 4d5ad33f, faulting module triagt.dll, version 0.0.0.0, stamp 4d5ad33e, debug? 0, fault address 0x00046160

Causing Tidal Agent to die.

Did you manage to resolve this incident?

Please appreciate if you can share your experience.

Anyone else from Cisco audience who can help with this, please greatly appreciate your feedback.

Thanks.

[NPBS.CISCO]

We're experiencing some intermittent issues like this with some of our servers as well.

Any thoughts to how this was fixed?