TM1 Forum

Hi ,

WHen iam trying to start the servicies i am getting the below error message .

ERROR MESSAGE :
The TM1server x64/server name service on local computer started and then stopped.Some services stop automatically if they have no work to do, for example,the performance logs and Alert service .

can any help me why this message error message comes.

Cheers!

Hi,

Try to change the port number in configuration file and start the service. We once had the same issue and was resolved by changing the port number. We got to know that the port number which we are using for that server is locked and once we changed it in configuration file to some other port number then it started working fine. Do let me know if this resolves your issue or still u r facing it. Thanks

If this is not 9.5, you will have to make sure if you got "tm1s.lic" file in the data directory.
If it is not there, try copying it from your installation bin directory to the data directory.

This happens for a few different reasons but the message you get when running as a service is a generic "this service can't start". If you try running your server as an application you might get more useful feedback. If it runs as an application but not as a service make sure you provided the correct path to the config file when adding the service.

Instead of guessing as to why it didn't start, why not try looking in the tm1server.log file and find out why.

asutcliffe wrote:This happens for a few different reasons but the message you get when running as a service is a generic "this service can't start". If you try running your server as an application you might get more useful feedback. If it runs as an application but not as a service make sure you provided the correct path to the config file when adding the service.

Running as a application not service won't give any more or better feedback. It is just a matter of where the feedback is (i.e. in the tm1server.log and in the windows application event log) versus immediatelly in the TM1 application window with popups as errors present.

Usually it the service stops and starts it is because there is no tm1s.cfg file in the directory the service is pointed to.

lotsaram wrote:

asutcliffe wrote:This happens for a few different reasons but the message you get when running as a service is a generic "this service can't start". If you try running your server as an application you might get more useful feedback. If it runs as an application but not as a service make sure you provided the correct path to the config file when adding the service.

Running as a application not service won't give any more or better feedback. It is just a matter of where the feedback is (i.e. in the tm1server.log and in the windows application event log) versus immediatelly in the TM1 application window with popups as errors present.

Usually it the service stops and starts it is because there is no tm1s.cfg file in the directory the service is pointed to.

Thanks, point taken. I suppose I was thinking more that it would explicitly tell you if the directory you had nominated didn't contain a tm1.cfg file which wouldn't turn up in tm1server.log (though presumably does in the windows event log).

if the TM1 service will not start, and the error is almost instantaneous, then it is almost certainly one of three things:

1) the data directory specified in the tm1s.cfg file is not valid.
2) the registry key for your service that specifies the location of the tm1s.cfg file is not valid.
3) there is no tm1s.lic license file in the data directory.

Did you check if the Windows Eventviewer Application Log has logged a corresponding error event for the TM1 server process tm1s.exe (Source "tm1s") respectively tm1sd.exe (Source "tm1sd") ?

If such an error event exists, if may have more detailed information why the TM1 server process did not start.


To add another cause for immediate startup failure of a TM1 server process to Tomok's list:

4) The LoggingDirectory in the TM1 server configuration file tm1s.cfg does not exist (for instance because it includes a Space character and is not encapsulated by quotes like LoggingDirectory="C:/Program Files/Cognos/TM1/Custom/TM1Data/SData/Logs").

Hi All,

Now iam getting a different error : i.e

Could not start the TM1 server x64/server name on the local computer

Error :1069 :The service did not start due to logon failure.

can any one help me

Regards
Ashok

Go to Services (Start, Administrative Tools, Services), then find the TM1 service for your server in the Services window. Right-click and open Properties, and select the Log On tab. Select "This Account" and make sure you use a logon account in the format domain/username and then enter the password fields. Apply, and then try to start the TM1 service again. You should make sure the account you use has the necessary rights to run programs etc.