Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    p_cir_23: "xmlParseStartTag: invalid element name"[etc.]

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    I am running Aleph 18 - latest service pack installed.

    I am looking to remove "old" patrons that have left the University, and have no remaining unresolved transactions.
    ( ie no debts, no books outstanding, no Hold requests)

    From the GUI Services menu, I ran Services > Patrons > Delete Patron Records (cir-23).

    I took default settings, except I put the 'Expiration Date Until 1/1/2007 .
    Update Database = 'NO'

    I find in my pc_server_6350.log multiple error messages:

    The message begin : ......../a18_1/aleph/pc_b_eng/p-cir-23.xml:###: error: :

    followed by one of these:

    xmlParseStartTag: invalid element name [ FIRST error message in sequence ]
    xmlParseStartTag: invalid element name
    Opening and ending tag mismatch: hidden and checkbox
    Opening and ending tag mismatch: hidden and control
    Opening and ending tag mismatch: checkbox and dialog
    Premature end of data in tag <control>
    Premature end of data in tag ). F20 -->
    xmlParseStartTag: invalid element name
    xmlParseStartTag: invalid element name
    Opening and ending tag mismatch: hidden and checkbox
    Opening and ending tag mismatch: hidden and control
    Opening and ending tag mismatch: checkbox and dialog
    Premature end of data in tag <control>
    Premature end of data in tag ).

    [Later:]
    It seems like this occurred around the time that I tried to look at a large file in Task Manager. Size = 118019940

    When I hit the 'Print' button in Task Manager, the window ended crashing. However, when I look at a more
    moderate sized file, everything works as expected. Again I was able to 'crash' the task manager in this manor,
    yet I do not find the same error messages.

    Perhaps this is the cause?

    Resolution:
    If you are now able to run p_cir_23 without getting these error messages, we will assume that the problem was do to some other factor. Let us know if the problem recurs.
    This issue is still open and was escalated to Development for further investigation <2008-11-09 01:00:00>.

    • Article last edited: 10/8/2013