We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

Exportation job failed

Hi Everyone,
When trying to export the database, I faced the following error:
Has anyone gone through a similar experience?
regards,
Paulo Moreira
--

Comments

  • Excuse me everyone,
    But the error message is this:
    Alerts & Messages
    The extract data job failed with the message:
    org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x8) was found in the element content of the document.
    More information may be available in the log files.
    Already Thankful,
    Paulo Moreira
  • drtesterdrtester Posts: 41
    Hi Paulo,
    2013/5/24 Paulo Moreira :
    > > Unicode: 0x8
    Not sure if this relates to your problem, but once we had data
    managers copying text from MS Word to the CRF Excel template. This
    lead to strange quotation marks that could be uploaded to OpenClinica
    but no export could be made because they were obviously not UTF-8. It
    had to be fixed in the database.
    Sincerly,
    Matthias
    -- Matthias Löbe, Inst. for Medical Informatics (IMISE), University of Leipzig Härtelstr. 16, D-04107 Leipzig, +49 341 97 16113, [email protected]
  • hhonshukuhhonshuku Posts: 50
    Paulo is correct.
    0x8 is a control character, namely a Backspace character. We have seen this type of incidents when user copies text from MSWord to MSExcel. We do not know exactly how MSOffice does this, but MSOffice uses a lot of unconventional binary level markups. On the OC documentation, it is emphasized to use Paste As Plain Text in order to avoid this type of issues. Once control character(s) is saved to the db, your option is to hunt it down to remove it at the db level as mentioned, unfortunately.
    -Hiro
    On Fri, May 24, 2013 at 12:01 PM, Matthias Löbe wrote:
    Hi Paulo,
    2013/5/24 Paulo Moreira :
    > Unicode: 0x8
    Not sure if this relates to your problem, but once we had data
    managers copying text from MS Word to the CRF Excel template. This
    lead to strange quotation marks that could be uploaded to OpenClinica
    but no export could be made because they were obviously not UTF-8. It
    had to be fixed in the database.
    Sincerly,
    Matthias
    --
    Matthias Löbe, Inst. for Medical Informatics (IMISE), University of Leipzig
    Härtelstr. 16, D-04107 Leipzig, +49 341 97 16113, [email protected]
  • hhonshukuhhonshuku Posts: 50
    Oops, sorry. I meant Matthias is correct.
    On Wed, May 29, 2013 at 3:21 PM, Hiroaki Honshuku wrote:
    Paulo is correct.
    0x8 is a control character, namely a Backspace character. We have seen this type of incidents when user copies text from MSWord to MSExcel. We do not know exactly how MSOffice does this, but MSOffice uses a lot of unconventional binary level markups. On the OC documentation, it is emphasized to use Paste As Plain Text in order to avoid this type of issues. Once control character(s) is saved to the db, your option is to hunt it down to remove it at the db level as mentioned, unfortunately.
    -Hiro
    On Fri, May 24, 2013 at 12:01 PM, Matthias Löbe wrote:
    Hi Paulo,
    2013/5/24 Paulo Moreira :
    > Unicode: 0x8
    Not sure if this relates to your problem, but once we had data
    managers copying text from MS Word to the CRF Excel template. This
    lead to strange quotation marks that could be uploaded to OpenClinica
    but no export could be made because they were obviously not UTF-8. It
    had to be fixed in the database.
    Sincerly,
    Matthias
    --
    Matthias Löbe, Inst. for Medical Informatics (IMISE), University of Leipzig
    Härtelstr. 16, D-04107 Leipzig, +49 341 97 16113, [email protected]
  • This problem would be only in data entry or could be generated in the construction of the CRF?
    Paulo Moreira.
    2013/5/29 Hiroaki Honshuku
    Oops, sorry. I meant Matthias is correct.
    On Wed, May 29, 2013 at 3:21 PM, Hiroaki Honshuku wrote:
    Paulo is correct.
    0x8 is a control character, namely a Backspace character. We have seen this type of incidents when user copies text from MSWord to MSExcel. We do not know exactly how MSOffice does this, but MSOffice uses a lot of unconventional binary level markups. On the OC documentation, it is emphasized to use Paste As Plain Text in order to avoid this type of issues. Once control character(s) is saved to the db, your option is to hunt it down to remove it at the db level as mentioned, unfortunately.
    -Hiro
    On Fri, May 24, 2013 at 12:01 PM, Matthias Löbe wrote:
    Hi Paulo,
    2013/5/24 Paulo Moreira :
    > Unicode: 0x8
    Not sure if this relates to your problem, but once we had data
    managers copying text from MS Word to the CRF Excel template. This
    lead to strange quotation marks that could be uploaded to OpenClinica
    but no export could be made because they were obviously not UTF-8. It
    had to be fixed in the database.
    Sincerly,
    Matthias
    --
    Matthias Löbe, Inst. for Medical Informatics (IMISE), University of Leipzig
    Härtelstr. 16, D-04107 Leipzig, +49 341 97 16113, [email protected]
This discussion has been closed.