Errors generally
fall into one of five categories, and are assigned the appropriate
error code for that category. The following table describes these
error codes:
Error Codes
|
|
|
Specifies an invalid
user name or password (the client application might want to re-prompt
the user for credentials).
|
|
Specifies a client error
(the client application might want to pass in different parameters).
This error might occur for one of the following reasons:
-
-
required parameter is missing
-
invalid request against schema
-
invalid stored process name (for
XMLA Web services only)
-
no ReadMetadata permission for
the stored process
|
|
Specifies a SAS error.
This error is generated when the stored process generates a SYSCC
macro variable that is not listed in the AcceptableSysccList configuration
option. An additional attribute is added to indicate the actual error
number that SYSCC was set to. The SYSMSG string is also included in
the message.
|
|
Specifies a configuration
error. This indicates a problem that the administrator of the service
should be notified about. The administrator should be able to examine
logs on the service to determine the cause of this error. This error
might occur for one of the following reasons:
-
invalid default credentials for
the anonymous user
-
invalid trusted credentials
-
metadata server or stored process
server is unreachable
-
invalid configuration file
|
|
Specifies a time-out
error. This error occurs if the user configures SAS BI Web Services
with a stored process time-out and the execution of a stored process
exceeds this time-out.
|
Note: Before SAS 9.2, XMLA returned
an error code of
99
for almost all
errors.
The following code is
an example of a generated SOAP fault that has an error code of
4000
:
<SOAP-ENV:Fault>
<faultcode>Server</faultcode>
<faultstring>The XML for Analysis provider encountered an error</faultstring>
<faultactor>XML for Analysis Provider>XML for Analysis Provider</faultactor>
<detail>
<sas:Fault code="4000">
<sas:Exception message="The configured credentials are invalid.">
<sas:Exception message="The config file contains invalid metadata
credentials."/>
<sas:Exception message="The user 'anon' is unknown.">
<sas:Exception message="'anon' is not defined in metadata."/>
</sas:Exception>
</sas:Exception>
</sas:Fault>
</detail>
</SOAP-ENV:Fault>