Action: Check and correct it. GalvinProject ManagerAkaza Research781-547-8425www.openclinica.org ~ OpenClinica Enterprise ~ Ask me about professional training, support, and services for OpenClinica***To search the archives of the User and Developer Forums, please go to http://www.openclinica.org/page.php?pid=107***Sent: Saturday, [email protected]: The object or objects are not found in the container TMP000.person.DATA. Action: See whether all axis names in the XSL file are correct. Check This Out
LPX-00277 no closing quote was seen Cause: A quoted string was started but not finished. LPX-00283 document encoding is string-based but default input encoding is not Cause: The input document was detected to be ASCII (or EBCDIC) based, but no encoding was specified in the XMLDecl LPX-00240 element-start tag is not well formed Cause: A start-element tag was improperly formed. Tech Support really is your best bet here.
The datasets uploaded fine into SAS using the PROC CDISC statement when there was only one event loaded into the study. Action: Value must contain one or more tokens, separated by spaces. Action: Check whether the variable references are valid. I get the SAS log error of: ERROR: Unexpected or unmatched end of element tag When I look at the XML file I noticed that the file looks normal for quite
Action: This is a programming error by the caller of the XML parser. XML is case sensitive, so only "version" (not "Version", and so on) is valid. Thanks,Paul -----------------------------------------------------------------------Paul J. For example:
The w3c site has this information, but the Wikipedia article states the rules more succinctly: http://en.wikipedia.org/wiki/XML#Well-formedness_and_error-handling [quote] Well-formedness and error-handling The XML specification defines an XML document as a text which Options are CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS. LPX-00275 can't set output/data encoding AFTER parsing Cause: Output/data encoding must be set after initialization but BEFORE any parsing has taken place. The SAS XML Libname Engine does not support processing of Data Type Definitions (DTD).
Action: Make sure that the attributes are unique. Action: Make sure that apply-imports are invoked only if there is a current template and it is not in a xsl:for-each. I don't actually know whether the SAS XML Libname Engine (SXLE) uses _ERROR_ or not. LPX-00279 invalid no_proxy "string" Cause: The no_proxy specification was invalid.
LPX-00411 unknown function name encountered Cause: The function is not supported at this time or the name is invalid. click If no port part is present, then it applies to all ports on that domain. I dumped dictionary.macros to print to see if any variable indicated the error. Action: Correct the document.
Action: Check for unmatched quotes in the XSL file. Action: Correct the document. They must all be provided, even if they are stub functions which do nothing. Thanks, Paul ----------------------------------------------------------------------- Paul J.
Now that more events have been loaded into the study this occurs, even if I am only selecting information from one event when I create a dataset it still has this SAS meets the information needs of new and experienced users with a variety of delivery methods including PDF, HTML, and electronic and hard copy books. Action: Always provide a version#, which must come first in the declaration. You cannot use both a shared DTD and and internal/external one.
Action: Language specification has the format
LPX-00101 parameter-entity markup cannot be split up Cause: Validity Constraint 2.8 failed: "Parameter-entity replacement text must be properly nested with markup declarations."
Proper format is ''. Action: UCS2 data consists of an array of shorts which must be aligned on an even-byte boundary. Reading the files twice is not a favored solution. This did not occur when I extracted for only one event.
Action: Contact the appropriate developer. Error processing resource 'file:///C:/Documents and Setti... This did not occur when I extracted for only one event. LPX-00273 failed to initialize TCP/IP Cause: The TCP/IP package could not be initialized. Action: Verify conditional nesting in document and correct.
I think that you are asking for some kind of processing capability with SXLE that it was not designed to do. LPX-00321 None of the output methods (DOM, SAX, Stream) are selected Cause: User is trying to process an XML file with out selecting any mechanism for output. LPX-00252 invalid entity replacement-text nesting Cause: Markup included from an entity must nest/group properly. Action: Check the input string to make sure the expected token is present.
Message was edited by: JMarkW Message 5 of 9 (172 Views) Reply 0 Likes Cynthia_sas SAS Super FREQ Posts: 8,229 Re: What error codes are available when using the libname XML