Publish iModel Crashes/Stalls

Dear Forum,


Using MS Connect 10.10.00.23 to publish iModel[s] and the process hangs and/or crashes. the total amount of files its trying to publish totals around 930mbs in 20 references. Anyone see this as being a problem?

Any hints to get around it i can try?


Andi

Parents
  • Hi all.
    This thread is really interesting for me.

    We are facing really serious problems with our iCS for i-Models.
    We have been struggling with this for two weeks now, and nothing is stable.

    Has anyone been able to run pas100003125en stable.

    We tried many version of MicroStation, but non work. Resetting the iCS database and much more.

    Very often get 'Not responding' > MicroStation and the Queue has crashed.

    or very long processing, that eats up all memory (32GB)

  • I downloaded the Microstation Update 11 last week as soon as Connect Advisor said that it was available.  The new update generated the i.dgn file in a couple minutes without issue.  When I selected to generate the .imodel file as well, the software hung.  I killed the process and was able to successfully open the .imodel file in Navigator.

  • Is any log file created in the same folder as source and/or output files?

    Yes there is a log file.  Contents below:

    "Warning,MissingData,Could not locate external v8 ECSchema BuildingDataGroup. Instances of classes from this schema will not be converted.,
    Warning,MissingData,Could not locate external v8 ECSchema OpenPlant_3D. Instances of classes from this schema will not be converted.,
    Warning,Sync,"ECSchema S already found in the V8 file with a different checksum (4124767832). Copy in model <5600, Default (0)> with checksum 300962576 will be merged. This may result in inconsistencies between the DgnDb version and the versions in the Dgn.",
    Warning,Sync,"ECSchema S already found in the V8 file with a different checksum (4124767832). Copy in model <5600, Default (0)> with checksum 2474878628 will be merged. This may result in inconsistencies between the DgnDb version and the versions in the Dgn.",
    Warning,Sync,"ECSchema S already found in the V8 file with a different checksum (4124767832). Copy in model <5600, Default (0)> with checksum 1612668746 will be merged. This may result in inconsistencies between the DgnDb version and the versions in the Dgn.",
    Warning,Sync,BISIfication required changing relationship strength of ECRelationshipClass 'ProStructures:AssembliesToObjects' from 'Holding' to 'Referencing'.,
    Warning,Sync,BISIfication required changing relationship strength of ECRelationshipClass 'ProStructures:GroupsToObjects' from 'Holding' to 'Referencing'.,
    Warning,Sync,BISIfication required changing relationship strength of ECRelationshipClass 'ProStructures:RebarBeamToRebar' from 'Holding' to 'Referencing'.,
    Warning,Sync,BISIfication required changing relationship strength of ECRelationshipClass 'ProStructures:SubGroupsToObjects' from 'Holding' to 'Referencing'.,
    Warning,MissingData,Could not embed font type/name 1/'MS Shell Dlg 2'; a different font will used for display.,"

  • It sounds like the last step in the conversion process (transform .i.dgn into .imodel) was not finished correctly.

    Yes, this is where is hangs with the progress bar at like 95% completion. 

  • Hi,

    thanks for providing details! :-)

    The log shows the original data was created in products like ProStructure, AECOsim Building Designer and maybe also in OpenPlant, so when published from MicroStation, some EC schemas are missing. There is also a problem with schema(s) inconsistency. But all reported issues are warnings, not errors, so they should not lead to the conversion hang. In fact some from these issues are reported even for standar MicroStation examples.

    My assumption is that some from design files is corrupted or it contains data that cannot be converted.

    Maybe (but it sounds like a bit time consuming task) you can try to publish individual files one by one to test, whether all will be converted or some not.

    With regards,

      Jan

  • Yes, the issue here is that all discipline files have been merged into one.  For example, we have structural files that may have been created over the years in Bentley Structural, Prosteel, AECOSIM, or even within some AutoCAD applications (rare for structural).  If we are talking about equipment models, then some have been created in Plantspace & most vendor models are created using some sort of Autodesk software of various versions.

  • Hi,

    Yes, the issue here is that all discipline files have been merged into one.

    It's recommended to export i-models from original application when possible, because MicroStation is not able to handle all application-specific data and as mentioned in log you shared, in such case the data are not converted into i-model. When a requirement is to maintain geometry and business data (non-graphical attributes) are not so important, the export from MicroStation is good enough.

    You can also try to start conversion from i-model to DgnDb format manually from command line and also to enable detail logging, which potentially can help to find out where the problem is.

    To start the conversion manually:

    1. Export your file into i-model as a single package, but do not use an option create also iModel version. It means only .i.dgn file will be created.
    2. Open Windows shell (DOS window).
    3. Navigate to a folder where .i.dgn exists.

    The command to start the conversion is:

    "C:\Program Files\Bentley\ItgDgnDbImporter 1.5\IDgnToIDgnDb.exe" -i <input i-model> --output <uncompressed DgnDb> -z <compressed DgnDb> --imodelVersion 2.0

    e.g.

    "C:\Program Files\Bentley\ItgDgnDbImporter 1.5\IDgnToIDgnDb.exe" -i my_exported_file.i.dgn --output big_imodel -z compressed_imodel --imodelVersion 2.0

    The conversion will be started as separate process and basic information about the progress is displayed. When there is any problem, .log file is created in the same folder.

    To use detail logging requires some more steps and it makes sense to me to ask somebody from Bentley to try the conversion and to analyse why the conversion hangs.

    With regards,

      Jan

Reply
  • Hi,

    Yes, the issue here is that all discipline files have been merged into one.

    It's recommended to export i-models from original application when possible, because MicroStation is not able to handle all application-specific data and as mentioned in log you shared, in such case the data are not converted into i-model. When a requirement is to maintain geometry and business data (non-graphical attributes) are not so important, the export from MicroStation is good enough.

    You can also try to start conversion from i-model to DgnDb format manually from command line and also to enable detail logging, which potentially can help to find out where the problem is.

    To start the conversion manually:

    1. Export your file into i-model as a single package, but do not use an option create also iModel version. It means only .i.dgn file will be created.
    2. Open Windows shell (DOS window).
    3. Navigate to a folder where .i.dgn exists.

    The command to start the conversion is:

    "C:\Program Files\Bentley\ItgDgnDbImporter 1.5\IDgnToIDgnDb.exe" -i <input i-model> --output <uncompressed DgnDb> -z <compressed DgnDb> --imodelVersion 2.0

    e.g.

    "C:\Program Files\Bentley\ItgDgnDbImporter 1.5\IDgnToIDgnDb.exe" -i my_exported_file.i.dgn --output big_imodel -z compressed_imodel --imodelVersion 2.0

    The conversion will be started as separate process and basic information about the progress is displayed. When there is any problem, .log file is created in the same folder.

    To use detail logging requires some more steps and it makes sense to me to ask somebody from Bentley to try the conversion and to analyse why the conversion hangs.

    With regards,

      Jan

Children
No Data