11-27-2012 12:32 PM - edited 03-01-2019 08:57 AM
Hi All -
We are running 5.3.1-307.
This past Sunday we have a job that runs for 3 hrs in increments of 15 min.
However, the one instance of this job received the following error.
Error Occured:
Error logging into Runtime user OUR USERNAME job - 3762501.
Has anyone seen this error before or any thoughts?
After that error the job continued to run fine as normal. We only got that error once.
Thanks,
Bill
12-05-2012 07:25 AM
We had the same issue yesterday and were running the same version.
Error message:
*** Error logging into runtime user [username] - job 4564464.
We recycled the tidal agent and everything is back to normal but its strange because there's about 10 more jobs using the same runtime user and running on the same server that didnt get affected except for 3 jobs.
Is this a known bug? Is there a fix to it?
Appreciate if we can get a response from Cisco Support.
12-05-2012 07:37 AM
I had the same issue a while back. I traced it to an overworked active directory domain controller. Since the runtime user couldn't get authenticated, the job failed. You can find out which domain controller Tidal will use for authentication by running the following on the tidal master server from a cmd prompt: set logonserver
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide