| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Analytics Message Reference > Siebel Analytics Messages >
XML Gateway Messages
This category contains message numbers 63xxx - 64xxx.
63001
The file @1%s is not found.
Cause. The path to the named XML file is not correct or the file does not exist.
Response. Correct the path or URL to the specified XML file, and try the action again.
63002
Failing to obtain XML data islands or HTML tables in the file @1%s.
Cause. The named HTML file does not contain any XML data islands enclosed in XML tags or HTML tables.
Response. Check the contents of the HTML file, and make the necessary corrections.
63003
File @1%s with unsupported suffixes; currently only .xml, .htm, and .html are supported.
Cause. The named file contains suffixes other than .xml, .htm, and .html.
Response. Modify the file to contain only supported suffixes.
63004
Attempting to store a column @1%s which does not exist in the schema; the column is ignored.
Cause. An attempt was made to store a column which does not exist in the schema. This could be caused by XML features that are not currently supported by Siebel Systems.
Response. This is an informational message. No action is required.
63005
No file has been found in the specified directory path @1%s
Cause. The named directory for import does not exist, is empty, or the wildcard (if specified) does not match any existing file names.
Response. Specify a valid directory path and file for import.
63006
The number of columns generated from the schema is less than those in the data @1%s; possible information loss.
Cause. Siebel Systems may not currently support some features in the schema.
Response. Contact Siebel Systems technical support for assistance.
63007
Warning: Problems were encountered in handling the following files:
Cause. Problems were encountered in loading, parsing, or flattening the named files.
Response. Review the contents of the problem files, and correct any problems. If necessary, contact Siebel Systems technical support for assistance.
64001
The file @1%s is not found.
Cause. The path to named XML file is not correct or the file does not exist.
Response. Correct the path or URL to the specified XML file, and try the action again.
64002
The table @1%s is not found in file @2%s loaded.
Cause. The unqualified name of the table is not found in the list of opened tables and tables to be opened.
Response. Verify that the name of the table is correct, and try the action again.
64003
Msxml cannot load and parse in memory the object contained in @1%s.
Cause. The named text fragment does not conform to proper XML syntax.
Response. Review the content of the XML or HTML file that contains the specified text fragment, correct any problems, and try the action again.
64004
Failed to flatten the object @1%s.
Cause. Problems were encountered in flattening the specified object.
Response. Review the content of the XML or HTML file that contains the specified text fragment, correct any problems, and try the action again.
64005
Failure in executing HTTP request for object @1%s.
Cause. Problems were encountered during execution of an HTTP GET request for the named object.
Response. Check the URL of the named XML or HTML file, correct any problems, and try the action again.
64006
Failing to parse the file @1%s.
Cause. The path to the named XML file is not correct or the file does not exist.
Response. Correct the path or URL to the named file, and try the action again.
64007
Declarations missing for element or attribute @1%s.
Cause. A declaration for the specified attribute or element in all scopes was not found.
Response. Review the content of the file, correct any problems, and try the action again.
64008
Internal Error: the number of columns to save in textstreamstore is less than originally declared.
Cause. An internal error occurred.
Response. Contact Siebel Systems technical support for assistance.
64009
Internal Error: failure in storing data to virtual table.
Cause. An internal error occurred. The temporary directory of the local machine may be full.
Response. If the temporary directory is full, make additional space available. If the temporary directory is not full, contact Siebel Systems technical support for assistance.
64010
Internal Error: no fully qualified column name has been given to column for binding to record.
Cause. An internal error occurred.
Response. Contact Siebel Systems technical support for assistance.
64011
Internal Error: attempt to bind record to an non-existent column.
Cause. The column name specified in the physical table does not match any element name in the corresponding XML file.
Response. Verify that the column name specified in the physical table matches the corresponding element name in the XML file. If the problem persists, contact Siebel Systems technical support for assistance.
64012
Internal Error: unable to get record for the specified column.
Cause. An internal error occurred.
Response. Contact Siebel Systems technical support for assistance.
64013
Unable to handle documents of less than two levels deep @1%s.
Cause. XML documents require a second level element to act as a row delimiter. XML documents that are less than two levels deep cannot be flattened.
Response. Add a row delimiter for each row, and try the action again.
64014
Unable to obtain columns for flattening @1%s.
Cause. XML documents require a second level element to act as a row delimiter. XML documents that are less than two levels deep cannot be flattened. Other possible causes are that the HTML table does not contain any column values even though there are column headings, or the XML document does not contain any elements inside the second level element.
Response. Add a row delimiter for each row, and make sure that each HTML table or XML file contains some column values. After making the corrections, try the action again.
64015
No files have been loaded successfully from directory @1%s.
Cause. Problems were encountered in loading, parsing, or flattening files from the named directory.
Response. Review the contents of the files in the named directory, and correct any problems. If necessary, contact Siebel Systems technical support for assistance.
64016
Cannot write to specified file @1%s.
Cause. Problems were encountered in writing to the named file. An disk may be out of space, or there may be permission problems with the specified path.
Response. Check the disk space of the drive that is to contain the specified file and make additional space available, if necessary. Verify that the path is writable. If the problem persists, contact Siebel Systems technical support for assistance.
64017
Cannot allocate a write buffer for the specified file @1%s.
Cause. Problems were encountered in allocation of the write buffer for the named file. There may be insufficient memory available.
Response. Make additional memory available by shutting down unnecessary applications. Try the action again. If necessary, restart the Siebel Analytics Server.
64018
Cyclic inclusion of node @1%s not allowed in file @2%s.
Cause. Cyclic inclusion of the named element was detected in the specified file.
Response. Change the schema to give the cyclically nested elements different names in different scopes.
64019
No data is found in file @1%s.
Cause. No data is contained in the named XML file. The file may be a schema file.
Response. Verify that the named XML file is not a schema file, and contains appropriate XML data. Correct any problems, and retry the action.
64020
HTTP Authentication Failure for @1%s.
Cause. The user ID and password pair is invalid.
Response. Verify that the user ID and password pair is valid and has the right to access the data source. Correct any problems and retry the action.
64021
The table @1%s is not found for import.
Cause. The unqualified name of the table is not found in the list of opened tables and tables to be opened.
Response. Verify that the name of the table is correct, and then try the action again.
64022
The table @1%s could not be contained in the URL @2%s specified in the Connection Object.
Cause. The unqualified name of the table is not found in the list of opened tables and tables to be opened. The specified URL may be unavailable, or incorrect.
Response. Review the URL associated with the Connection Pool or specified during the import process, make the appropriate changes, and try the action again.
64023
@1%s for table @2%s
Cause. Cannot establish read access to the file that contains the named table. The table name may be incorrect.
Response. Review the name of the table, make the appropriate changes, and try the action again.
64024
Unable to obtain rows for flattening @1%s.
Cause. The row data necessary to create the HTML tables cannot be obtained. There may be a problem with the data format.
Response. Review the data and the data format, make the appropriate changes, and try the action again.
64025
Cannot access @1%s: @2%s. Please check the path and the adequacy of the access privilege.
Cause. The named path cannot be accessed. This may occur because the path is invalid or the permissions are incorrect.
Response. Review the path and the associated permissions, and make the appropriate changes. Try the action again.
64026
The structure of the XML file @1%s is not currently supported.
Cause. The structure of the named XML file is not currently supported.
Response. Change the structure of the file and try the action again.
64027
There are more than one second level, or row delimiting, elements, in XML file @1%s.
Cause. There are multiple second level, or row delimiting, elements, in the named XML file.
Response. All second level elements in the XML file must have the same name. Review the contents of the named file, make the necessary corrections, and try the action again.
64028
Stat() call on table @1%s failed.
Cause. The data file that contains the named table no longer exists. The file may have been moved or deleted, or the path may be incorrect.
Response. Verify the existence of the data file, correct any problems, and try the action again.
64029
Loading of URL @1%s failed: @2%s.
Cause. The named URL is invalid or does not exist.
Response. Verify the URL and be sure that it is accessible. After making the appropriate corrections, try the action again.
64030
Opening of temporary output file failed: @1%s.
Cause. The named temporary output file does not exist or user does not have read permission.
Response. Verify that the named file exists and can be opened. Verify that the permissions are set appropriately. After making the necessary corrections, try the action again.
64031
Execution of user-specified filter @1%s failed for @2%s.
Cause. The named filter program or data file does not exist or the user does not have read/execute permission.
Response. Verify the existence of the filter and the data file. Verify that the permissions are set appropriately. After making the necessary corrections, try the action again.
64032
HTTP_STATUS_ACCEPTED (202): The request has been accepted for processing, but the processing has not been completed.
Cause. The request has been accepted for processing, but the processing has not been completed.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64033
HTTP_STATUS_PARTIAL (203): The returned meta information in the entity-header is not the definitive set available from the origin server.
Cause. The returned meta information in the entity-header is not the definitive set available from the origin server.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64034
HTTP_STATUS_NO_CONTENT (204): The server has fulfilled the request, but there is no new information to send back.
Cause. The server has fulfilled the request, but there is no new information to send back.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64035
HTTP_STATUS_RESET_CONTENT (205): The server has fulfilled the request, but there is no new information to send back.
Cause. The server has fulfilled the request, but there is no new information to send back.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64036
HTTP_STATUS_PARTIAL_CONTENT (206): The server has fulfilled the partial GET request for the resource.
Cause. The server has fulfilled the partial GET request for the resource.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64037
HTTP_STATUS_AMBIGUOUS (300): The server could not decide what to return.
Cause. The server could not decide what to return.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64038
HTTP_STATUS_MOVED (301): The requested resource has been assigned to a new permanent URI, and any future references to this resource should be done using one of the returned URIs.
Cause. The requested resource has been assigned to a new permanent URI. Any future references to this resource should be made using one of the returned URLs.
Response. This is an informational message. No action is required. However, you may wish to update the underlying related URL, if necessary. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64039
HTTP_STATUS_REDIRECT (302): The requested resource resides temporarily under a different URI.
Cause. The requested resource resides temporarily under a different URI.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64040
HTTP_STATUS_REDIRECT_METHOD (303): The response to the request can be found under a different URI and should be retrieved using a GET method on that resource.
Cause. The response to the request can be found under a different URI and should be retrieved using a GET method on that resource.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64041
HTTP_STATUS_NOT_MODIFIED (304): The requested resource has not been modified.
Cause. The requested resource has not been modified.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64042
HTTP_STATUS_USE_PROXY (305): The requested resource must be accessed through the proxy given by the location field.
Cause. The requested resource must be accessed through the proxy given by the location field.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64043
HTTP_STATUS_REDIRECT_KEEP_VERB (307): The redirected request keeps the same verb. HTTP/1.1 behavior.
Cause. The redirected request keeps the same verb. HTTP/1.1 behavior.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64044
HTTP_STATUS_BAD_REQUEST (400): The request could not be processed by the server due to invalid syntax.
Cause. The request could not be processed by the server due to invalid syntax.
Response. For additional information on HTTP STATUS codes, seeW3C at http://www.w3c.org. Contact Siebel Systems technical support for assistance.
64045
HTTP_STATUS_DENIED (401): The requested resource requires user authentication.
Cause. The requested resource requires user authentication.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64046
HTTP_STATUS_PAYMENT_REQ (402): Not currently implemented in the HTTP protocol.
Cause. Not currently implemented in the HTTP protocol.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64047
HTTP_STATUS_FORBIDDEN (403): The server understood the request, but is refusing to fulfill it.
Cause. The server understood the request, but is refusing to fulfill it.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64048
HTTP_STATUS_NOT_FOUND (404): The server has not found anything matching the requested URI.
Cause. The server has not found anything matching the requested URI.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64049
HTTP_STATUS_BAD_METHOD (405): The method used is not allowed.
Cause. The method used is not allowed.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64050
HTTP_STATUS_NONE_ACCEPTABLE (406): No responses acceptable to the client were found.
Cause. No responses acceptable to the client were found.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64051
HTTP_STATUS_PROXY_AUTH_REQ (407): Proxy authentication required.
Cause. Proxy authentication required.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64052
HTTP_STATUS_REQUEST_TIMEOUT (408): The server timed out waiting for the request.
Cause. The server timed out waiting for the request.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64053
HTTP_STATUS_CONFLICT (409): The request could not be completed due to a conflict with the current state of the resource. The user should resubmit with more information.
Cause. The request could not be completed due to a conflict with the current state of the resource. The user should resubmit with more information.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64054
HTTP_STATUS_GONE (410): The requested resource is no longer available at the server, and no forwarding address is known.
Cause. The requested resource is no longer available at the server, and no forwarding address is known.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64055
HTTP_STATUS_LENGTH_REQUIRED (411): The server refuses to accept the request without a defined content length.
Cause. The server refuses to accept the request without a defined content length.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64056
HTTP_STATUS_PRECOND_FAILED (412): The precondition given in one or more of the request header fields evaluated to false when it was tested on the server.
Cause. The precondition given in one or more of the request header fields evaluated to false when it was tested on the server.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64057
HTTP_STATUS_REQUEST_TOO_LARGE (413): The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
Cause. The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64058
HTTP_STATUS_URI_TOO_LONG (414): The server is refusing to service the request because the request URI is longer than the server is willing to interpret.
Cause. The server is refusing to service the request because the request URI is longer than the server is willing to interpret.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64059
HTTP_STATUS_UNSUPPORTED_MEDIA (415): The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
Cause. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64060
HTTP_STATUS_RETRY_WITH (449): The request should be retried after doing the appropriate action.
Cause. The request should be retried after doing the appropriate action.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64061
HTTP_STATUS_SERVER_ERROR (500): The server encountered an unexpected condition that prevented it from fulfilling the request.
Cause. The server encountered an unexpected condition that prevented it from fulfilling the request.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64062
HTTP_STATUS_NOT_SUPPORTED (501): The server does not support the functionality required to fulfill the request.
Cause. The server does not support the functionality required to fulfill the request.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64063
HTTP_STATUS_BAD_GATEWAY (502): The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
Cause. The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64064
HTTP_STATUS_SERVICE_UNAVAIL (503): The service is temporarily overloaded.
Cause. The service is temporarily overloaded.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64065
HTTP_STATUS_GATEWAY_TIMEOUT (504): The request was timed out while waiting for a gateway.
Cause. The request was timed out while waiting for a gateway.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64066
HTTP_STATUS_VERSION_NOT_SUP (505): The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
Cause. The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
Response. This is an informational message. No action is required. For additional information on HTTP STATUS codes, see W3C at http://www.w3c.org.
64067
XSLT transformation of the data file failed: @1%s.
Cause. The XSLT transformation returns the specified error.
Response. Try running the transformation from Internet Explorer 5 or higher, and with msxml3 or higher installed. If the problem persists, contact Siebel Systems technical support for assistance.
64068
The data file is not a delimited file as declared: @1%s.
Cause. The data file is declared as a delimited file, but it is not.
Response. Review the content of the data file, make the appropriate corrections, and try the action again.
64069
A search script has not been specified for the XML_Server database type, or the Initialization String of an Initialization Block does not comply with the XML query syntax of Siebel Analytics: @1%s.
Cause. A search script has not been specified for the XML_Server database type, or the query string specified as the initialization string of an initialization block does not comply with Siebel Systems' XML query syntax.
Response. Verify that a search script has been specified if the XML_Server database type is selected. Review the syntax of the initialization strings of all initialization blocks to make sure that they conform to Siebel Systems' XML query syntax.
64070
The query string sent to the external database gateway does not comply with Siebel's XML query syntax: @1%s.
Cause. The query string does not comply with Siebel Systems' XML query syntax.
Response. Contact Siebel Systems technical support for assistance.
64071
The query has been timed out.
Cause. The query has been timed out.
Response. Set a longer time-out period for the client or the Connection Pool. This value is set in the Connection Pool XML tab URL loading time-out field.
64072
Not all rows in the delimited or fixed-width query output file contains the same number of fields.
Cause. The delimited or fixed-width query has been improperly generated. All rows should have the same number of fields, and they do not.
Response. Examine the external script used to generated the query output, correct the problem, and try the action again.
64073
An internal error in flattening the XML file creates an unsymmetrical flattening output.
Cause. A logical error was encountered in the XML flattening code.
Response. Send the source file to Siebel Systems technical support for investigation.
64074
Duplicated column names detected: @1%s.
Cause. Siebel Systems does not supported columns of the same names and level of nesting in an HTML table or XML text fragment.
Response. Rename the elements of the documents to avoid naming conflict.
64075
Third party query process execution failed with exit code: @1%s. Try to debug it from the command line using the XML query in the query log as input.
Cause. Execution of the third party process failed with the specified exit code.
Response. For additional error diagnostics, try to run the third party program from the command line using the XML query in the query log as input. If you cannot correct the problem, contact Siebel Systems technical support for assistance.
64076
Launching of third party query process failed: @1%s. Please check the correctness of the program path.
Cause. Launching the third party process failed with the specified error code. The path to the program may be incorrect or not available.
Response. Verify the path and name of the third party program specified for execution. Make the necessary changes, and try the action again.
64077
Insufficient number of columns returned for table @1%s. Please check the search script.
Cause. The union set of the input parameters and returned column values of the search script should equal to the set of columns of the physical table.
Response. Verify that the union set of input parameters and returned column values of the search script equals the set of columns of the physical table.
64078
No search script has been specified for table @1%s.
Cause. No search script has been specified for the table.
Response. Please specify a search script at the search script boxes under the XML tab of either the Connection Pool or the Physical table.
64079
No XML header file has been specified for table @1%s.
Cause. No XML header file has been specified for the table.
Response. Please specify an XML header file at the XML header file text boxes under the XML tab of either the Connection Pool or the Physical table.
64080
No XML Trailer file has been specified for table @1%s.
Cause. No XML Trailer file has been specified for the table.
Response. Please specify an XML Trailer file at the XML trailer file text boxes under the XML tab of either the Connection Pool or the Physical table.
64081
Insufficient number of predicate columns provided for the query to table @1%s. Please check the search script. Also make sure that the table is not joined to more than one other tables.
Cause. The union set of the input parameters and returned column values of the search script should equal to the set of columns of the physical table.
Response. Verify that the union set of input parameters and returned column values of the search script equals the set of columns of the physical table.
64082
Could not find or load up the search utility shared object or DLL @1%s.
Cause. The specified search utility does not exist or cannot be loaded.
Response. Verify that the specified search utility exists and is loadable.
64083
Could not find the function @1% in the search utility shared object or DLL @2%s.
Cause. The specified function does not exist in the shared object or DLL.
Response. Verify that the specified search utility exists and is loadable.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Analytics Message Reference Published: 18 April 2003 |