Page 1 of 1
Change TM1 server location - Service getting started from old location
Posted: Tue Aug 23, 2016 5:44 am
by SBK88
Hi All,
Need your help
I have few TM1 servers installed (PROD environment) in Drive D, I need to move them to new Drive E.
I have updated the cfg file in new location. ( data directory and log directory new path)
and have updated the TM1 server configuration path for the particular TM1 server in IBM Cognos Configuration.
But while restarting the TM1 services, it is getting started from its OLD location not from the new one.
Is there anything that I have missed or what additional thing I need to update ?
Thanks
Re: Change TM1 server location - Service getting started from old location
Posted: Tue Aug 23, 2016 6:49 am
by lotsaram
DELETE the service using cmd.exe (sc delete "service name")
Then Cognos Configuration will regenerate the service with the correct path to the folder containing tm1s.cfg
Re: Change TM1 server location - Service getting started from old location
Posted: Tue Aug 23, 2016 7:58 am
by TrevorGoss
lotsaram wrote:DELETE the service using cmd.exe (sc delete "service name")
Then Cognos Configuration will regenerate the service with the correct path to the folder containing tm1s.cfg
You can also delete the service from the Cognos configuration application. Is there a reason for deleting via a windows command instead of the Cognos configuration? I know when you delete it from the Cognos configuration it saves all of your other services and when you close the application it asks if you want to start all of your stopped services, but apart from that, is there any reason to pick one over the other?
Thanks.
Trevor.
Re: Change TM1 server location - Service getting started from old location
Posted: Tue Aug 23, 2016 10:00 am
by lotsaram
TrevorGoss wrote:
You can also delete the service from the Cognos configuration application. Is there a reason for deleting via a windows command instead of the Cognos configuration? I know when you delete it from the Cognos configuration it saves all of your other services and when you close the application it asks if you want to start all of your stopped services, but apart from that, is there any reason to pick one over the other?
Only speed and convenience. Deleting with command line takes a second. Thereafter selecting "start" in Cognos configuration will automatically recreate the service. Deleting in Cognos config causes an unnecessary resaving and checking of all the services and more time staring at the COGNOS hourglass.
Re: Change TM1 server location - Service getting started from old location
Posted: Tue Aug 23, 2016 1:08 pm
by TrevorGoss
lotsaram wrote:TrevorGoss wrote:
You can also delete the service from the Cognos configuration application. Is there a reason for deleting via a windows command instead of the Cognos configuration? I know when you delete it from the Cognos configuration it saves all of your other services and when you close the application it asks if you want to start all of your stopped services, but apart from that, is there any reason to pick one over the other?
Only speed and convenience. Deleting with command line takes a second. Thereafter selecting "start" in Cognos configuration will automatically recreate the service. Deleting in Cognos config causes an unnecessary resaving and checking of all the services and more time staring at the COGNOS hourglass.
Yeah I can agree with that, thanks.
Re: Change TM1 server location - Service getting started from old location
Posted: Wed Aug 24, 2016 5:23 am
by gtonkin
I usually just update the ConfigPath in the registry for the relevant service.
Code: Select all
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<tm1 server>\ConfigPath
Re: Change TM1 server location - Service getting started from old location
Posted: Thu Aug 25, 2016 10:00 am
by whitej_d
I reported this as a bug to IBM when v10.1 first came out. They told me it was expected behaviour!
Re: Change TM1 server location - Service getting started from old location
Posted: Thu Aug 25, 2016 10:27 am
by lotsaram
whitej_d wrote:I reported this as a bug to IBM when v10.1 first came out. They told me it was expected behaviour!
I got the same with service name getting farked if there is a space between param name equal sign and param value in tm1s.cfg