EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB46033: "Error Saving and publishing the cube. Invalid Unicode value U+D96B" error message appears when importing data from an Excel file in MicroStrategy Web 9.4.1 and above.


Community Admin

• Strategy


"Error Saving and publishing the cube. Invalid Unicode value U+D96B" error message appears when importing data from an Excel file in MicroStrategy Web 9.4.1 and above.

SYMPTOM:
When trying to publish a cube created from an Excel file using Data Import in Strategy Web 9.4.1 and above, the following error is seen:
 

ka04W000000Ofh0QAC_0EM4400000026KB.png


Data Import
Error saving and publishing the Cube: (QueryEngine encountered error: MBase::WideCharToUnicodeValue: Invalid UNICODE value U+D96B... 

CAUSE:
All characters imported through data imported into Strategy Web must be valid in Unicode. In this case, U+D96B is not a valid UNICODE value.
For more information on the codepages accepted by Strategy Data Import, refer to the documentation on Best Practices for Importing Data into MicroStrategy Web

 

ACTION:
Remove the non-unicode character(s) from the Excel file being imported. Several methods could be utilized to find the offending character(s), depending on the size of the Excel dataset being imported:

  1. Use a Unicode lookup tool to determine what the character looks like, then manually find this character in the Excel dataset.
  2. To find the character(s) in a large dataset, perform a binary search on the Excel dataset:
    Split the dataset into two halves, into separate Excel files. Import and publishing both Excel files using Strategy Data Import. If only one of these files cause the error to be shown, then continue this process of halving and testing until the offending column(s) and row(s) are found.

Comment

0 comments

Details

Knowledge Article

Published:

May 19, 2017

Last Updated:

October 27, 2017