Search found 2 matches
- Mon Aug 29, 2011 12:47 am
- Forum: Bugs
- Topic: PMR69311 999 866: Corrupt Log Files > Server Crash
- Replies: 12
- Views: 15725
Re: PMR69311 999 866: Corrupt Log Files > Server Crash
I'm not sure if this is useful in debugging this issue, but here is the code from my SaveDataAll process: Prolog: ProcessName = 'zSaveDataAll'; #Enter the Start Time in the Parameter Cube StartVal= TIMST(Now, '\d/\m/\Y \h:\i:\s'); CellPutS(StartVal, 'Parameters','1',ProcessName,'Start Time'); Epilog...
- Thu Jul 21, 2011 3:58 am
- Forum: Bugs
- Topic: PMR69311 999 866: Corrupt Log Files > Server Crash
- Replies: 12
- Views: 15725
Re: PMR69311 999 866: Corrupt Log Files > Server Crash
I had a similar issue yesterday when the TM1 server wouldn't restart due to a corrupted log file. It looks like log files created by a SaveDataAll process result in a missing " in the first line of the log file. The log files created by a manual Save Data seem to be OK.