The description for Event ID 0 from source tm1sdx64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
tm1sdx64 error: 0
c12
The server restarts itself many times a day without any error in tm1server.log. The bug message is from OS event manager.
What may be the reason? How to get additional info?
C 12) is a message that there is a log file there when the system starts back up. It indicates that TM1 did not shut down properly. So this particular error is most likely after the fact. It's probably not directly related to the server restarting itself.
Unless the cause of the restart is obvious (e.g. you don't have enough RAM) you'll need to log a bug with IBM.
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers. Jodi Ryan Family Lawyer
I had the same error, that the tm1s.log was not deleted automatically on a server shut down. So TM1 stoppt booting the service when detected the log file. Deleted it, and anything was ok.
Ganos Lal wrote:Bit old but perhaps it helps someone else.
I had the same error, that the tm1s.log was not deleted automatically on a server shut down. So TM1 stoppt booting the service when detected the log file. Deleted it, and anything was ok.
Please note that tm1s.log is never deleted on server shutdown. The tm1s.log is the active transaction log file. When a server is shutdown the active log file is renamed to tm1s<timestamp>.log. When the server is started again a new tm1s.log file is opened.
If you're closing down your server and at the end there is still a tm1s.log file available, than your server did not shutdown properly. In that case you should try and find out why that is - did the server get enough time to shutdown properly?
i know this is a late response, but i just had the same issue on my server. it turns out that the antivirus went offline and in doing so, it stopped the service. so maybe have a look at your antivirus if this error occurs again
