I have an XMA that for the Import run consumes an XML file that has DSML in it. The import run fails with the sync-engine status of "stopped-parsing-errors". Looking in the event log, I see this: The management agent "xxx" failed on run profile "FISO" because parsing errors were detected at the following location: Line Number: 55 ColumnNumber: 5 Looking in the three-element XML file, I see that this position is the second from last closing element. This makes no sense as the DSML is valid as far as I can see. Line 55 is: </searchResponse> </batchResponse> At first we thought it was an encoding issue, so we manually changed the encoding of the xml file in notepad to all the options it had, i.e. ansi, utf-8, unicode, endian, etc.. But the result was the same. Any ideas what this could be? The total Xml document is: <?xml version="1.0"?> <batchResponse xmlns="urn:oasis:names:tc:DSML:2:0:core" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <searchResponse> <searchResultEntry dn="CN=1000000660"> <attr name="changetype"> <value>add</value> </attr> <attr name="objectclass"> <value>MPSpecialism</value> </attr> <attr name="updatedDate"> <value>17/08/2010</value> </attr> <attr name="guid"> <value>1000000660</value> </attr> <attr name="MPDisciplineguid"> <value>CN=1000000659</value> </attr> </searchResultEntry> <searchResultEntry dn="CN=1000000654"> <attr name="changetype"> <value>add</value> </attr> <attr name="objectclass"> <value>MPSubRegion</value> </attr> <attr name="updatedDate"> <value>17/08/2010</value> </attr> <attr name="guid"> <value>1000000654</value> </attr> <attr name="MPRegionguid"> <value>CN=1000000653</value> </attr> </searchResultEntry> <searchResultEntry dn="CN=1000000659"> <attr name="changetype"> <value>add</value> </attr> <attr name="objectclass"> <value>MPDiscipline</value> </attr> <attr name="updatedDate"> <value>17/08/2010</value> </attr> <attr name="guid"> <value>1000000659</value> </attr> <attr name="MPBrandguid"> <value>CN=1000000658</value> </attr> </searchResultEntry> </searchResponse> </batchResponse>

Try adding a search results done before the </searchResponse> closing element. <searchResultDone> <resultCode code="0" descr="success" /> </searchResultDone> MarkMark Creekmore - Blue Chip Consulting Group