Thursday, December 10, 2009

Q-SnTT - Quickr Qpconfig.xml Errors

Bart agrees about the qpconfig.xml

All together now, repeat after me, I will NOT edit the qpconfig.xml while sleep deprived or during the night while attending Lotusphere. I will not...

If you like the above graphic, go make one here.

Here is why:
12/09/2009 07:25:48 PM JVM: Java Virtual Machine initialized.
12/09/2009 07:25:49 PM Agent error: [Fatal Error] :69:5: The element type "user" must be terminated by the matching end-tag "</user>".
12/09/2009 07:25:52 PM org.xml.sax.SAXParseException: The element type "user" must be terminated by the matching end-tag "</user>".

What is this error in my server console telling me?

I have an agent run amok? A java agent at that.

And some org.xml.sax whatever? Come on guys, I'm an admin not a miracle java debugger.

But that /user thing rings a bell....

So here is what happened. It seems in my over zealous creative way, I had edited the qpconfig.xml and misplaced a reference. Who knew HTML was so unforgiving, or in this case XML. Raise your hands, me too, yes I know, my bad.

But in any event, here is what it looked like:
qpconfig bad

and what it should look like:
qpconfig good

Mote the juxtaposition of the /user field.

So if you get odd java/xml errors in your server console after editing your Qpconfig.xml file, guess you know where to start now don't you.


  1. I always open QPCONFIG.XML in Internet Explorer after I edit the file. If the file opens correctly then the syntax is ok. Otherwise IE will report an error.

  2. Michael,
    Excellent idea, thanks for sharing.