12.07.2015 Views

General Error Messages - InterSystems Documentation

General Error Messages - InterSystems Documentation

General Error Messages - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>General</strong> <strong>Error</strong> <strong>Messages</strong><strong>Error</strong> Code63096310631163126313635063516352635363546355635663576358635963606361636263636364636563666367636863696370637163726373637463756376DescriptionClass '%1' is in deployed mode and so can not be export, skipping this item.URL '%1' is malformed and cannot be processedSchema definition for namespace '%1' does not exist.Unable to find default namespace for class '%1'.Schema moniker type '%2' (from schema '%1') is invalid.SoapMessageName keyword may only be specified for a web service method: %1.SoapAction keyword may only be specified for a web service method: %1.Invalid value for HttpRequester: %1.Unexpected attributes for element %1: %2If a property is not of type string and has XMLPROJECTION = content, then all otherproperties must have XMLPROJECTION = attribute.SOAP message has no body.Invalid node type: %1.Parent node may not be set directly.<strong>Error</strong> scanning tree: element expected.Binary SOAP protocol may not be used with %SOAP.WebRequest.Unexpected class, %1, received for binary SOAP protocol. %2 expected.Class must be XML enabled.Duplicate definition of XML schema %1 %2 for class %3.Inconsistent use of encoded format for XML namespace %1.Inconsistent definition of ElementQualified for classes in namespace %1.Invalid format of SOAP binary %1.Unexpected top logical block: %1.Unexpected SOAP binary version number: %1.Duplicate definition of class, %1, in SOAP binary message.Object instance refers to unknown classwith index %1 in SOAP binary message.Duplicate specification of SOAPCLASSNAME for class %1.ServiceName must be specified in SOAPCLASSNAME for class %1.Multipart MIME SOAP message received with unexpected Content-Type header field: %1.Only SOAP with Attachments and MTOM are supported.The SOAPVERSION parameter specifies an unsupported SOAP version: %1.SOAP version %1 is not supported for this web client.SOAP encodingStyle %1 is not supported.Mandatory Header NOT supportedCaché <strong>Error</strong> Reference 61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!