Hi, Many apologies if this has been asked before, have searched and searched and searched! I'm trying to load a soap request using MSXML2.DOMDocument.6.0 - the request looks something like this: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/ envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> <versionTag soapenv:actor="http://schemas.xmlsoap.org/soap/actor/ next" soapenv:mustUnderstand="0" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xsi:type="soapenc:string"/> <messageID soapenv:actor="http://schemas.xmlsoap.org/soap/actor/ next" soapenv:mustUnderstand="0" xmlns:soapenc="http:// schemas.xmlsoap.org/soap/encoding/" xsi:type="soapenc:string">29664</ messageID> </soapenv:Header> <soapenv:Body> <submit soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/ encoding/"> <Userid xsi:type="xsd:string">AAA1</Userid> <Password xsi:type="xsd:string">AAA1</Password> <OriginatorID xsi:type="xsd:string">0001056027</OriginatorID> <Underwriterid xsi:type="xsd:string"></Underwriterid> <OriginatorProposalReference xsi:type="xsd:string">77707000576752</ OriginatorProposalReference> <UnderwriterProposalReference xsi:type="xsd:string"></ UnderwriterProposalReference> <OperationType xsi:type="xsd:string">PROPOSAL</OperationType> <OperationData xsi:type="xsd:string"><?xml version="1.0" encoding="UTF-8"?><Proposal><Party><Individual type="Hirer"><Person dateOfBirth="1977-03-03" firstName="Pat" .......... </OperationData> </submit> </soapenv:Body> </soapenv:Envelope> (hope that formats ok!) On a test server I am loading that from a post request using msxml.loadXML() - works a treat. I'm then pulling out OperationData, validating against a schema, writing to db etc.. Working on our live server I get the following parseError (-1072897994) Type '{http://schemas.xmlsoap.org/soap/encoding/}string' is not found in Schema. Removing the versionTag and messageID nodes (leaving a blank header) loads OK on both servers, but obviously this it not ideal. I can not change the format of the data being processed and would prefer not to have to transform it. I am stumped as to the reason for this discrepancy between servers. Both have the same version of msxml2.dll (8.30.9528.0) As you can probably tell I am not vastly experienced in XML, but have been able to use it in the past to solve problems and transfer data without problems. Any light that anyone here could shed on this issue would be greatly appreciated. Many thanks. Sean Green
