Missing TM1 objects: file format is too new

Post Reply
cchunken
Posts: 1
Joined: Wed Mar 21, 2018 4:19 am
OLAP Product: Cognos TM1
Version: 10.2.2
Excel Version: 2013

Missing TM1 objects: file format is too new

Post by cchunken »

Hi,

I have to migrate a TM1 model from one server (Server A) to another (Server B) monthly. The migration was used to be successful, i.e. the TM1 instance can be started up in Server B perfectly. However, the 'file format is too new' problem happens recently and I have no idea how to fix it.

To be exact, here are the details:
1) Stop the TM1 windows service in Server A.
2) Backup the existing TM1 model folder in Server A
3) Delete all folders and files in TM1 model directory of Server A
4) Migrates all folders and files in TM1 model directory from Server B to Server A.
5) Start the TM1 service in Server A.
6) The new TM1 server starts up successfully, but missing some dimensions and cubes in Architect.
7) In the TM1 server log, we can see the following message:

"ERROR <Date> <Time> TM1.Cube Cannot load <Dimension/Cube Name>: file format is too new", in which the dimension and cubes in the message are what we found missing in Architect.

Please share if you have any ideas. Thanks!

Environment:

Server A:
TM1: 10.2.2 FP3

Server B:
OS: Windows Server 2012 R2
TM1: 10.2.2 FP6

Note: No recent upgrades had been done on both servers

Ken
kangkc
Community Contributor
Posts: 206
Joined: Fri Oct 17, 2008 2:40 am
OLAP Product: TM1, PA , TMVGate
Version: 2.x
Excel Version: 36x
Location: Singapore
Contact:

Re: Missing TM1 objects: file format is too new

Post by kangkc »

I only remember there is a object structure change in 10.2.2 FP7 IF4 which caused the objects incompatible with lower release of TM1 (FP7 and below).
http://www-01.ibm.com/support/docview.w ... wg22008561

But in your case Server B is at FP6. :roll:

Unless there are some other objects changes between FP3 and FP6 that I am not aware.
David Usherwood
Site Admin
Posts: 1453
Joined: Wed May 28, 2008 9:09 am

Re: Missing TM1 objects: file format is too new

Post by David Usherwood »

I just hit this moving a server between PA Local versions, specifically from 10.3.10200.60377 back to 10.3.10000.60286 . Only the new objects were kicked out. :evil:
Post Reply