Hi guys,
we are experiencing "object duplicate" message which is followed by cube errors (something like "unable to load cube") in TM1 applications.
Does anyone know what exactly means "ObjectDuplicate" in Ops console, how is it connected to cube errors and how to avoid this behavior?
Any advice appreciated!
BR
Vladino
"ObjectDuplicate" in Ops console and cube error in TM1 apps web
-
- Community Contributor
- Posts: 248
- Joined: Tue Nov 01, 2011 10:31 am
- OLAP Product: TM1
- Version: All
- Excel Version: All
- Location: Manchester
- Contact:
Re: "ObjectDuplicate" in Ops console and cube error in TM1 apps web
Couple of posts in the forum around ObjectDuplicate, seems that adding a parameter to your tm1s.cfg file should help
Script to kill TM1TOP Process
What do your log files say?
What action precedes the issue?
Can you replicate the issue?
Script to kill TM1TOP Process
What do your log files say?
What action precedes the issue?
Can you replicate the issue?
-
- Posts: 110
- Joined: Sat Nov 06, 2010 10:10 am
- OLAP Product: Cognos TM1
- Version: 10.2.2
- Excel Version: Excel 2013
Re: "ObjectDuplicate" in Ops console and cube error in TM1 apps web
Hi Edward,
thanks for your reply.
Yes, I know this parameter already and we have it in our CFG file (set to 120s). But we also use "ClientMessagePortNumber" parameter which should avoid this locking behavior. Or should we use also this parameter and set it only to few seconds?
We can't find anything about these locks in the standard tm1server log file.
We haven't found any specific user behavior that may cause this issue. Subset editor is disabled, the only thing users can do within the views is pivoting.
This situation occurs from time to time but as we don't know what users are doing we can't replicate.
BR
Vladino
thanks for your reply.
Yes, I know this parameter already and we have it in our CFG file (set to 120s). But we also use "ClientMessagePortNumber" parameter which should avoid this locking behavior. Or should we use also this parameter and set it only to few seconds?
We can't find anything about these locks in the standard tm1server log file.
We haven't found any specific user behavior that may cause this issue. Subset editor is disabled, the only thing users can do within the views is pivoting.
This situation occurs from time to time but as we don't know what users are doing we can't replicate.
BR
Vladino