PO20 Invalid XML: Root node does not exist

 4 Replies
 0 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Melissa LeCompte
New Member
Posts: 3
New Member

    We have a user that is getting an "Invalid XML: Root node does not exist" error message when attempting to view "Comments to Print on Headers on Internal Documents" in PO20. 

    We've deleted his Lawson access and rebuilt him as a new user, checked the XML file permissions and owner, checked his CPU memory and java, and put him in a different security class in LAUA. So far everything we've tried hasn't worked.

    Here is the message:

    /cgi-Lawson/getattachrec.exe?

    _OUT=XML&K1=1864&K2=222I&_AUDT=I&K3=535153&K4=0&_TYP=CMT&_ON=Comments+to+Print+on+Headers+on+Internal+Documents&_ATTR=TRUE&_ATYPE=C&_DRIL=TRUE&_IN=PCRSET1&_AOBJ=TRUE&_FN=PURCHORDER&_PDL=PROD&_OPM=C&_ECODE=FALSE

    SSORequest() - sso.js

    Any suggestions on what we can try to resolve this issue.

    JonA
    Veteran Member
    Posts: 1163
    Veteran Member
      I'm not familiar with the error message but have you ruled out the comment itself as the issue? We've had problems in the past where someone copied
      an email with invalid characters and pasted it to comments. It didn't give us that particular error but when I see errors related to viewing comments I like
      rule out the comments. Is he the only one getting this error? Is the error specific to a particular comment or any comment on any screen (PO20, RQ10,
      PO30, etc.)?

      Also, I found this post from 2009 where someone was getting the same error while attempting to create a custom HR11 screen.

      https://www.lawsonguru.co...ft/5907/Default.aspx
      Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
      Melissa LeCompte
      New Member
      Posts: 3
      New Member

        As far as we know he is the only user having an issue with the comments in PO20.

        I saw the HR11 post from 2009. We tried those steps as well and didn't get any further in resolving the issue.

        We've logged into LID as the user and did not get the error message however, when we login to Lawson portal as the user we get the same error message.

        JonA
        Veteran Member
        Posts: 1163
        Veteran Member
          So it's not PC related if you can duplicate his error on onother PC logged in as him. And if he's the only one that gets the error everything seems
          to be pointing to his set up. Does he get the error on any of the other comment types or just comments to print on internal documents?
          Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
          Melissa LeCompte
          New Member
          Posts: 3
          New Member
            He's getting the error on all comment types