Tm1RunTI Diffrent Adminhosts Issue

[Darkhorse]

Hi all

I have been trying to get the Tm1runTI.exe to work inside a TI and when trying diffrent servers on the same adminhost the TI runs perfectly however when my server is on a diffrent adminhost It does not work

I have each focal point classed as a variable to make interchanging easily, I alter my Admin host and servername

Code: Select all

S_Run ='Tm1runti -process ' | vProcess | ' -Connect -adminhost ' | vAdminHost | ' -server ' | vServername | ' -user ' | vUsername |' -pwd ' | vPassword ;
ExecuteCommand(EXPAND(S_Run),0);

is there any further Instructions I require that I'm missing to get this command to run accross adminhosts?

[qml]

Firstly, you don't need the EXPAND function there.
Secondly, have you tried doing ASCIIOUTPUT of the S_Run variable to a text file and pasting it to a command line window to see what is wrong with the syntax?
Thirdly, are you passing the correct Admin Host reference, including the domain if necessary?

[Darkhorse]

Hi qml thanks for the reply,

Unfortunately due to the way our servers are setup I don't have access to the tm1runti.exe file via cmd.

I removed the expand but it wasn't a problem using it as it worked perfectly on adminhost1 server 1and 2

But I think the problem actually lies with the admin hosts themselves, I built the same TI exactly the same on adminhost2 and created a test TI to run exactly the same as on adminhost1 the process will not run the test TI and it won't work the TI's on the adminserver1 system which I know works due to my first tests.

Will keep scratching my head and testing

[PlanningDev]

It will be hard to find out but if the directory that tm1runti.exe is in doesn't exist in your path variable then you have to provide the full path to it.

Simply calling tm1runti.exe from command line will fail if you don't have this. Also, be aware that adding the TM1 directories to the command line can cause issues with other Cognos Installs as TM1 contains similar .dll files but they are 64 bit. IE framework manager installed on the same server will run into issues starting up if you have the TM1 directories defined in the path. Im testing now to see if the tm1runti.exe can be moved from the bin directory so you can get around this.

[Darkhorse]

I had tried the full path but due to security restrictions I'm unable to run it from the folder it's located in, is it possible to restrict a user from using specific exe's on different servers? I.e I have the ability to run tm1runti on one server but not the next? Just still scratching my head on this one, unfortunately I'm learning tm1 backwards, having never installed tm1 I'm learning the configs files in reverse, learning the programming and trying to advance the limits of the coding is making me look more at the setups used on the servers.

Could a tm1config.ini be setup differently from one user to the next on different servers.

The reason why I'm asking is because I'm a developer/admin on 2 servers within the same admin host. I also have rights to create TIs in other servers and classed as an admin but not responsible for them. The tm1runti works on both my responsible servers but not on others.

Admin host1
Server1 - me responsible - tm1runti works
Sever2 me responsible - tm1runti works
Server3 admin but not owner - tm1runti does not work

Adminhost2
Server1 admin not owner -tm1runti does not work
Etc

Seems a little to coincidental that it works on my owned servers but not others, is this possible to do via the configs?