Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
  • Welcome
  • Products
  • Support
  • About
  • More
  • Cancel
ALIM | Exor
  • Product Communities
  • AssetWise
  • ALIM | Exor
  • More
  • Cancel
ALIM | Exor
ALIM | Exor - Wiki Invalid XML error when sending notice
    • Sign in
    • -Exor - Wiki
      • +ALIM Document Manager
      • +AWLRS
      • Exor Accidents Manager
      • +Exor Asset Manager
      • +Exor CIM / FIM
      • +Exor Document Manager
      • +Exor Enquiry Manager
      • +Exor Information Manager
      • +Exor Information Manager TMA Reporting Pack
      • +Exor Maintenance Manager
      • +Exor Maintenance Mobile
      • +Exor MapCapture
      • +Exor MapCapture (ESRI)
      • +Exor MCI MapCapture Interface
      • +Exor Network Event Manager
      • +Exor Network Manager
      • +Exor Oracle
      • Exor Problems and Solutions
      • +EXOR product placeholder
      • Exor Public Enquiry Manager API
      • +Exor Schemes Manager
      • +Exor Spatial Manager
      • +Exor Street Gazetteer Manager
      • Exor Streetworks Manager
      • Exor Streetworks Mobile
      • +Exor Structures Manager
      • Exor Structures Mobile
      • +Exor TMA API and Web Service
      • -Exor TMA Noticing Manager
        • Attachments in work reference cannot be seen
        • Change contact number in works form
        • Daily Failed Transactions Alert
        • Exor TMA unable to view street in Works
        • Failure accessing WMS theme.
        • FRM 41035 error when select notice type
        • HIG-0169: Database constraint violated: TNSW_UK
        • How to check if a notice was sent / received
        • How to configure TMA Attachments
        • How to fetch results on Review Notices form(TMA1030)
        • How to locate the .net wsdl file
        • How to remove and add recipients from S58s
        • How To Respond To A Temporary Traffic Signal Application
        • Incoming inspections fail to load
        • +Inspections - Exor TMA Noticing Manager
        • Interim Construction Method Warning Missing
        • Invalid enumeration value 0
        • Invalid XML error when sending notice
        • Major Works 3 Months Notice FPN
        • Many Inspection Records Updated
        • Missing Phase Data
        • New User Cannot Send Notices
        • No notice type for informal overrun warning
        • Notice Sent OK but Not Received
        • Notice went out of sequence in TMA3000
        • +Notices - Exor TMA Noticing Manager
        • Opening the EXOR Application Directly to TMA1000 Works Form
        • ORA 13356 adjacent points in a geometry are redundant
        • +Other - Exor Noticing Manager
        • +Other - Exor TMA Noticing Manager
        • Proximity Validation warning
        • Report not returning all records
        • +Reports - Exor Noticing Manager
        • +Reports - Exor TMA Noticing Manager
        • Restrictions - Exor Noticing Manager
        • Revoke Cancel FPN
        • Sample Inspection Quotas Report Figures Too Low
        • Scheduler only assigns to 1 inspector
        • Sender Does not Exist in NSG Error
        • Sent Transaction stuck at Pending Send status
        • Some DCD Inspections Not Downloaded
        • Start date for Major Notices
        • +Street Groups - Exor Noticing Manager
        • Street of Interest or Lane Rental Check Box
        • The XML page cannot be displayed Cannot view XML input using XSL style sheet
        • TMA Works Phase Master refresh: error in materialized view path
        • +Transactions - Exor Noticing Manager
        • +Transactions - Exor TMA Noticing Manager
        • Type 4 Street Used On Works
        • Unable to change one type of issued Direction notice type to another
        • Unable to select the Promoter/Contractor contact on Phase Details tab
        • Unable to use Links->Works function
        • What is the difference between created and modified dates
        • Works - Exor Noticing Manager
        • +Works - Exor TMA Noticing Manager
      • +Exor TMA Permitting Manager
      • +Exor UKPMS
      • ORA-20000: HIG-0230: Inconsistency detected error on login
      • +Transportation Intelligence Gateway
      • +Video Series for Exor
      • Working From Home with Exor
    • ORA-04063 'MAI' package body error

     
     Questions about this article, topic, or product? Click here. 

    Invalid XML error when sending notice

       
      Applies To 
       
      Product(s): Exor TMA Manager
      Version(s): N/A
      Environment:  N/A
      Area:  N/A
      Subarea:  N/A
      Original Author: Bentley Technical Support Group
       

     

    Problem

    When user tries to send a notice the following error is seen:

    TMA-0093 Unable to send the notice: Error in XML
    (tma_types.get_schema_notice_root) PL/SQL: Numeric or value error: Null index table key value

    or

    TMA-0093 Unable to send the notice: Error in XML
    (tma_transactions_api.validate_xml) invalid XML document

    Solution

    This error is seen when the application tries to create some XML for a notice but it isn’t compliant with the EToN Technical Specification. This error can be seen for several reasons, including:

    1. If the data which is being inserted into the XML contains invalid characters. All characters must be in the UTF8 specification. If text is copied from other software programs into a form then it can often contain hidden control characters, particularly from MS Word or Outlook. When you have to copy text, paste it into a basic text editor such as notepad, remove any strange characters and then copy it again.  If you’re unsure then try retyping all text in each field again manually.
    2. If an invalid postcode is declared. You must use a valid postcode that publicly recognised and complies with BS7666.
    3. Check the works description to make sure there are no invalid characters or spaces.  Sometimes if copied from word additional spaces can be at the end of the text.  So highlight all the text and make sure it has not highlighted blank spaces as well.  If it has removed these spaces/carriage returns from the works description.
    4. Check the Contractor/Promoter Contacts.  Are these valid.  Is there any Spaces in any of the fields.  Try reselecting the Contact details from the drop down again.
    5. If the sender or recipient organisation doesn’t have an EToN Version set in the NSG0110 Organisations  and Districts form. An EToN Version needs to be set for every organisation you send notices to so that the XML created is valid.

    If the above does not resolve this, another thing to check is whether the user is trying to send a 0500 notice on a Permit at status Works In Progress. If the end date needs changing then the user should send a 0510 notice.    

    See Also

    Product TechNotes and FAQs

    External Links

    Bentley Technical Support KnowledgeBase

    Bentley LEARN Server

    Comments or Corrections?

    Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

     

    • Exor Noticing Manager
    • TMA Manager
    • 87712
    • Notices
    • Share
    • History
    • More
    • Cancel
    • Elisabeth Pry Created by Bentley Colleague Elisabeth Pry
    • When: Mon, Oct 7 2013 12:09 PM
    • Jodie Preston Last revision by Bentley Colleague Jodie Preston
    • When: Thu, Jun 11 2015 12:14 PM
    • Revisions: 10
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2021 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies