Local Config file error

Post Reply
AWTM1
Posts: 16
Joined: Wed May 15, 2013 10:57 am
OLAP Product: Tm1
Version: 10.2.2
Excel Version: 2010

Local Config file error

Post by AWTM1 »

Hi, I have been unable to resolve the following issue with TM1 9.5.2:

Our tm1 servers fell over last night due to running out of space. They are back up and running now but I am experiencing the following problem:

Error on opening any rule editor is "Local config file error, restoring defaults Root element is missing." This only happens on the tm1 server. If I click ok I can continue and write rules but architect has crashed twice.

If I turn advanceruleseditor to False in the TM1p ini file I get no error and everything seems to be working as normal.

If I use my local architect pointed at the tm1 server with exactly the same TM1p.ini settings I get no error (inc advancedruleeditor being switched on).

If I use a remote app pointed at the tm1 server I get no error.

I have tried creating a new admin user on the tm1 server and I get the same error.

Can anyone help?
declanr
MVP
Posts: 1831
Joined: Mon Dec 05, 2011 11:51 am
OLAP Product: Cognos TM1
Version: PA2.0 and most of the old ones
Excel Version: All of em
Location: Manchester, United Kingdom
Contact:

Re: Local Config file error

Post by declanr »

Bit late to the show but I've just had the same issue on a PC.

The PC in question did have the advanced rules editor turned on and last night with TM1 open; the PC froze up (not a tm1 thing - its just awful) so the power button was held down and off it went.
This morning the "Local config file error, restoring defaults Root element is missing" came up when trying to open rules in the advanced editor.
Resolved it by just removing the contents of the AppData folder for Applix; turning Architect back on to let it generate its own tm1p.ini file from scratch. Closed down architect again and made the usual tm1p.ini changes including turning the advanced rules editor back on and it worked fine after that as if nothing had happened.

So I am guessing its a localised error due to some temp files etc that are left over when you don't shut down properly - surprised I've not seen it before though as I force PCs to turn off worryingly often.
Declan Rodger
Post Reply