tm1s.log not readable

[mrnara]

This might be more of a Windows Server configuration question, but...

Why is tm1s.log not readable (it is being used/lockled by some other process)?
Any way to make it readable while the server is running?

[Alan Kirk]

This might be more of a Windows Server configuration question, but...

Why is tm1s.log not readable (it is being used/lockled by some other process)?

The "some other process" would be your TM1 server. It's your transaction log.

Any way to make it readable while the server is running?

Not that I'm aware of (I stand to be corrected on that) but if any other process has access to the file it could cause some unfortunate consequences. If your server can't write to the transaction log for any reason it will immediately crash. It needs to be free to write to it as and when it needs to, which even a read operation by an external application could block temporarily.

If you're an administrator you can view the transactions that have been processed via the GUI. Details of how to access that are in the Operations manual. Otherwise if you really need to load up the file and analyse it you should do a data save, at which time all of the data in the transaction log will be copied to a new file which you can peruse at your leisure.

[mrnara]

Thanks for the explanation!

Programmers/Developers often do something like

Code: Select all

tail -f serverLogFile.log

while a server is running to see what it is up to.
Can't think of any server that ran into a problem writing to the .log file while someone was tailing it.