Plex 2E

  • 1.  XML IMPORT ERROR

    Posted Nov 29, 2017 01:58 AM

    Hello,

     

    When importing a large .xml file we receive the following error in the Plex Message Log:

     

    'RegisterCall' while importing function [FunctionName]. Line 2071, File .\Src\ADFUNC\IMPORTAD.

     

    In addition, import failed and Entity could not be imported at all. There are many functions that were not imported.
    (It may not be the only reason for this error to fail import, because other errors were also output.)

     

    We tried it with Plex r7.1 Build 26.005. When we check the r7.1 Fix Note(Problem/Issue Number : 1838), we thought that this problem was solved, but have not it solved it?


    We did the following procedure:
    1. Exported a local model of about 460M and created an .xml file(about 900M).
    * Tools - Export - XML Model

     

    2. Added the same model configuration as when exporting to the new group mode.

     

    3. Created a new local model and extracted the objects of the upper library from the group model created in Step 2.

     

    4. Imported the .xml file created in Step 2 into the local model created in Step 3.
    * Tools - Import - XML Model Import


    The reason why we are doing this work is that high surrogate checks are done on our customer group model and high surrogate check errors are output each time they update their group model.
    Available surrogates will be short in the near future as it is.

    We thought that this problem occurred due to surrogate jumps and asked them to try "Assign alternative group model surrogate".


    We created "renum.num" file by writing "1" in the enablerenum.dat file.
    For a while we could use the renum.num file, but perhaps because it corresponded to all the gaps in the group model, the renum.num file can not be used.

     

    When the renum.num file is no longer used, a high surrogate check is output again.

    They are doing their daily work while worried that the surrogate fills up and the group model can not be updated.

    We thought that the problem might be solved by re-numbering the surrogate, tried to re-number surrogate by exporting and importing the local model.
    However, .xml import can not be done correctly. There is no error when exporting.

     

    Do you know who is importing large .xml file correctly?

     

    Regards,
    Hifumi



  • 2.  Re: XML IMPORT ERROR

    Posted Nov 30, 2017 07:23 PM

    Contact me at darryl.millington@hawkbridge.com.au - I might be able to assist you in your problem - I have been doing large Plex XML file imports for more than a decade for various clients.



  • 3.  Re: XML IMPORT ERROR

    Posted Dec 03, 2017 11:27 PM

    Dear Darryl,

     

    Thank you for your kind offer.
    Unfortunately, my boss isn't agreeing with the case, therefore I have to decline this time.

     

    Regards,
    Hifumi