Page 1 of 1

Tm1 not re-starting

Posted: Sun Feb 16, 2014 3:17 pm
by nickykoller
We have a long-standing application that I have recently done several changes to.
I have tried to re-start the server today and it won't re-start.
I have tried deleting the old log files several times and re-started the Application Services.
Another smaller database starts up fine.
A back-up from a few days ago, doesn't start up.

The log file doesn't show an error.
Its gets near the end and stops after this:
41632 [] INFO 2014-01-14 07:31:01.020 TM1.Server TM1CubeImpl::ProcessFeeders: Done computing feeders for base cube '}StatsByClient'.
Other log files show this afterwards:
42104 [] INFO 2014-01-14 07:31:13.937 TM1.Server Starting PseudoElement thread. Thread Id: 42104
44140 [] INFO 2014-01-14 07:31:13.937 TM1.Server Starting spy thread. Thread Id: 44140
41632 [] INFO 2014-01-14 07:31:13.937 TM1.Chore Registering chore: Accpac - Update GL Start time: 2013/08/15 00:12:18 Frequency: 01:00:00:00

The last file which has a date stamp is the Chores.dim.
I tried moving the Chores related files out of the main folder (as it would be easy to re-create), but doesn't help and it recreates the Chroes.dim file.

Fresh out of ideas!!
Any thoughts??

Re: Tm1 not re-starting

Posted: Sun Feb 16, 2014 5:27 pm
by declanr
I would copy the contents of the data directory into the location of the database that does start and see if you can load it up under that guise. That way you can see whether its anything to do with the data files or not.

If not you could try changing the port etc on the servers config file.

If it is something to do with the data directory, take out sections of files you think may be the issue until you narrow down which one/s are stopping it from starting up.

Re: Tm1 not re-starting

Posted: Sun Feb 16, 2014 7:43 pm
by nickykoller
I tried your suggestions.
Deleted just about everything (rules, processes,chores,security cubes etc) and EVENTUALLY deleted some folder files which held the .vues files.

It has now started up with hopefully not to much damage...

Still not 100% sure which folder/file it was.
Suspecting it was one of the Application Security views...?

Thank you for you help.