04-01-2015 06:03 AM - edited 03-01-2019 09:14 AM
I am getting theis error with an AD account when trying to run a script. The script will run with a local account. The UNIX admin assures me that all permissions are granted for this to work. Any ideas?
04-01-2015 07:06 AM
So the AD account is granted access on the Unix box. Is that correct ?
Are you getting the same error when you try to run it with a non-existent(eg: abcd) user also ?
04-01-2015 07:24 AM
The AD account has all necessary file permissions. The UNIX admin tells me that SSH permission is not necessary to run the script.
I have used another Ad account and it throws the same error. A local account from another unix server gets the same error.
We checked the agent file, and the runtime uses that show up in the console show up in the agent file.
04-01-2015 07:43 AM
Did you try giving all permissions on the script file(chmod 777) ?
Can you share more details of the error message seen ?
04-01-2015 07:53 AM
04-01-2015 08:13 AM
Hi Paul,
Can you please verify runtime user? (From Job Activity->Job Details)
Is this runtime user an Interactive user or a runtime user?
How did runtime user get created?
-Derrick Au
04-01-2015 08:43 AM
It is a runtime user. I created it manually in the console.
We have tried changing to all lowercase, with and without password, exactly as it is in AD with respect to upper or lower case.
This seems to be a problem with all out active directory userid's on this unix server. None of them work.
04-01-2015 09:48 AM
Does it show the domain name as well ? such as DOMAIN\userid
04-01-2015 10:02 AM
It does in the job view, and it is entered in the runtime user record.
04-02-2015 08:04 AM
After restarting the instance yesterday, I increaded the logging levels to high debug. When I ran the job with the invalid runtime user today I have the following log entry:
JobRun: 989519 had error during startup; XML=<ST STS="10" TM=20150402090356 VAL=0 ETP=TDL ECD=0><SE>^A:~{Launcher Error: Invalid runtime user
04-02-2015 01:42 PM
Hi Paul,
I don't believe the logs would help here.
Which Tidal version are you running (Master, Client Manager)?
When you say creating a runtime user from the console, do you mean from the Java client? or from the web client?
-Derrick Au
04-02-2015 02:27 PM
Scheduler is 6.1.0.404 and CM is 6.1.0.133.
We use the web client for this version.
04-05-2015 01:37 PM
There must be a way to print all the values being used by the unix agent.
In the case of Windows agent, we would create a sample job which will print all the environment variables being used by the agent
C:\WINNT\system32\cmd.exe /c set
04-10-2015 08:12 AM
We found that the problem was that the 32 bit winbind clients were not installed on the server. Once they were, works just fine.
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