Page 1 of 1

EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Tue Nov 06, 2012 5:23 pm
by Jodha
I have TI Process with Execute command to copy a file from one server to other server it ran perfect in Dev and Uat when i moved the same process to Production
i am facing the issue , Even though TI process shows confirmation message that TI process executed sucessfully but nothing happens
when i tried access batch file manually i was able to copy the file from one server to other
i tred changing security like giving access to domain user to all file folders in the path

below is the command i am running
EXECUTECOMMAND ( '\\Servername\G$\TM1\Data Files\BatFiles\Copy.bat' ,1);

Is there any thing that i need to look for please help me
i am using TM1 10.1 version on windows 2008 R2

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Tue Nov 06, 2012 7:32 pm
by Michel Zijlema
Is the user the TM1 Production server service is running on a different user than the user the DEV/UAT services are running on?
If so, does this user have sufficient privileges to copy the file from the source to the destination location?

Michel

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Tue Nov 06, 2012 8:30 pm
by Jodha
Micheal,
Thanks for the response yes both Dev/Uat and Prod has different Domain Account user
i manually gave Prod Domain Account user access to batch file path by right clicking on the folder>Properties>Security>Edit>Add full access
is there any thing that i am missing

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Wed Nov 07, 2012 9:48 am
by vaneagle
Sounds like a security issue with your production domain account user.

had a similar issue on a 2008 enterprise server and the access for a service account. Security access fixed it.

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Wed Nov 07, 2012 10:11 am
by asutcliffe
As suggested, security might be an issue.
Jodha wrote:i manually gave Prod Domain Account user access to batch file path by right clicking on the folder>Properties>Security>Edit>Add full access
is there any thing that i am missing
As well as having rights to execute the script, the user needs to have sufficient rights to execute the commands in the script itself. Have you tried running the script manually as the user the TM1 service is running as?

Also, (as I thought someone else had pointed out), I assume you know that \\Servername\G$\TM1\Data Files\BatFiles\Copy.bat is refers to the g: on server "Servername"? If it is a local file you might be better off using g: or a relative path.

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Fri Nov 09, 2012 2:40 pm
by Jodha
MICHEAL,VANEAGE,ALEX,

Thanks for your replays as all we expected it was an access issue by adding TM1 domain user to Admin group on all servers solved my Problem :P

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Fri Mar 29, 2013 3:35 pm
by kkmk
Hi,

I am also facing the same issue and tried this in three different machines, DEV/QA and Mock environment. The same logic works in all environment except DEV. All my developments progress in DEV.

I have tried all the solutions given in the Forum and nothing works out in DEV. After all tries, I understand that the problem is with the Security access. We are using a separate network account for running the TM1 service. and i have checked this TM1 service is in admin group.

Please let me know what kind of access is required the process to run a batch file in command prompt.

Thanks in advance
kkmk

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Fri Mar 29, 2013 4:53 pm
by jim wood
Normally the user used to start the TM1 service needs full control of the TM1 data directory. I would suggest for any script directory the user would need read, write and execute as a minimum but again full control might be a safer bet,

JIm.

Re: EXECUTE PROCESS UNABLE TO KICK BATCH FILE FROM TI

Posted: Thu Apr 04, 2013 3:15 pm
by Jodha
KKMK try comparing access rights of domain user acccount in DEV with domain user account in Mock & QA environments some times this can be issue. Try to replicate exact access in all 3 environments.