Attribut key not found vs Characters

Hello,

When I process one of my dimension, I have an error message "attribut key not found".

It's not link with records present in fact table and not in dimension table, but with the value of the attributs which contain symbols.

To be accurate I integrate first data from a database DB2 AS400 to sql server 2005 (with provider ADO.NET ODBC).

In the database DB2 AS400 the data could have different languages (chinese, japanese,...) but so far it is not necessary to see data with the correct language (moreover the database is not setup in Unicode and 1 specific language = 1 CCSID value...).

So I could have a client name with symbols in the name like :"€"

I think this is what SSAS doesn't like when I process the dimension...

When I set the KeyNotFound property of the dimension to "Ignore Error", I can after process my dimension, but when I browse it, I have an error ("the server sent an unrecognizable response").

Do you have any idea to how to deal with this error?

I think about eliminating the symbols like "€" to begin, but I don't know if there are better solutions (and less dirty...).

Thanks,

Guillaume

There are two properties on the attribute's key columns you should check: Collation and InvalidXmlCharacters. The first will set the character set and case sensitivity for the column in question. When not set at the column level it inherits from the parent object, usually all the way up to the default settings specified when the OLAP server is installed. This should allow the server to understand when two different character codes represent equivalent or different characters. The second property, InvalidXmlCharacters, determines the behavior of the server when it encounters characters that are not valid in XML without some encoding. For performance reasons, the server will not check for the presence of such characters unless you set the InvalidXmlCharacters property. As a result if such invalid characters exist, the response the server sends to the client will not be valid XML.|||

Thanks for you reply, it works now!

I need to ignore the "attribut key not found" error to be able to process the dimension, but thanks to the option InvalidXmlCharacters set to "remove" I can browse my attributs.

Guillaume