In the middle of adding a new dimension to our cube and ran into an error message stating “The server sent an unrecognizable response”.
Goggled for help and most of the help led me down the path of reviewing the dimension’s columns attributes; specifically the KeyColumns sub-property that reads “InvalidXMLXCharacters”.
The attribute has three possible values Preserve, Remove, and Replace.
Here is a sampling of corresponding web documents:
- ‘Invalid characters’ in Analysis Services cube
- SQL Server Forums \ SQL Server Analysis Services \ Getting Error “The server sent an unrecognizable response” on running MDX query
Change InvalidXMLCharacters from Preserve to Remove
- Access the “Dimension Structure”
- Select each attribute and right click on the attribute
- Navigate to the “Solution Explorer”
- Transverse to the “NameColumn” property
- Navigate to the Sub property titled “InvalidXMLCharacters”
- And, I will suggest that you change the property’s value from Preserve to Remove
Review Data, looking for special characters
Using a nice query posted by Jitendra:
Solving MDX query error “The server sent an unrecognizable response”
was able to confirm that the data set does not in fact have special characters; or more specifically the ones that are specified in Jitendra’s solution.
- Our crude solution was to create a new database table that resembles the original dimension table. But, in this case carefully populate with cleansed data; data that we were sure only contained English character set.
- Accessed the Data Source view, and added the new Table
- Created a new dimension against the new Table
- Accessed the Cube and attached a new dimension
Now I see why they say it is best to have separate tables for your OLTP and OLAP data sets.