This line of code works fine:
Code: Select all
AsciiOutput( '\\CUSTOMER.local\dfs$\dhx-public\Applications\BIManRep\Logfiles\TI.log', 'test hello world' );
Code: Select all
LogOutput( 'DEBUG', 'test hello world' );
If I use the logging directory as the output folder (so I uncomment line 5 above and I comment line 6), TM1 generates the file the way it should.log4j.logger.TM1.TILogOutput=DEBUG, Debug_LogOutput
log4j.appender.Debug_LogOutput=org.apache.log4j.SharedMemoryAppender
log4j.additivity.TM1.TILogOutput=false
log4j.appender.Debug_LogOutput.TimeZone=Local
# log4j.appender.Debug_LogOutput.File=TI.log
log4j.appender.Debug_LogOutput.File=\\CUSTOMER.local\dfs$\dhx-public\Applications\BIManRep\Logfiles\TI.log
log4j.appender.Debug_LogOutput.MaxFileSize=100 MB
Hence, I don't think there's an issue with the tm1s-log.properties file.
Can someone spot any issue or error, which explains why the TI.log file is not created as it should ?
The way I understand it, is that the TM1 service account has write privileges to the folder, as confirmed by AsciiOutput. Then what is stopping LogOutput from working ? The folder is on a different server but AsciiOutput does not seem to complain, though.
Thanks !