TCC – A SAX parsing error occurred

One of the most general errors you will encounter in TCC is the dreaded SAX parsing error.  It happens often and gives you no clue as to what went wrong.

SAXerror

The way to get it to give you the details of the error is to go into the post processing tab of the config file and uncheck the ‘Fail on export error’ checkbox.  While this won’t fix the error it will now return the error (more specifically the field that’s causing the error) in the response file.

UncheckFailOnError

One comment

  • Greig Saunders
    May 30, 2014 - 4:23 am | Permalink

    Hi Aron,

    I have also found that this error occurs when the user logged into TCC does not have sufficient permissions to access Modules/Entities. Using SmartOrg (from the online portal), and assigning the correct permissions to a report developer user will allow the TCC to extract the data without the SAX error.

    Oracle support suggests that the SAX error is corrected by ensuring that the output type is “CSV-Report”, but I still continued to experience the error until I realised it was a permissions issue based on the modules I could see online. Hope this helps someone experiencing the same issue…

  • Comments are closed.