Essbase Error 1020034 – Binary spreadsheet table token error – Solutions 8

Someday, Somewhere (no I’m not singing “Someday Somewhere” by MLTR, I’m already together with her 😉 ) you might have seen or you might end up getting this error while retrieving data using Smart View.

When I ended up getting this error, the first thing I checked was whether there are any hidden instances of EXCEL and there were none!!!

I was thinking that probably “Reduce Excel File size” option was causing the problem (not sure why I thought that way, maybe because it was not reducing the file size), so I disabled it and went ahead with a refresh.

I was under the impression that I’ll get the same error but to my surprise the refresh went fine!!!

Now I wanted to prove that it is because of “Reduce Excel file size”. I enabled the option, performed a refresh believing that I’ll get the error and I could file a bug (or even curse people).

Nope again no errors!!!! This was a forgotten story and then yesterday a colleague of mine called up and asked “Have you seen this error?” (You should have seen the smile on my face).

He was going to re-create the sheet and I advised him not to, “Just perform a refresh”. (with a heavy tone) (He might have thought this guy is crazy, didn’t say anything and went with the refresh).

He didn’t get the error and his refresh returned data from Essbase.

Back of my mind I wanted him to get the error and prove that it was because of “Reduce Excel file size”. But it seems like that is not the reason.

If you are getting this error, wait for some time (or even disconnect your connections), and perform a refresh.

I’m listing out possible solutions for the error here.

  1. Check whether you’ve a correct version of Smart View/ EXCEL Add-in
  2. Check for hidden EXCEL instances, close them and perform a refresh.
  3. Perform a refresh and see whether it solves the issue.
  4. Check whether you’ve any EXCEL formulas that is returning strings.
  5. If there is another solution please post it here. 🙂


About Celvin Kattookaran

I’m an EPM Consultant, my primary focus is on Hyperion Planning and Essbase. Some of you from Hyperion Support team might recognize me or have seen my support articles, I was with the WebAnalysis Support Team. I'm an Independent Consultant with “Intekgrate Corporation” based out of Aurora office. I’m from God’s Own Country (Kerala, India), lived in all southern states of India, Istanbul and Johannesburg (and of course United States). I’m core gamer :) and an avid reader. I was awarded Oracle ACE Director for my contributions towards EPM community.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

8 thoughts on “Essbase Error 1020034 – Binary spreadsheet table token error – Solutions

  • rakesh kumar

    I also faced this few days back and it was so frustrating…what i did is copied all my content into a new excel and deleted the old excel and saved this new excel with a bit different name than the previous one and then again did refresh and it worked..but if you save it with the same name if gives the same error. So not sure what it looks for this solved my issue.

  • Celvin Kattookaran

    one more solution

    The issue is solved by the following workaround:
    Uncheck 'Preserve Formulas and Comments on Adhoc operation (except pivot)' on the member option table. The replacement field is kept as #NumericZero.

    Save the workbook (after deleting the extraneous rows).

  • iso2000

    I found that the error was caused by thousands of blank rows being wrongly included in the Smart View grid.

    I ran this VB:

    Sub Last_Cell()


    End Sub

    which goes to the last active cell of the sheet. Use this to delete the unneeded rows and refresh. No need to save as a new workbook.

  • Shawn M

    i was getting the message because the Essbase table extended to row 1800 of a spreadsheet that only should have had about 77 rows. I did a CTRL-End, highlighted all rows from there to the last row of data (Row 77), and deleted the entire rows. Refreshed with no problem.

    • Celvin Kattookaran Post author

      I thought I did update this one on the post, I saw this like an year and half back. Thanks for updating Shawn M