TM1 Forum

I've just hit and a resolved a strange pathing issue and was wondering if anyone can throw some light on what might have happened or changed. 903U9 and 64 bit Windows Server 2003 SP2

We've been running a TI process that calls a perl script quite happily for several months using this statement and ExecuteCommand. Since the perl script was in the data directory TI knew where it was and could execute it with no issues.

All of sudden as if by magic this stopped working, but specifying the full path to the perl script appears to have resolved the issue. Happy to have resolved the issue but would love to understand why I needed to make the change. As far as I'm aware no changes have been made to the environment but I guess there could have been a windows update that I don't know about.

Cheers,
Steve

Hi Steve,

Just a theory here since I've seen a similar problem in a much older version of TM1 (either 7.1 or 8.x) and changed to use full paths ever since: I think sometimes TM1's search path/current folder can get changed as it writes files to disk within the data folder structure. For example, if the last thing it wrote to disk was a subset file, it might be looking for your script in that }subs subfolder, rather than the data directory root.

Regards,
Mike

Steve Rowe wrote:I've just hit and a resolved a strange pathing issue and was wondering if anyone can throw some light on what might have happened or changed. 903U9 and 64 bit Windows Server 2003 SP2

We've been running a TI process that calls a perl script quite happily for several months using this statement

Code: Select all

cmd /c dropeof.pl 

and ExecuteCommand. Since the perl script was in the data directory TI knew where it was and could execute it with no issues.

All of sudden as if by magic this stopped working, but specifying the full path to the perl script appears to have resolved the issue.

Code: Select all

cmd /c D:\TM1Data\Live\LiveData \dropeof.pl 

Happy to have resolved the issue but would love to understand why I needed to make the change. As far as I'm aware no changes have been made to the environment but I guess there could have been a windows update that I don't know about.

Mike may well be right; the way I work around that is to ensure that the path that I store my batch files in is specified (and is high enough up) in the Windows Server's PATH environment variable for TM1 to be able to find them without ambiguity, and without depending on the current drive/directory. In that way I don't have to burn up precious characters in specifying the full path when I call them via ExecuteCommand.