TM1.Mdx.Interface Syntax error

[John Hammond]

Periodically in the TM1 log we get this appearing.

Code: Select all

5492   ERROR   2010-06-15 16:39:53.686   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34
5492   ERROR   2010-06-15 16:39:54.811   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34
5492   ERROR   2010-06-15 16:39:55.108   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34
5492   ERROR   2010-06-15 16:39:55.405   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34
5492   ERROR   2010-06-15 16:39:55.983   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34
5492   ERROR   2010-06-15 16:39:56.686   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34
5492   ERROR   2010-06-15 16:39:56.702   TM1.Mdx.Interface   Syntax error at or near: ')}', character position 34

1. There is no pattern to its appearance - by time, after running a TI etc
2. I have opened all MDX subsets without error
3. It does not seem to be causing a problem.

Does anyone have any ideas as to what might be causing this?

As usual all replies appreciated and acknowledged.

Regards

John

[kaazimraza]

Hey John

Were you able to get around this error? I am getting this error only when I execute a process from Cognos Insight. If I run the same process from Architect, it works as expected.

[rmackenzie]

1. There is no pattern to its appearance - by time, after running a TI etc
2. I have opened all MDX subsets without error
3. It does not seem to be causing a problem.

Does anyone have any ideas as to what might be causing this?

I think I've seen something similar to this, and, from your list, I would be looking at Excel reports that used custom MDX for their TM1RPTROW formulas in active forms. If the MDX statement is being built up from concatenating different cells (from data validations etc) and something has gone wrong in the workbook, then you could end up with invalid MDX.

TM1 evaluates these MDX statements on the fly (AIUI) (rather than creating registered subsets with dynamic expressions) which is why there's no pattern and why there's no evidence in subsets - it just relies on a user rebuilding the form ad hoc.

If you need further information from the log then perhaps you can try putting the following line in tm1s-log.properties:

Code: Select all

log4j.logger.TM1.MDX.Interface=DEBUG

I've not done that before so I don't know how much garbage you'd get in the log. But presumably you'd get some more information to help you track down the offending active form (if I'm right).

Edit - I just noticed the date on the original post!... I'm not familiar enough with the internals of Insight to properly comment on that issue, but the debugging item for logging would seem to still be a good bet for that as well.

[kaazimraza]

It looks like Cognos Insight was going crazy because of unnamed subsets. I stopped getting these errors once i replaced all unnamed subsets with named ones.

[macsir]

I have this similar issue periodically but it doesn't seem to be a problem. It only happens when the server is shutting down after destroying dimensions but not always.
Anyone has any idea? We don't use Cognos Insight.

Code: Select all

468   []   INFO   2014-01-07 14:00:35.554   TM1.Server   TM1ServerImpl::Destroy: Save server data
1468   []   INFO   2014-01-07 14:00:35.554   TM1.Server   TM1ServerImpl::Destroy: destroy chores
1468   []   INFO   2014-01-07 14:00:35.554   TM1.Server   TM1ServerImpl::Destroy: destroy processes
1468   []   INFO   2014-01-07 14:00:35.569   TM1.Server   TM1ServerImpl::Destroy: destroy blobs
1468   []   INFO   2014-01-07 14:00:35.585   TM1.Server   TM1ServerImpl::Destroy: destroy sets
1468   []   INFO   2014-01-07 14:00:35.585   TM1.Server   TM1ServerImpl::Destroy: destroy groups
1468   []   INFO   2014-01-07 14:00:35.585   TM1.Server   TM1ServerImpl::Destroy: destroy clients
1468   []   INFO   2014-01-07 14:00:35.585   TM1.Server   TM1ServerImpl::Destroy: destroy cubes
1468   []   INFO   2014-01-07 14:00:35.632   TM1.Server   TM1ServerImpl::Destroy: destroy dimensions
1468   []   ERROR   2014-01-07 14:00:35.694   TM1.Mdx.Interface   Syntax error at or near: ' [DimXYZ] )}, 0)}, ASC)}, { [DimXYZ ... ', character position 63
1468   []   ERROR   2014-01-07 14:00:35.694   TM1.Mdx.Interface   Syntax error at or near: ' [DimXYZ] )}, 0)}, ASC)}, { [DimXYZ ... ', character position 63
1468   []   ERROR   2014-01-07 14:00:35.710   TM1.Mdx.Interface   Syntax error at or near: ' [DimXYZ] )}, 0)}, ASC)}, { [DimXYZ ... ', character position 63
1468   []   INFO   2014-01-07 14:00:35.741   TM1.Server   TM1ServerImpl::Destroy: destroy connections
1468   []   INFO   2014-01-07 14:00:35.741   TM1.Server   TM1ServerImpl::Destroy: Destroy unregistered objects
1468   []   INFO   2014-01-07 14:00:35.741   TM1.Server   TM1ServerImpl::Destroy: Commit changes
4348   []   INFO   2014-01-07 14:00:37.366   TM1.Server   Terminating Admin Server poller thread.
1468   []   INFO   2014-01-07 14:00:37.382   TM1.Server   Server shutdown

[macsir]

Anyone has some ideas?

[Wim Gielis]

Anyone has some ideas?

Can you look for the string [DimXYZ] in all of the *.sub files of your TM1 data directory ?
Is it found ? If so, do you see anything weird with the subset and/or the dimension ?

[tomok]

Anyone has some ideas?

Yes. That's TM1 telling you there is a syntax error in an MDX query a user tried to execute. Usually you get this error from an active form, when you have a problem with generated MDX in a TM1RPTROW formula.

[Wim Gielis]

Tomok is right. In addition, please look at uploaded websheets for wrong MDX statements.

[macsir]

Nothing wrong in the sub files. But I did find that MDX from activeform report. However, when I tested this MDX in the subset editor, it is right without any syntax error.

[Wim Gielis]

How does the MDX look like, and does it use cell references or other inputs from Excel ?

[macsir]

It is using cell reference. After I have re-saved the activeform again into the server, looks like so far so good. No such error appearing. I will keep eyes on it.

[Wim Gielis]

Thanks for keeping an eye on it and reporting back later.