I have a problem with Analysis Server 2005, more the XMLA side on the
msmdpump.dll.



My analysis cube contains source columns for dimensions set as nvarchar,
allowing me to store Cyrillic and Chinese characters. In AS 2K, these
characters are showing fine in the client application. Now I have moved to
AS2005 and the data displays fine in the SSBI Dev Studio. But when the front
end tool receives the data from the msmdpump.dll Cyrillic and Chinese
characters in the XMLA are replaced by question marks. Is there some setting
that would make msmdpump.dll to retrieve non-Latin Characters correctly?

Do you know what API the front-end tool uses to access the server over HTTP?
Does it use ADOMD.Net or OLE DB?

If it uses ADOMD.NET (or XMLA directly), then the problem is most likely
with msmdpump.dll not returning an HTTP header properly indicating that the
result is UTF-8. Unfortunately there isn't really a workaround for this
except for switching to use an OLE DB based client application, or using a
TCP connection to the server instead of HTTP.

You can verify this by using a HTTP trace utility (available from the net)
to see if the Content-Type header in the HTTP response specifies "text/xml"
or "text/xml; charset=utf-8" (the latter is what you need).

Alternatively, you can contact product support and open a case to get this
issue fixed.

Thanks,
Akshai

--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Mitak" <dkfake (AT) hotmail (DOT) com> wrote

Akshai,

Thank you for the reply. I reached the same conclusion already. We are using
a third party control for our front-end. It uses msmdpump.dll over HTTP as a
web service (I suspect) and as you mentioned since the response does not
return the proper utf-8 encoding setting in the soap packet the automatic
serialization does not take the proper encoding into account. However, I
used ascmd sample utility provided by Microsoft with the -o command
parameter which saves the output into a file and does custom utf-8 encoding
in the process which seems to work properly. In other words maybe another
workaround is to implement a custom soap serialization which does utf-8
encoding when the soap packed is returned to the client from msmdpump.dll.

Thanks again!


"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

Yes, theoretically you could create a proxy ISAPI DLL (or something like
that) which would modify the Content-Type to add the utf-8 marker or
implement some other similar solution on the client side to force the client
app to treat the response as utf-8.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Mitak" <dkfake (AT) hotmail (DOT) com> wrote