TM1 Forum

Hi all,

We are on 9.5.1 here and are using DOS commands called from TI to archive data files post the load.

For many months this has worked well and without issue. Recently this step appears to have become erratic sometimes working and sometimes not. Has anyone experienced anything like this?

The batch file always works when executed manually (at least it hs never failed).
The environment here is pretty buttoned up so its going to be hard to answer any "whats changed" type questions so if anyone has a clue about what might have changed to cause this I'd appreciate it.

Server OS is Windows Server 2003 Enterprose Edition x64 SP2

Cheers

Have had a few similar issues and have usually traced it back to another batch script running under the same account which has changed the DOS directory. Fully qualifying all paths within the batch scripts as well as within the ExecuteCommand fuction in TI for where to find the batch file to execute has resolved this but it does make the code less portable.

Thanks lotsram, pretty sure all our paths are fully UNC or from a local to server drive letter so I don't think this can be it.
Cheers

Hi, I too have faced a similiar issue as well (after months of running without issue). Additionally, while this affects batch file execution I've come to find it also(this being an educated guess) has to do with how TM1 (and/or the server) is resolving directories. What also seems weird it that once the batch file calls are "broken" they stay broken until the next reboot of the server. From that point they will be "fixed" until the next reboot whereas they become broken again. Also aside from just the batch files not running properly I've found strange results with ASCIIOUTPUT and ASCIIDELETE calls. To help illustrate, consider the following example:

Week1
All batch file calls (all with fully qualified paths and file names) work as expected
ASCIIOutputs and AsciiDeletes work properly without fully qualified path (i.e. something to the effect of AsciiOutput('MyFile.txt', 'sometext') creates a file in the database directory)
Weekly Reboot

Week2
All batch file calls (all with fully qualified paths and file names) fail
ASCIIOutputs and AsciiDeletes work incorrect (i.e. something to the effect of AsciiOutput('MyFile.txt', 'sometext') creates the file not in the database directory, I have no idea where on the server as I am no permitted to view any directory aside from database directory on the server)
Weekly Reboot

Week3
All batch file calls (all with fully qualified paths and file names) work as expected
ASCIIOutputs and AsciiDeletes work properly without fully qualified path (i.e. something to the effect of AsciiOutput('MyFile.txt', 'sometext') creates a file in the database directory)

And here I am in the middle of Week3.

This is in 9.5.1 on a Windows 2008 server.... Any thoughts/guesses would be greatly appreciated)

Hmmm, that's even odder than the problem that we have...

Meant to add that our issues tend to be cleared by a restart of the TM1 instance until such time as they randmoly stop working again.

One thought I had is that the dos can be called 100s of times a day and if there was something that was buried in the OS or maybe virus protection that says this PID or programme has called a piece of DOS x times don't let it do it anymore. Anyone know of something like that?

Cheers,