_BB_SHOW_DATASET_LOAD_MSGS

RE: _BB_SHOW_DATASET_LOAD_MSGS

Marc Thomas — Tue, 11 May 2021 11:38:17 GMT

Hmm, it's not clear from the text file which errors are being referred to, we'll need a screenshot of the errors in the message center.

Also I see "Failed to update ProjectWise project information according to the current document - current project may be incorrect.
Could not retrieve information from the CONNECTION client." You should talk to your ProjectWise admins about that.

RE: _BB_SHOW_DATASET_LOAD_MSGS

Alla Remizova — Tue, 11 May 2021 00:35:46 GMT

Thank you Marc. I solved these 3 problems above but still have an error message in Message center : Architecture Configuration Check found error(s), please review the previous 3 message(s) for details. It's very confusing, hard to understand what 3 messages should be checked. Text file attached

communities.bentley.com/.../Error-message.txt

RE: _BB_SHOW_DATASET_LOAD_MSGS

Marc Thomas — Mon, 10 May 2021 09:33:34 GMT

Regarding these three messages, from the top down:

Two SHX fonts, iso3098b and ARCHITXT, used (presumably) by a DWG somewhere in the reference files are not available. If the SHX file(s) containing these can be identified and added to a location defined by MS_FONTPATH. The default value for this is C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\Default\fonts\, however adding SHX files in that location is obviously not efficient.

The best resolution would be for the people/organizations in the supply chain who still use SHX fonts to switch to commonly available Windows TrueType fonts, but this is not going to resolve your immediate problem. I suggest that your ProjectWise administrators do the following:

add a Fonts folder in an appropriate shared location
Append the path to this location to MS_FONTPATH in the managed configuration
obtain the missing fonts and put them in this folder

For info, hel says "If AutoCAD is installed, MicroStation searches for SHX fonts in AutoCAD’s Fonts directory (the "Fonts" folder in the installation directory of the most recently used version of AutoCAD). With or without AutoCAD, MicroStation searches the directories specified by MS_FONTPATH, as well as the same directory as the design file requesting the font."

The other error is that a material palette file, hatch232.pal, is not found. If this palette can be located and copied into a location defined by MS_MATERIAL it should be seen during iModel publishing. Any images used by the materials in this palette will need to be in locations defined by MS_PATTERN and MS_BUMP variables. It could be worth checking what hatch232.pal contains and if the materials are actually needed, they might be duplicates of standard materials.

RE: _BB_SHOW_DATASET_LOAD_MSGS

Alla Remizova — Fri, 07 May 2021 17:41:32 GMT

Thank you Marc. I attached text file here. There is an error message which creates a problem: Architecture Configuration Check found error(s), please review the previous 3 message(s) for details.

communities.bentley.com/.../Message-Center.txt

RE: _BB_SHOW_DATASET_LOAD_MSGS

Marc Thomas — Fri, 07 May 2021 17:02:38 GMT

Hi, next time you open the file please can you follow the steps in The Message Center - Some Tips to create a text file listing all of your messages then post that file to this thread. Many of the messages contain guidance that can help to resolve the messages.

RE: _BB_SHOW_DATASET_LOAD_MSGS

Alla Remizova — Fri, 07 May 2021 13:41:03 GMT

Hello, we have similar error message in OBD Message Center: Architecture Configuration Check found error(s).

It affects automation iModeling process, the same error shows up in BAS which stop iModeling publishing. Please help us to solve this problem. Thank you.

RE: _BB_SHOW_DATASET_LOAD_MSGS

Marc Thomas — Tue, 23 Mar 2021 11:53:21 GMT

Filed Defect 1125448: "_BB_SHOW_DATASET_LOAD_MSGS Message Center text should include syntax for use"

RE: _BB_SHOW_DATASET_LOAD_MSGS

Marc Thomas — Tue, 23 Mar 2021 11:37:45 GMT

Hi Rik,

You are correct, we should explain that in this message and document in help.

setting it to 1 is the correct syntax. That is generally the case for on/off variables but we still need to be explicit about each case.