java.io.UTFDataFormatException

I've tried validating an xml file against a schema two different ways and I get the following error. I found something on the web stating that there could be some data problem regarging special characters. Not sure what though.

java.io.UTFDataFormatException: Invalid byte 2 of 2-byte UTF-8 sequence.

at org.apache.xerces.impl.io.UTF8Reader.invalidByte(Unknown Source)

at org.apache.xerces.impl.io.UTF8Reader.read(Unknown Source)

at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)

at org.apache.xerces.impl.XMLEntityScanner.peekChar(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)

at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)

at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)

at validator.Main.main(Main.java:23)

Here is some of the xml file being parsed. Notice anything early on that could cause a problem?

<?xml version="1.0" standalone="no"?>

<!-- DOCTYPE OLifE PUBLIC"-//ACORD/DTD XMLife//EN""file:///D:/XMLife/dtds/XMLife2.7.01.dtd" -->

<OLifE>

<SourceInfo>

<SourceInfoName>REPNET</SourceInfoName>

</SourceInfo>

<CurrentLanguage tc="9">English</CurrentLanguage>

<Holding id="Holding_8604">

<HoldingTypeCode tc="2">Policy</HoldingTypeCode>

<HoldingName>Life Insurance</HoldingName>

<HoldingStatus tc="3">Proposed</HoldingStatus>

<HoldingForm tc="1">Individual</HoldingForm>

<Policy>

<PolNumber>20071105</PolNumber>

<LineOfBusiness tc="1">Life</LineOfBusiness>

<ProductType tc="3">Universal Life</ProductType>

.

.

.

[2634 byte] By [black_lotusa] at [2007-10-2 8:53:27]
# 1
Right at the beginning I notice that the document doesn't declare an encoding. So the parser will assume it was encoded in UTF-8. But if whatever produced it didn't use UTF-8 but some other encoding, then non-ASCII characters can cause that exception.
DrClapa at 2007-7-16 22:57:16 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2
Seems to work a little better when i specify an encoding - I still get other others, but this is progress. However if I specify the encoding I get syntax errors when opening the xml file in IE or validating it in an online W3Schools validator.
black_lotusa at 2007-7-16 22:57:16 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 3
Sorry, my mistake. I had ... standalone="no" encoding="UTF-8"?>and not... encoding="UTF-8" standalone="no"?>
black_lotusa at 2007-7-16 22:57:16 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...