XML for Analysis - Microsoft SQL Server 2008 Analysis Services - page 592

<detail>
<Error ErrorCode=”3238658054” Description=”Query (1, 9) The dimension '[x]'
➥ was not found in the cube when the string, [x], was parsed.” Source=”Microsoft SQL
➥ Server 2008 Analysis Services” HelpFile=””>
<Location xmlns=”http://schemas.microsoft.com/analysisservices/2003/engine”>
<Start>
<Line>1</Line>
<Column>9</Column>
</Start>
<End>
<Line>1</Line>
<Column>9</Column>
</End>
<LineOffset>0</LineOffset>
<TextLength>1</TextLength>
</Location>
</Error>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Errors That Occur After Serialization of the Response Has Started
Because the SOAP specification allows the SOAP body to have only one child element, if
an error occurs after the server has started to produce the result, a SOAP fault cannot be
created. In such cases, Analysis Services generates an <Exception> element.
An exception can occur at any point of execution of a method. If the server has already
started to serialize the response and has produced multiple nested XML elements at the
time of the error, the server has to close all open tags (to produce valid XML) and serialize
the error information.
To mark the exact place where the problem occurred, an <Exception> element is placed at
the spot. After the server has closed all the open XML elements, it serializes the error
information in a <Message> element. (There could be more than one message element in
the response.) If you are familiar with exception handling in the .NET Framework or other
languages that support exceptions, the following analogy will help: The Exception
element is similar to a throw statement; the Message element corresponds to the catch
statement.
The following example demonstrates how exception/message elements work:
<Axes>
<Axis name=”Axis0”>
...