Sources of Errors - Intergraph Smart 3D - Troubleshooting

Intergraph Smart 3D Troubleshooting Reference

Language
English
Product
Intergraph Smart 3D
Subproduct
Troubleshooting
Search by Category
Troubleshooting
Smart 3D Version
12 (2018)

Bulkloading

Symbols can be broken in the model because of an incorrect bulk load operation. The most common bulkloading mistakes are:

  • Deleting the symbol definition, flavor manager, or flavor in the catalog when the symbol still exists in the model.

  • Setting incorrect parameter values in the catalog. For example, setting a pipe diameter to be zero.

Synchronize Model with Catalog

After bulkloading is complete or if symbol definitions have been changed and the major version number of the definition increased, you must run the Tools > Synchronize Model with Catalog command in the Project Management task for all models that use the catalog or changed definitions.

Symbols Folder

The software expects to find the symbol DLL files in a single folder, usually located under the SharedContent folder. This symbols folder is specified when the catalog database is created. Doing any of the following can cause symbol problems:

  • An incorrect symbols folder is specified when the catalog database is created.

  • The symbols folder is moved after the catalog database is created.

  • The catalog database is backed up and then restored to a different server, but the symbols folder is not copied to the new server.

  • Using different custom symbol folders for the different clients of the server.

Usage of Cached/Non-cached Symbols

The default method is to cache symbols whenever possible. A symbol definition that has a non-parametric input (for example, a part) will not be cached even if all the other inputs are parameters. However, if a custom method (CMcache) is written to convert the part into a parameter, then the symbol will be cached.

To make this change from a non-cached to cached for the case where non-cached symbols have already been placed in the model, the major version number of the symbol definition must be increased and the Tools > Synchronize Model with Catalog command in the Project Management task run. If this is not done, then the change in the way the part input is treated results in an error as the symbols already placed in the model are expecting a part, and not a parameter, and will fail to compute.

Multiple Outputs with Same Name

A .NET symbol with duplicate output names is not allowed. When such a symbol is placed in the model, the transaction will be aborted. Check the Core error log file for errors. If there are existing .NET symbol occurrences that have duplicate output names, they cannot be recomputed. For information on how to resolve the error, please refer to the Symbol has outputs with duplicate names topic in Smart 3D Database Integrity Guide.

Software Updates

Errors can occur if the server and the client software are not the same software version. All the symbols must be the same version to guarantee compatibility.

See Also

Troubleshooting Symbols