TI Process Read Lock on CSV Source File
Posted: Thu Dec 14, 2017 9:34 pm
Has anyone run into a TI process not releasing its read lock on a csv or txt file after completion? The offending file is one that is used for export from one TM1 server and import to another. I use RunTi to call the export and import and run the processes sequentially so I know it's not a case of the import running when the export is still executing. I've tried changing the file name, changing extension, changing file location, and setting up a 10 second wait between export completion and import start, but eventually the file will get locked in read only again. Our server has virus protection turned off for the selected area, that was my first suspicion. A restart of the TM1 server that the import process is on will release the lock and I'm able to export to the original file again.
TM1 won't generate a process error if it can't overwrite a file, so I test it in the export process prolog by trying to delete the target file, wait 5 seconds, and test if it still exists. It's crude, but it lets me know when I need to change the file name for continued use that day.
I might replace this process with a rest call, but I thought I'd ask if anyone else has experienced something similar as I don't foresee the rest api replacing our heavier transfers between TM1 servers.
*running Planning Analytics 2.0 on windows server 2012 64bit; all export/import files are saved to a share drive on a separate server; so far this is the only process/file with this issue
TM1 won't generate a process error if it can't overwrite a file, so I test it in the export process prolog by trying to delete the target file, wait 5 seconds, and test if it still exists. It's crude, but it lets me know when I need to change the file name for continued use that day.
I might replace this process with a rest call, but I thought I'd ask if anyone else has experienced something similar as I don't foresee the rest api replacing our heavier transfers between TM1 servers.
*running Planning Analytics 2.0 on windows server 2012 64bit; all export/import files are saved to a share drive on a separate server; so far this is the only process/file with this issue