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

In such a case, it could be that the provider was not able to parse the SOAP enve-
lope of the request. For example, the method name was misspelled. Or maybe a
method was called successfully, but the error occurred during execution of the
method. As another example, if an MDX command that contains a syntax error is
passed into the Execute method, the XML/A provider will generate an error.

. Errors that occur during the execution of the request, after part of the request

have already been generated by the server

For example, the <Batch> command might have multiple subcommands. If one of
them succeeds and a result is generated, but the second one fails, the XML/A
provider will generate an exception.

. Errors in the response

In such a case, execution of the request succeeds, but the error occurs when the
server is creating the response. For example, if one of the cells contained in the
resultset has a secured value, the XML/A provider will generate a cell error.

. Warnings that are issued when some problem occurs that does not prevent

the execution from completing

For example, if during creation of the cube the locale specified by the user is not
supported, the server creates a cube using a default locale. Because the cube is
usable, Analysis Services does not fail the execution of the command and does
not roll back the cube-creation transaction. Everything might look normal, but
the data will not be in the locale the user expects—and she probably won't know
it. The warning lets her know about the different locale settings used by the server.

Errors That Result in the Failure of the Whole Method

For errors that result in the failure of the whole method (category 1), the XML/A error-
handling mechanism is built on top of SOAP. It uses the SOAP FAULT message that carries
error information within a SOAP message response. Table 32.2 shows three child elements
of the Fault element that can offer information about the error contained in the SOAP
message.

TABLE 32.2 Child Elements of the Fault Element
<Fault> Child Element Description

Identifies the fault that occurred by an error code number <faultcode>

An explanation of the fault <faultstring>

Application-specific information about the error

<detail>

According to the XML/A specification, the <detail> element should contain one or more
Error elements that provide detailed information about the error that occurred. Table 32.3
describes the four attributes of the Error element.