Express 10.1. Planner Application error TI_CUBE_NOT_EXIST

[mr j]

Believe it or not, this problem is still unsolved. I've opened SR with IBM.

What happens is
- a user (any in any namespace) opens application and takes ownership
- control cube }tp_central_application_state is updated accordingly
- user closes the application grid and immediately the mentioned error appears
- the same user is not able to open the app anymore but gets the error
- another user can open and take ownership and }tp_central_application_state is updated accordingly, but when this another user closes the app the same happens to him.

The only way to get around this is reset the application.

Nobody else faced similar?

_____________


--------------------------------------------
Hello again,

I'm building apps with IBM Cognos Express 10.1. and got an issue with an application not opening. The attached error message appears after clicking the app name -hyperlink to open it:
----
IBM Cognos Express Planner Application
An error occurred on TM1 server.
:com.ibm.cognos.pmpsvc.PMPSVCException: Cube does not exist.
:TI_CUBE_NOT_EXIST
----

I think there's a connection to when the application is closed because of timeout (another issue according to a bit of googling, 20min being the default..). After a timedout session you're not able to open the app with the same user id. With another id the same application is ok.

Ring any bells, anyone? What to look for?

[mr j]

Guys, seriously.

Are you telling me by being silent that nobody ever got this error message?

[MFGF]

Guys, seriously.

Are you telling me by being silent that nobody ever got this error message?

Seriously. I never got this message. :)

MF.

[mr j]

Seriously. I never got this message. :)

MF.

Right. One down  ;)
In a way it's not a comforting thought it could be just me...

Any ideas what could cause the behaviour I've described are appreciated.

When this occurs the log file "tm1server.log" is updated e.g.                                                               
                                                                       
----                                                                   
8124   [7]   ERROR   2014-05-05 08:12:48.368   TM1.Process   Process "}
tp_workflow_update_user_name": : Execution was aborted. Error file:     
<TM1ProcessError_20140505081248_}tp_workflow_update_user_name.log>     
----                                                                   
                                                                       
The mentioned "...}tp_workflow_update_user_name.log" contains the following:                     
"Error: Prolog procedure line (73): ProcessError()"                     
                   
In process "tp_workflow_update_user_name" on line 71 there's error message "TI_CUBE_NOT_EXIST".

[MFGF]

Right. One down  ;)
In a way it's not a comforting thought it could be just me...

Any ideas what could cause the behaviour I've described are appreciated.

When this occurs the log file "tm1server.log" is updated e.g.                                                               
                                                                       
----                                                                   
8124   [7]   ERROR   2014-05-05 08:12:48.368   TM1.Process   Process "}
tp_workflow_update_user_name": : Execution was aborted. Error file:     
<TM1ProcessError_20140505081248_}tp_workflow_update_user_name.log>     
----                                                                   
                                                                       
The mentioned "...}tp_workflow_update_user_name.log" contains the following:                     
"Error: Prolog procedure line (73): ProcessError()"                     
                   
In process "tp_workflow_update_user_name" on line 71 there's error message "TI_CUBE_NOT_EXIST".

I can't find any other mention of this error anywhere online. What are IBM saying about it? You said earlier in the thread you have raised a PMR?

MF.

[mr j]

I can't find any other mention of this error anywhere online. What are IBM saying about it? You said earlier in the thread you have raised a PMR?

Can't find anything either..!

What are IBM saying... to keep the story short the latest idea was there could be something with the versions of different components not being in sync (FP1 / not FP1). Maybe something there, maybe not. I'd say the latter.