cancel
Showing results for 
Search instead for 
Did you mean: 

Error message when adding a Calculation (Invalid Token)

gleo_SRAM
Active Contributor
0 Kudos

We upgraded our BW system a fortnight ago and since then, we cannot add any calculations to any Analysis for OLAP reports.


We get the attached error message when we do -

We are using SAP BusinessObjects BI Platform 4.1 Support Pack 2 - Version: 14.1.2.1121

We have the same issue on every single query available to us in Business Objects from the BW / BICS connection. Anyone with saved Workspaces that had calculations saved in them gets the same message so they can't use these reports.

I have looked on SDN / OSS and can't find anything relevant that is current.

Suggestions welcome!

Gill

Accepted Solutions (1)

Accepted Solutions (1)

TammyPowlas
Active Contributor
0 Kudos

Gill - there is a KBA related to the error message but not on your environment here about switching authentication:

http://service.sap.com/sap/support/notes/1903888

http://service.sap.com/sap/support/notes/1801353

What is more interesting too is that it references an SAP internal note that we (non-SAP) cannot access

I hope SAP sees this and can take a look.

gleo_SRAM
Active Contributor
0 Kudos

Thanks Tammy,

I had seen that note but couldn't understand how changing the olap connection could have a positive impact - strange!

My Analysis workspaces all work now, the WebI documents I had that shared the olap connections don't but that's another days work. Perhaps some config we are shy getting WebI to recognize the SSO connectivity.

I will leave this discussion open for a wee while in case there is another solution other than the SSO workaround!

Thanks

Gill

I_MCA
Employee
Employee
0 Kudos

Hi Gill

The Notes mentioned by Tammy relate to WebI. I'm not aware of similar AOLAP issues though.

WebI and AOLAP both use the same OLAP connections and the original issue was with the JCo component which we also both use. However this was fixed in 4.0 SP06. Using SSO is just a workaround.

Although the issue was fixed in 4.0 SP06, it's not clear if the fix was propagated into 4.1 SP02. I would suggest contacting support and bring the above notes to their attention.

Regards

Ian

Answers (0)