unexpected character while parsing XML from batch script

Question

I am getting this error when I am trying to parse XML from batch Script

 error : 
 < was unexpected at this time.

xml:

<driver type=".dbdriver">
        <attributes>localhost;1521;XE;false</attributes>
        <driverType>Oracle thin</driverType>
      </driver>
      <password>7ECE6B7E7D2AF514C55BAE8B3A6B51E7</password>
      <user>JR</user>

batch scrpit:

for /f "tokens=3 delims=><" %%j in ('type %SETTINGSPATH% ^| find "<user>"') do set user=%%j

This code is supposed to read user value from XML which is just "JR" and on some machines I am getting this values; but some machines are not showing this value and showing this error.

Please guide.

dbenham · Accepted Answer · 2012-10-18 17:05:02Z

2

Parsing XML with batch is often problematic and always risky. A valid XML documented could be legitamately reformatted in any number of ways that would break you parser. But if you really want to continue to use batch...

That error message occurs when you have an unescaped and unquoted < character in your IN() clause. The "<user>" is already quoted, so that normally should not be a problem. The problem must stem from the value contained in %SETTINGSPATH%. Either the value must have an unquoted and unescaped <, or there must be an odd number of quotes in the value. The odd number of quotes would cause the <user> to no longer be quoted.

The only other possibility is that you have not shown us all your code, and the error is occuring someplace else.

edited Oct 18, 2012 at 17:05

answered Oct 18, 2012 at 16:04

dbenham

132k29 gold badges273 silver badges410 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Pawel · Accepted Answer · 2012-10-18 16:36:00Z

0

This will never work reliably. The reason for this is that you are trying to process Xml using wrong tools. There is an infinite number of textual representations of an Xml document that have the same semantical meaning. As a result a space here or a new line there will not change the semantics of your document but will break your script even though all the tools that process the input as Xml will continue to work correctly. Use PowerShell or vbscript/jscript where you can use Xml capabilities or you will always have problems like this since you should not use a brush to drive screws.

edited Oct 18, 2012 at 16:36

answered Oct 18, 2012 at 15:25

Pawel

31.7k4 gold badges76 silver badges106 bronze badges

3 Comments

Andriy M Over a year ago

‘This will never work reliably’ – While the OP's experience does seem to confirm your statement, it would be much better if you elaborated on why this is unreliable.

dbenham Over a year ago

I agree that batch should not be used to parse XML. But I don't see how the XML could cause the reported error.

Pawel Over a year ago

@AndriyM - added more explanation.

Collectives™ on Stack Overflow

unexpected character while parsing XML from batch script

2 Answers 2

Comments

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related