Cryptic TM1 Messages Decoded
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Cryptic TM1 Messages Decoded
My idea for a thread is to list cryptic TM1 messages and decode them once you find what really is going on. Apologies if this has been done before. If not please add your own insights into the secret world of TM1 error messages.
Cryptic Error:
4388 ERROR 2010-01-07 18:31:05.775 TM1.Process Process "jphTempo": : Could not initialize process
Real Error
Parameter list supplied in TIExecute call from jphTempo does not match required list of parameters
Cryptic Error:
4388 ERROR 2010-01-07 18:31:05.775 TM1.Process Process "jphTempo": : Could not initialize process
Real Error
Parameter list supplied in TIExecute call from jphTempo does not match required list of parameters
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic Error
This Process is not complete and cannot be run
Real Error
You had an error that you fixed but you didn't change the code. Type a blank space in the prolog to amend the code without really amending it and this will go away.
This Process is not complete and cannot be run
Real Error
You had an error that you fixed but you didn't change the code. Type a blank space in the prolog to amend the code without really amending it and this will go away.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic Error
Error: Prolog procedure line (8): Cell is not writeable
You are doing a viewzeroout in the prolog. The view has calcs and consolidations removed.
Real Error
This error occurs where you have n level values which have been overridden by a calculation. Only when the cube is next saved to disk will the n level values will be lost. This confuses TM1.
Solution
Unload and reload the cube.
(Sorry gave wrong soln before below)
1. Turn calcs off by renaming the .rux file. Unload the cube and then reload with calcs back on to find the n level values unwittingly retained.
2. Recreate the cube from the unload which has conflicting n level data removed.
Error: Prolog procedure line (8): Cell is not writeable
You are doing a viewzeroout in the prolog. The view has calcs and consolidations removed.
Real Error
This error occurs where you have n level values which have been overridden by a calculation. Only when the cube is next saved to disk will the n level values will be lost. This confuses TM1.
Solution
Unload and reload the cube.
(Sorry gave wrong soln before below)
1. Turn calcs off by renaming the .rux file. Unload the cube and then reload with calcs back on to find the n level values unwittingly retained.
2. Recreate the cube from the unload which has conflicting n level data removed.
Last edited by John Hammond on Tue Jun 21, 2011 8:25 am, edited 1 time in total.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic Error
Syntax error on or before <code fragment> logical expression
Possible Reason
You need to '@' prefix any comparator for alphanumeric operations with a string
eg
Change
SubOrganisation = IF( P3 = '%', 'AllMDX',JobName) ;
To
SubOrganisation = IF( P3 @= '%', 'AllMDX',JobName) ;
Syntax error on or before <code fragment> logical expression
Possible Reason
You need to '@' prefix any comparator for alphanumeric operations with a string
eg
Change
SubOrganisation = IF( P3 = '%', 'AllMDX',JobName) ;
To
SubOrganisation = IF( P3 @= '%', 'AllMDX',JobName) ;
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic Error
Within the TI process message box this flashes up:
Could not write Dimension Definition to disk storage
Reason
The disk is full on the server
Postscript
Thought this was the reason but see
http://forums.olapforums.com/viewtopic.php?f=3&t=2092
Within the TI process message box this flashes up:
Could not write Dimension Definition to disk storage
Reason
The disk is full on the server
Postscript
Thought this was the reason but see
http://forums.olapforums.com/viewtopic.php?f=3&t=2092
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic
Error registering object
Real
You have sufficient access to read an object and go into the editor but insufficient access to update that object.
Error registering object
Real
You have sufficient access to read an object and go into the editor but insufficient access to update that object.
- Steve Rowe
- Site Admin
- Posts: 2416
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Cryptic TM1 Messages Decoded
You also get that error if you try and save a TI with the same name of a (different)TI that already exists.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
Re: Cryptic TM1 Messages Decoded
Cryptic
2516 ERROR 2010-04-08 00:01:58.561 TM1.Rule TM1RuleImpl::LineGet - String overflow error, length = 526
Real Error
When doing a CellGetS and passing in a NULL or '' as a dimension, it will give give the error above.
Solution
Add an if statement to verify the dimension is not a non null or blank value.
2516 ERROR 2010-04-08 00:01:58.561 TM1.Rule TM1RuleImpl::LineGet - String overflow error, length = 526
Real Error
When doing a CellGetS and passing in a NULL or '' as a dimension, it will give give the error above.
Solution
Add an if statement to verify the dimension is not a non null or blank value.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Thanks Steve and itsPat for your contributions.
Cryptic:
tm1xl: An invalid argument was encountered
Cause:
You pressed an action button when the active cell in Excel begins with an IF formula.
Starter for 10 if anyone can come up with the why...
Cryptic:
tm1xl: An invalid argument was encountered
Cause:
You pressed an action button when the active cell in Excel begins with an IF formula.
Starter for 10 if anyone can come up with the why...
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic:
TM1 No data showing in Transaction log and logging is ON for the cube
Real reason
Transaction log uses GMT / Universal Time and not local time.
TM1 No data showing in Transaction log and logging is ON for the cube
Real reason
Transaction log uses GMT / Universal Time and not local time.
-
- Posts: 6
- Joined: Thu May 27, 2010 1:17 am
- OLAP Product: TM1, Infor PM Olap
- Version: TM1 9.4 + Infor PM Olap 3-10.x
- Excel Version: all
- Location: Singapore
Re: Cryptic TM1 Messages Decoded
Hi John,
I am struggling with that exact same problem at the moment and haven't got a handle on it yet, unfortunately I am not sure if I understand the solution steps you propose. Would you explain a little more in detail please?
thanks!
Marc
I am struggling with that exact same problem at the moment and haven't got a handle on it yet, unfortunately I am not sure if I understand the solution steps you propose. Would you explain a little more in detail please?
thanks!
Marc
John Hammond wrote:Cryptic Error
Error: Prolog procedure line (8): Cell is not writeable
You are doing a viewzeroout in the prolog. The view has calcs and consolidations removed.
Real Error
This error occurs where you have n level values which have been overridden by a calculation. You would think that when the cube is next saved to disk the n level values will be lost, but they are not. This confuses TM1.
Solution
1. Turn calcs off by renaming the .rux file. Unload the cube and then reload with calcs back on to find the n level values unwittingly retained.
2. Recreate the cube from the unload which has conflicting n level data removed.
- Martin Ryan
- Site Admin
- Posts: 1988
- Joined: Sat May 10, 2008 9:08 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
- Location: Wellington, New Zealand
- Contact:
Re: Cryptic TM1 Messages Decoded
Hi Marc,
The answers John suggests here are usually just one possible cause rather than the definitive reason for any given error. Please post a detailed description of your problem in the main forum, preferably including the code that's causing the problem.
Martin
The answers John suggests here are usually just one possible cause rather than the definitive reason for any given error. Please post a detailed description of your problem in the main forum, preferably including the code that's causing the problem.
Martin
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers.
Jodi Ryan Family Lawyer
Jodi Ryan Family Lawyer
-
- MVP
- Posts: 3113
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.0.9.18
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Cryptic TM1 Messages Decoded
And you also get that error whenever the Rules editor for the cube }ProcessSecurity contains errors like unexisting process names. For no matter what process. You cannot create a new process.Steve Rowe wrote:You also get that error if you try and save a TI with the same name of a (different)TI that already exists.
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Cryptic:
2011/04/01 10:26:08:Process "_big_string": System stack overflow, process terminated
In English:
You've probably exceeded the maximum string size in TM1. This is only 255 bytes in rel 90 and practically unlimited 94 onwards I think.
2011/04/01 10:26:08:Process "_big_string": System stack overflow, process terminated
In English:
You've probably exceeded the maximum string size in TM1. This is only 255 bytes in rel 90 and practically unlimited 94 onwards I think.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
tm1 cell type is consolidated divide by zero
George got here before but still spent 45 mins sticking in debugging messages
TM1 DOES NOT EXCEPTION ON DIVIDE BY 0 BUT LOADS INFINITY WHICH IS NOT A REAL NUMBER WHICH CAUSES CELLPUTN TO FAIL!
http://www.tm1forum.com/viewtopic.php?f=3&t=325
George got here before but still spent 45 mins sticking in debugging messages
TM1 DOES NOT EXCEPTION ON DIVIDE BY 0 BUT LOADS INFINITY WHICH IS NOT A REAL NUMBER WHICH CAUSES CELLPUTN TO FAIL!
http://www.tm1forum.com/viewtopic.php?f=3&t=325
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Message Faux
TM1 Invalid Number
Verite
You typed a dot which you couldn't see due to the excellent choice of fonts in the TI editor
TM1 Invalid Number
Verite
You typed a dot which you couldn't see due to the excellent choice of fonts in the TI editor
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Newsspeak:
Unknown process return status. Please contact Applix Support
English
You called a proc that has an Itemskip in the prolog.
Unknown process return status. Please contact Applix Support
English
You called a proc that has an Itemskip in the prolog.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
Psychobabble:
Tm1 viewzeroout Wrong Number of Dimension Elements
Mr Spock
It is spurious, Captain. TM1 is most illogical. Unload the cube and you will stop the error occurring. This is particularly where the cube has a view that references an MDX based subset.
Tm1 viewzeroout Wrong Number of Dimension Elements
Mr Spock
It is spurious, Captain. TM1 is most illogical. Unload the cube and you will stop the error occurring. This is particularly where the cube has a view that references an MDX based subset.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
OMG!!!
tm1 string in quotes too large
KEWL!!!
You coded a triple quote ''' which your aging peepers could not make out.
tm1 string in quotes too large
KEWL!!!
You coded a triple quote ''' which your aging peepers could not make out.
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Cryptic TM1 Messages Decoded
tm1 error opening the logfile cube drill
Unbelievably this appears on a drill. What actually has occured is that the dimensionality of the cube has changed and you are no longer passing the right number of arguments to the drill proc.
Unbelievably this appears on a drill. What actually has occured is that the dimensionality of the cube has changed and you are no longer passing the right number of arguments to the drill proc.