Troubleshooting Guide

(1)

SmartPlant 3D

(2)

Copyright

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization.

Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is “restricted computer software” submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations (“FAR”) and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense (“DoD”): This is “commercial computer software” as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

Unpublished – rights reserved under the copyright laws of the United States. Intergraph Corporation

Huntsville, Alabama 35894-0001

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its

publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks

Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, IntelliShip, INtools, ISOGEN, PDS, and MARIAN are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. ACIS is a registered trademark of SPATIAL TECHNOLOGY, INC. Infragistics,

Presentation Layer Framework, ActiveTreeView Ctrl, ProtoViewCtl, ActiveThreed Ctrl, ActiveListBar Ctrl, ActiveSplitter, ActiveToolbars Ctrl, ActiveToolbars Plus Ctrl, and ProtoView are trademarks of Infragistics, Inc. Portions of 2D DCM, 3D DCM, and HLM from D-Cubed Limited are incorporated. All rights reserved. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other brands and product names are trademarks of their respective owners.

(3)

To Do List: O...91 To Do List: P ...93 To Do List: Q...96 To Do List: R ...97 To Do List: S ...99 To Do List: T ...110 To Do List: U...117 To Do List: V...119 To Do List: W ...123 To Do List: X...124 To Do List: Y...124 To Do List: Z ...124 Error Messages...125 Error Messages: A ...126 Error Messages: B...129 Error Messages: C...130 Error Messages: D ...133

Error Messages: E...134

Error Messages: F ...135

Error Messages: G ...135

Error Messages: H ...136

Error Messages: I...137

Error Messages: J...137 Error Messages: K ...137 Error Messages: L...138 Error Messages: M...139 Error Messages: N ...140 Error Messages: O ...142 Error Messages: P ...143 Error Messages: Q ...143 Error Messages: R...144 Error Messages: S ...144 Error Messages: T...146 Error Messages: U ...154 Error Messages: V ...157 Error Messages: W ...157 Error Messages: X ...157 Error Messages: Y ...158 Error Messages: Z...160 Index...161

(5)

Preface

This document is a troubleshooting guide for SmartPlant® 3D. The purpose of this document is to describe how to resolve errors that you may encounter in the software.

Document Audience

This document is intended for advanced users who are familiar with SmartPlant 3D database architecture and relational databases in general.

Related Documents

For more information about SmartPlant 3D, please see the following documents:

• SmartPlant 3D Installation Guide

• SmartPlant 3D Reference Data Guide

Documentation Comments

(6)

What's New with Troubleshooting

Version 2007

• You can filter the To Do List messages that appear in the To Do List dialog box to only those messages that apply to selected objects. Select the

Filter To Do List By Select Set command on the To Do List dialog box

to display only those To Do List messages that apply to selected objects. Select Clear Filter to display all the To Do List messages again.

• Added Structure To Do List messages.

• Added Space Management To Do List messages.

• Added Equipment To Do List messages.

• Added Common error messages.

• Added Piping To Do List messages.

• Added HVAC To Do List messages.

• Added Electrical To Do List messages.

• Added Hangers and Reports To Do List messages.

• Added information about the Remove Design Basis custom command. For more information, see Integration, page 14.

• Added information about the cable auto-routing log file to the Electrical troubleshooting tips section.

(7)

Troubleshooting: An Overview

Troubleshooting is the act of working to correct errors that you encounter while working in the software. The following situations are examples of troubleshooting.

• You are working in the model, and an error message pops up. For more information, see Error Messages, page 125.

• You are working to correct errors on the To Do List. For more information, see To Do List Messages, page 35.

• You are analyzing a log file that the software produced while running a process.

Related Topics

• Customer Support and Documentation Comments, page 7

Customer Support and Documentation Comments

For the latest support information for this product, use a World Wide Web browser to connect to http://www.intergraph.com/support/.

(8)

(9)

Troubleshooting Tips: An Overview

This section contains general troubleshooting information for each task. For example, some tasks include troubleshooting tools, and some tasks generate log files.

Common

To troubleshoot the software, you can use several utilities delivered with the software, check log files, and run reports.

Troubleshooting Tools

Both the Core and Project Management components include troubleshooting tools. The Core tools are located in [Product Directory]\Core\Tools\Administrator\Bin.

• ErrorLogEnable.exe - Allows you to specify the severity of logged runtime errors. The default setting is 1, which means only critical errors are logged. Setting 4 will log many more errors, including warnings, and could impact performance. You can also specify the name and location of the log file.

• IMSRenderFlag.exe - Allows you to run the software through NetMeeting.

• VersionCheck.exe - Displays the version for each task component in the software.

The Project Management tool is located in [Product Directory]\ProjectMgmt\Tools\bin.

• CheckDataConsistency.exe - Checks data consistency in the databases. You can also run reports to check database integrity. For more information about this subject, see the Database Integrity Guide.

Log Files

One way to find more details about the operations in the software is to check the Core error log file. You can specify the error log file location using the

ErrorLogEnable.exe tool, described above. The file lists the date and time the errors occurred as well as a description for each error.

In addition, several of the software components provide log files. You can find these log files by searching your computer's hard drive for *.log. You can open these log files in a text editor like Notepad and then copy and paste information. For example, you can paste information from the log file into an email message to send to a co-worker.

(10)

Core

The Core component includes troubleshooting tools, which are located in [Product Directory]\Core\Tools\Administrator\Bin.

• ErrorLogEnable.exe - Allows you to specify the severity of logged runtime errors. The default setting is 1, which means only critical errors are logged. Setting 4 will log many more errors, including warnings, and could impact performance. You can also specify the name and location of the log file.

• IMSRenderFlag.exe - Allows you to run the software through NetMeeting and to troubleshoot video card issues.

• VersionCheck.exe - Displays the version for each task component in the software.

You can find out more details about the operations in the software by checking the Core error log file. The error log file location is specified using the

ErrorLogEnable.exe tool, described above. The file lists the date and time the errors occurred as well as a description for each error.

Related Topics

(11)

Drawings and Reports

Log files are used to review activities and errors that occur when working with documents.

Volume and Snapshot Drawings

Two different types of drawings error logs exist: a general Drawings Error Log and error logs for each drawing sheet when generated.

The error logs reside in the following locations.

• The general Drawings Error log (Drawings.log) resides at the location specified in your Temp environment variable. For example, the path to the log might be C:\Documents and Settings\login name\Local Settings\Temp. To view your environment variable, click Start > Settings > Control

Panel. Then, double-click System. On the Advanced tab, click Environment Variables.

• The error logs for the generated drawing sheets reside on the Symbols share on the SmartPlant 3D server computer. For example, the path is [Product

Directory]\CatalogData\Symbols\Drawings\plant_name\...\component_na me\Logs\DrawingNumber1.log, DrawingNumber2.log, and so forth.

Isometric Drawings

Log files for isometric drawings generated in this task reside on the Symbols share on the SmartPlant 3D server. For example, the path is [Product

Directory]\CatalogData\Symbols\Drawings\plant_name\...\component_name\piping_ systems. You can view a message file (.mes), a piping component file (.pcf), and log files for the batch process.

Reports

The log file for reports (SP3DReports.log) resides at the location specified in your Temp environment variable. For example, the path to the log might be C:\Documents and Settings\login name\Local Settings\Temp.

Note

• You can specify the settings for drawings error logging by toggling

switches in the registry. For more information, contact Intergraph Support.

Related Topics

(12)

Electrical

This section contains troubleshooting tips for the Electrical task.

Cable Auto-Routing

When you auto-route cables in the Electrical task, the software creates a log file in your computer's temp folder named CableAutoroute.log. If you are having problems auto-routing cables, refer to this log file.

Related Topics

• Troubleshooting Tips: An Overview, page 9

Equipment and Furnishings

This section contains troubleshooting tips for the Equipment and Furnishings task.

Placing Equipment after Delete and Replace

After bulk loading an Equipment part class using the Delete and Replace mode, the parts from the class are not available for placement. The root node corresponding to the part class is not available while placing the part.

Related Topics

Grids

Due to the 32-bit precision limitations of graphics cards, objects in the model should be within 100,000 meters of the Global Coordinate System, or they will not display correctly. If your plant coordinate values are larger that this limit (for example, E = 200,000, N = 300,000), in order to get the coordinate readout desired, you should define a coordinate system at correspondingly large negative values (in our example, E = -200,000, N = -300,000). You should then use the coordinate system you created as your active coordinate system for modeling and output. Do not bring this new coordinate system into your workspace, or you will have the display problem you want to avoid.

Related Topics

(13)

Hangers and Supports

This section contains troubleshooting tips for the Hangers and Supports task.

Related Topics

HVAC

This section contains troubleshooting tips for the HVAC task.

Placing HVAC Parts after Delete and Replace

After bulk loading an HVAC part class using the Delete and Replace mode, the parts from the class are not available for placement. The root node corresponding to the part class is not available while placing the part.

Related Topics

(14)

Integration

This section contains troubleshooting tips for integration.

Registering Your Registering Your Plant with Another SmartPlant Foundation Plant

If you want to register your plant with a different SmartPlant Foundation plant, you can run the Remove Design Basis custom command, which removes all correlation relationships and deletes all design basis objects in the 3D model.

Then, you can register the plant. You must retrieve all the data again, and re-correlate objects.

Important

• You must run the Remove Design Basis command from a task in the model, not from Project Management.

1. Start the software.

2. Click Tools > Custom Commands.

3. Click Add on the dialog box.

4. In the Command ProgID box, type

IMSEngFrameworkCmd.RemoveDsgnBasis.

5. In the Command name box, type text such as Remove Design Basis.

6. Click OK on the Add Custom Command dialog box.

7. Select the command name, and click Run. 8. Click Yes on the message boxes.

Notes

• After running this command, register the plant, retrieve information, and re-correlate objects.

• For more information about other custom commands, see the Common User's Guide, available from Help > Printable Guides in the software.

Verifying P&ID Integrity

If there is a problem displaying a P&ID or selecting objects on a P&ID, you can run a custom command to troubleshoot the connections between the objects on the P&ID and the objects in the Model database. The ProgID for this command is

SP3DDisplayPIDService.VerifyPIDCmd, and it provides the following statistics for a selected P&ID.

(15)

• 3D Objects: The number of design basis objects that have a correlated relationship between the P&ID document and the SmartPlant 3D object. The current correlation status is also reported.

• P&ID Objects (Total Identified): This count is the total number of RAD objects that have a drawing ID in the P&ID document. The total identified should match the number of Design Basis Objects. These objects are displayed with their representation ID.

• P&ID Objects (contained in Design Basis): The number of RAD objects that have a graphic OID that will map to drawing representation design basis objects. This number should match the Design Basis Object count. A mismatch most likely means that the objects were deleted. The difference is the number of Deleted P&ID OIDs.

• Deleted P&ID OIDs: The number of RAD objects that have a graphic OID but do not exist in the model.

• Duplicate OIDs: The number of multiple RAD objects with the same graphic OID. Most likely, there is a problem with the P&ID file or with the integrated environment.

• Miscellaneous Errors - Any errors not defined above are in this category.

Accessing Map Files

When running the Compare Design Basis command, the software looks for the map file on the Symbols share. If you do not have access to this share or to the map file, you will see an error message. Ask your administrator to grant you access privileges to the Symbols share.

Mapping Enumerated Lists

To use a new enumerated list (also called codelist or select list) in an integrated environment that includes SmartPlant 3D, you must map the list in the

EFSchema.xml file (SmartPlant schema). If the list does not already exist in the SmartPlant schema, then it has to be created there and mapped. If it already exists in the SmartPlant schema, then you must define the mapping between the SmartPlant schema and the tool map schema.

You must also generate component schemas to create a new P3DComponent.xml file, which is part of the SmartPlant schema. You will also need to make the same

additions in the SP3DPublishMap.xml file. You can do these mapping operations using the Schema Editor software.

For example, if you want to add Fluid System values, modify the EFSchema.xml file to include the fluid codes that are missing. You can examine the catalog data in the Catalog task or in the Excel .xls files that were bulkloaded to find out which fluid codes to add.

(16)

Important

• User reference data codes start at 10,000. Values less than 10,000 are reserved for use by Intergraph.

Here are some important points to check when troubleshooting the mapping of enumerated lists:

• Did you extend the enumerated list in the SmartPlant schema?

• Did you extend the SmartPlant 3D publish map?

• Have you used the same value in both the SmartPlant schema and 3D publish map?

• Have you regenerated component schemas?

• Have you regenerated the views on the Model database? You can use the View Generator at [Product Directory]\Core\Tools\Administrator\Bin for this purpose. The schema to use is the Catalog Schema database.

Related Topics

(17)

Piping

This section contains troubleshooting information for the Piping task.

Paste and Restore Limitations

If you select only a branch run, you can copy and restore it fine. But, if you change some properties on the branch feature which is in working, those properties will retain instead of replacing the branch feature from back since it got trimmed while doing copy paste. Branch features from backup will not get replaced. The same issue observed while restoring the run, alone which is connected to the equipment. Since the software copied only the connected run the software will not copy the logical distribution connection (LDC) and the LDC, which is there in working, will get retained.

Setting Colors Based on Fluid Codes

You can specify the color of pipe based on the fluid code by using filters and surface style rules. For more information, see the Common User's Guide available from the

Help > Printable Guides command in the software. Related Topics

Project Management

The Project Management component includes a delivered troubleshooting tool, which is located in [Product Directory]\ProjectMgmt\Tools\bin. The tool is called

CheckDataConsistency.exe, and it checks data consistency in the databases. For more information about data consistency, see the Database Integrity Guide.

Related Topics

(18)

Space Management

This section contains troubleshooting tips for the Space Management task.

Related Topics

Structural Analysis

This section contains troubleshooting tips for the Structural Analysis task.

Paste/Restore Limitations

Loads/Load Cases/Load Combinations/Boundary Conditions

Behavior

No special behavior beyond a typical paste operation.

Limitations

No known limitations at this time.

Related Topics

(19)

Structure

This section contains troubleshooting tips for the Structure task.

Paste Restore Behavior/Status/Limitations

This section describes the object specific behavior, limitations and status associated to paste restore of structural members, frame connections, split connections, assembly connections, footings, ladders/stairs, equipment foundations and handrails.

Members

Behavior

Copying a member part always includes its member system and copying the member system always includes the member parts; therefore, paste restore of a member restores both the member system and member part properties.

Limitations

Cannot restore only the member part – its member system (including its fame connections) will always be restored too.

Frame Connections

Behavior

A stand-alone frame connection cannot be copied; frame connections are automatically copied when the member part or member system are copied. The frame connections associated to the restored member system always replace/update the frame connections in the working data, which includes:

• Changing any related member system frame connections to Unsupported if the restored frame connection conflicts with any existing frame

(20)

• Removing split connections if a restored member system has a frame connection other than Unsupported and the same member system end splits another member system:

Limitations

You cannot paste restore a member system and frame connection such that it would introduce a loop; the restore process is aborted.

(21)

Split Connections

Behavior

Split connections are considered features of the member system; therefore, all split connections of a member system within the back up replace those in the working set. For example, a member system that has a split first connection restored into a

working data set where the member system has had the original split removed and another one added will result in the member system and the split first connection being restored removing the newly added split connection in the working set.

Limitations

Split connections are copied explicitly when a member system is copied except when the split connection is Split-none. A Split-none connection must be selected along with the member system if the intent is to copy the split connection.

Adding or removing split connections in the working set and subsequently only restoring the split member system will result in the removal of all the external relationships to the member parts. This would include such relationships as ladders related to a part edge, hangers and supports related to the edge or plane port of a part. In most cases the object losing its relationship will be sent to the To Do list. In some cases, the related items will be removed (such as analytical loads assigned to a member). If all related items are restored along with the member system then these relationships will not be affected.

Similar to the above limitation, if in the working set split connections are added or removed and subsequently new relationships are added to member parts, the related data will be disconnected upon a paste restore of the split member system. In most cases the object being disconnected will be sent to the To Do list. In some cases, the related items will be removed such as analytical loads assigned to a member part. Restoring a split member system into a condition where the working data has splitting member systems attached with frame connections other than Unsupported, the split connection will not be restored. The following demonstrates an example of this:

(22)

and the Axis-along frame connection forces the split to be removed from the restored data. If in the above example both the splitting and split members were restored then the split connection would have been restored because the Axis-Along frame

connection would have been restored with an Unsupported frame connection.

Assembly Connections

Behavior

Paste restore behavior is similar to that of a normal copy and paste of an individual assembly connection where multiple assembly connections may result at the intersection of two or more member systems. The result will be that one of the assembly connections will go to the To Do list.

Limitations

During SP3D manipulation of frame connections, assembly connections are automatically removed when the related supported member's frame connection changes to "Unsupported". Therefore, restoring two member systems with its assembly connection may result in the assembly connection being restored and immediately being removed during the restore process. This happens only when the frame connection of the supported member changes to "Unsupported" similar to the edit behavior. The following example demonstrates this limitation:

Footings

Behavior

The backed up footing replaces the working version of the footing including changing its outputs.

(23)

Ladders/Stairs

Behavior

No special paste restore behavior beyond that of normal restore.

Limitations

No limitations at this time.

Equipment Foundations

Behavior

The backed up equipment foundation will replace the working equipment foundation including changing its outputs.

Limitations

No limitations at this time.

Handrails

Behavior

Restoring a handrail includes restoring its type (if the type has change) and/or restoring its path if the path was modified. The path of the handrail is considered a part of the handrail; therefore, the backup path of the handrail replaces the working data path for the handrail.

Limitations

(24)

Slabs

Behavior

Backup Model After Restore

Slab-1 with no opening to paste and restore in the working Model

Slab-1 with Opening-1

Slab-1 with no opening Opening-1 removed

Slab-1 with Opening-1 to paste and restore in the working Model

Slab-1 with Opening-1 + Opening-2 + Opening-3

Slab-1 with Opening-1 Opening-2 removed Opening-3 removed

(25)

Slab-1 with Opening-2 + Opening-3

Workflow Details: - Place Opening-2 + Opening-3 on the same port face as the Opening-1 - Remove Opening-1

Slab-1 with Opening-1 - Opening-1 restored - Opening-2 removed - Opening-3 removed Technical Details:

- Opening-1 and Opening-2 + Opening-3 were

generated by the same CustomComponent. In this case the

CustomComponent is overridden

Slab-1 with Opening-2 and Opening-3

Workflow Details: - Remove Opening-1 - Place Opening-2 and Opening-3 on the same port face as the Opening-1

Slab-1 with Opening-1 - Opening-1 restored - Opening-2 removed - Opening-3 removed Technical Details:

- Opening-2 and Opening-3 were generated by the a new CustomComponent. In this case it is deleted at restore time and the CustomComponent of the

(26)

Slab-1 with no opening - Ladder-1 connected to Slab-1 using a top edge and a vertical reference port face

Technical Details: - Only Slab-1 is restored, Ladder-1 is connected to the same ports as before the Paste and Restore operation

- Note that Ladder-1 is not connected to stable ports

(27)

Slab-1 with no opening to paste and restore in the

working Model Slab-1 with Opening-1 - Ladder-1 connected to Slab-1 using a top edge and a vertical reference port face

Slab-1 with no opening - Ladder-1 connected to Slab-1 using a top edge and a vertical reference port face

Technical Details : - Before the Paste And Restore operation, the ports referenced by Ladder-1 were extracted from the geometry after cutout. -After Paste And Restore the ports are extracted from the geometry after trim

(28)

Slab-1 with Opening-1 - Pump-1 placed on Slab-1 using a mating relationship with a stable face port (before cutout)

Slab-1 with no opening - Pump-1 placed on Slab-1 using a mating relationship with a stable face port (before cutout = after trim) Technical Details :

Before and after the Paste and Restore operation Pump-1 is connected to stable port extracted from the geometry after trim

Slab-1 with Opening-1 and Opening-2

- Pump-1 placed on Slab-1 using a mating relationship with a stable face port (before cutout)

Slab-1 with Opening-1 - Pump-1 placed on Slab-1 using a mating relationship with a stable face port (before cutout = after trim)

(29)

Slab-1 with 4 boundaries: 3 gridlines and 1 sketch3D object

- Slab-1 is to be pasted and restored in the working model

Slab-1 with 4 boundaries - Skectch3D boundary modified

Slab-1 with 4 boundaries - Skectch3D restored

Slab-1 with 4 boundaries: 4 gridlines

- Slab-1 is to be pasted and restored in the working

Slab-1 with 5 boundaries - 4 gridlines + 1 sketch3D

Slab-1 with 4 boundaries - Sketch3D boundary removed

(30)

- Slab-1 is to be pasted and restored in the working model

Slab-1 with 5 boundaries - 4 gridlines + 1 Sketch2D

Slab-1 with 4 boundaries - Sketch2D boundary removed

- Slab -1 is to be pasted and restored in the working model

- left boundary replaced by another gridline

- Original gridline referenced as boundary

(31)

Openings

Behavior

Slab-1 with Opening-1 - Opening-1 is to be pasted and restored in the working model

Slab-1 with Opening-1 - Opening-1 sketched contour moved/modified

Slab-1 with Opening-1 - Opening-1 position and sketched curve is restored as in the backup DB Technical Details: Orientation inputs are reconnect by default in the case where Opening-1 parent slab is still Slab-1

Slab-1 with Opening-1 - Opening-1 is to be pasted and restored in the working Model

Slab-1 with Opening-1 + Opening-2 + Opening-3 - Opening-2 & Opening-3 are added to the same sketch.

Slab-1 with Opening-1 + Opening-2 + Opening-3 - Opening-1 restored Technical Details : The sketch2D is restored but since Opening-2 & Opening-3 must be kept, the restored sketch2D must be adapted to re-include the related 2D curves

(32)

Slab-1 with Opening-1 - Opening-1 is to be pasted and restored in the working Model Slab-1 Opening-2 + Opening-3 Workflow Details: - Remove Opening-1 - Place Opening-2 + Opening-3 on the same port face as the Opening-1

Slab-1 with Opening-1 + Opening-2 + Opening-3 - Opening-1 restored Technical Details : In this Opening-1 has a separate Sketch

CustomComponent. So it is simply restored. Opening-2 & Opening-3 Sketch CustomComponent is unchanged

Slab-1 with Opening-1 + Slab-2

- Opening-1 is to be pasted and restored in the working Model

Slab-1 with Opening-1 + Slab-2

- Opening-1 sketched contour moved/modified

Slab-1 + Slab-2 with Opening-1

- Opening-1 restored on Slab-2

Technical Details : Since a new parent slab is selected the

SketchReferencecollection of the restored

CustomComponent for Opening-1 must be adapted

(33)

Missing Frame Connections

Occasionally during modeling, a member might lose one of its frame connections. A common example of this can happen when a beam frames into the middle of a column, and then you delete the column. The frame connection on the beam-end closest to the column is also deleted. To restore relationships for that end of the beam, you must re-create the frame connection:

1. Click Select on the vertical toolbar.

2. Set the Locate Filter to Member Parts.

3. Select the member with the missing frame connection.

4. Look for the triad that indicates which end of the member is the start end. 5. If the missing frame connection is at the start end of the member, click Start

on the ribbon. If the missing frame connection is at the end of the member, click

End on the ribbon.

The software re-creates the missing frame connection and automatically activates the edit frame connection ribbon.

6. Optionally, select By Rule in the Connection box and define a new end location

of the member.

Related Topics

(34)

(35)

To Do List Messages

This section lists the notes that may appear on the To Do List. You can access the To Do List by clicking View > To Do List or by pressing CRTL+T on your keyboard. You can filter the To Do List messages that appear in the list by selecting objects in the model, and then clicking Filter To Do List By Select Set on the dialog box. Only To Do List messages associated with the selected object appear in the list. To view all the To Do List messages again, click Clear Filter.

The notes are organized here alphabetically by the first word in the note. To Do List: A, page 36 To Do List: B, page 46 To Do List: C, page 49 To Do List: D, page 57 To Do List: E, page 59 To Do List: F, page 63 To Do List: G, page 69 To Do List: H, page 71 To Do List: I, page 73 To Do List: J, page 76 To Do List: K, page 76 To Do List: L, page 77 To Do List: M, page 78 To Do List: N, page 83 To Do List: O, page 91 To Do List: P, page 93 To Do List: Q, page 96 To Do List: R, page 97 To Do List: S, page 99 To Do List: T, page 110 To Do List: U, page 117 To Do List: V, page 119 To Do List: W, page 123 To Do List: X, page 124 To Do List: Y, page 124 To Do List: Z, page 124

(36)

To Do List: A

The messages are in alphabetical order.

A required part could not be located in the catalog. Reference data should be checked to verify that the required part is included in the piping job specification and is available in the catalog. (Piping, HVAC, Electrical)

Meaning: A required reportable part could not be found in the catalog.

Recovery: Add the missing data in the catalog, or correct the data that is calling the

missing data.

A temperature-based insulation exclusion rule has been defined for this component type; however, the owning run has no temperature defined. You should define a temperature on the owning run in order to ensure the rule is being properly honored. (Piping, HVAC, Electrical)

Meaning: A temperature is not defined for the pipe run. Recovery: Define a valid temperature on the pipe run.

Access Denied. (Hangers and Supports)

Meaning: An object is out-of-date because of permission problems. Recovery: Check the permissions on the object and update the object.

An attempt has been made to delete a connection item. These objects are system-generated and cannot be selected and deleted directly. (Piping, HVAC, Electrical)

Meaning: A connection must exist between two connected parts. You cannot delete

this connection.

Recovery: Delete one of the adjacent features.

An input is in error (Structure)

Meaning: The slab or opening boundary is invalid because one of the input

boundaries is in error.

(37)

Another assembly connection already exists at the member end. This connection has been disabled and should be deleted. (Structure)

Meaning: This occurs only during a paste operation of an assembly connection where

a member part already has an assembly connection but another assembly connection is being pasted at the same member end as the existing one. Because the assembly connection trims the geometry at the member end, two assembly connections cannot apply separate trim operations; hence, one assembly connection must be removed. The paste operation cannot remove the assembly connection so the paste assembly connection is set to "inoperative" and tagged with a To Do List record.

Recovery: Delete the assembly connection because one already exists at the member

end.

Assembly connection has been defined with an unsupported section type. (Structure)

Meaning: Assembly connections only support the well-know section types whose

types are found in the latest AISC set of tables. Arbitrary or sections outside these types are not supported.

Recovery: Delete the Intergraph supplied assembly connection. You might consider

creating your own assembly connection that supports this cross-section type modeled after the Intergraph supplied assembly connection. This would requires a working knowledge of Visual Basic and familiarity with customization of catalog content.

Assembly Info Rule CLSID cannot be retrieved from its ProgID (Hangers and Supports)

Meaning: The Assembly Information Rule program is not registered.

Recovery: Register the Assembly Information Rule specified for the given support

assembly.

Assembly Info Rule object cannot be retrieved from its CLSID. (Hangers and Supports)

Meaning: The software cannot instantiate the Assembly Information Rule. Recovery: Check the Assembly Information Rule program code for problems.

(38)

Assembly Info Rule ProgID cannot be retrieved from the support object. (Hangers and Supports)

Meaning: The software is unable to retrieve the ProgID for the Assembly

Information rule from the catalog data for a given support assembly.

Recovery: Check the spreadsheet for the assembly definition and make sure that the

ProgID for the given support assembly is specified. Make sure the spreadsheet is bulk loaded correctly into the catalog database.

At least one branch from a turn exists in this cableway that is only valid for a "no-part" configuration. The cableway has been changed to a specification that generates parts. As a result, these branch connections are no longer valid. (Piping, HVAC, Electrical)

Meaning:

Recovery:

Attributes cannot be retrieved from hanger rule object (Hangers and Supports)

Meaning: The Rule object failed to retrieve the given attribute value from the catalog

data.

Recovery: Check the rule implementation and see if the corresponding catalog data

exists. Update the catalog data with the necessary information and bulk load. Correct the rule implementation if necessary.

Axis collinear frame connections require the member systems to be collinear. Either modify one of the member systems to make it collinear with the other member or delete the axis collinear frame connection. (Structure)

Meaning: Caused by moving one of the members or its end; or by using a paste

operation of a member with an axis collinear frame connection. A member with an axis collinear frame connection may be moved such that the supported and supporting members are no longer parallel. The copy condition where this occurs is when

copying a member with an axis collinear frame connection and pasting this into a model selecting a member that is not parallel to the pasted member when establishing the axis collinear connection in the paste special dialog.

Recovery: Modify the ends of the members that support this frame connection and

(39)

Axis-along frame connection is invalid because the previous connection was not removed. Change connection to unsupported and the re-select the supporting member. (Structure)

Meaning: The member's frame connection was converted to an axis-along

connection (from another connection type) without first being re-initialized. This is an internal software failure where the calling software did not re-initialize the frame connection as an unsupported frame connection first.

Recovery: Change the frame connection to unsupported and then re-define it as axis

along reselecting the supporting member.

Axis-along frame connection is missing a required input. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Axis along frame connection expects two objects as input: a supported

member and a supporting member to be axis along to. This is an internal software failure where not all the inputs were provided to the axis along connection.

Recovery: Change the frame connection to unsupported and then re-define it as

axis-along by reselecting the supporting member.

Axis-along frame connection is missing the supporting member information. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: The axis along member's supporting member was not provided. This is an

internal software failure where the calling software did not properly call the frame connection with its required inputs.

Axis-along frame connection is related to something other than a supporting member system. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: The input axis along member's supporting member is not a member

system. This is an internal software failure where the calling software did not properly call the frame connection with its required inputs.

(40)

Axis-along frame connection is using the same member system for both the supporting and supported member. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: The axis along connection has the axis along member and the supporting

member as the same object. This is an internal software failure where the calling software is attempting to make a member axis along itself.

Axis-along frame connection was re-verified and found to be invalid. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Re-verification of the axis along connection indicates that it was not

established correctly. This is an internal software failure and not the result of a user action.

Axis-along frame connection's supported member has invalid point-on relationship with another member. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Inconsistent relations exist where the supported member is axis along to

one member system but is related as point-on a different member system. This is an internal software failure and not the result of a user action.

axis-along reselecting the supporting member.

Axis-collinear frame connection has an invalid end port relationship. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Inconsistent relations where the input end port of the supporting member

does not match the related end port of the axis collinear connection. This is an internal software failure where the axis collinear connection was defined incorrectly.

(41)

Axis-collinear frame connection is invalid because the previous connection was not removed. Change connection to unsupported and the re-select the supporting member. (Structure)

Meaning: The axis collinear connection is invalid because the member's frame

connection was converted to an axis collinear connection from another connection type without first re-initializing the frame connection. This is an internal software failure where the calling software did not re-initialize the frame connection as an unsupported frame connection first.

collinear reselecting the supporting member.

Axis-collinear frame connection is missing a required input. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Axis collinear frame connection expects three objects as input: a supported

member, a supporting member to be collinear with, and the end port of the supporting member. This is an internal software failure where not all the inputs were provided to the collinear connection.

Axis-collinear frame connection is missing the supporting member information. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Improper placement of the axis collinear connection where the supporting

member was not provided. This is an internal software failure where the calling software did not properly call the frame connection with its required inputs.

Axis-collinear frame connection is related to something other than a member system. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: This is an internal software failure where one of the two input members are

not member systems.

(42)

Axis-collinear frame connection is related to something other than a supporting member system. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Improper placement of the axis collinear connection where the supporting

member input is not a member system. This is an internal software failure where the calling software did not properly call the frame connection with its required inputs.

Axis-collinear frame connection is using the same member system for both the supporting and supported member. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: The collinear connection has the supported member and the supporting

member as the same object. This is an internal software failure where the calling software is attempting to make a member collinear with itself.

Axis-collinear frame connection requires the same permission group for both member systems. Edit one of the permission groups to match the other. (Structure)

Meaning: To establish the axis collinear connection the permission group of the

supporting member and the supported member must be the same. The software prevents this from occurring during placement and paste; hence, this should never occur unless something unexpected occurred.

Recovery: Reset the permission group of either the supporting or supported member

and they should both get the same permission group. You can also correct this by changing the frame connection to unsupported and then re-define it as axis collinear reselecting the supporting member.

Axis-collinear frame connection was re-verified and found to be invalid. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Re-verification of the axis collinear connection indicates that it was not

(43)

Axis-end frame connection cannot find supported member end. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: The end of the supported member system could not be determined based

on the relations to the supporting member. This indicates that this axis-end

connection was ill-defined. This is an internal software failure and not a result of a user action.

end reselecting the supporting member.

Axis-end frame connection has an invalid end port relationship. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Expected the third input into the axis-end connection to be the end port of

the supporting member. This is an internal software failure where not all the inputs were provided to the connection correctly.

Axis-end frame connection is invalid because the previous connection was not removed. Change connection to unsupported and the re-select the supporting member. (Structure)

Meaning: Improper invocation of the placement of the axis-end connection where the

member's frame connection was converted to an axis-end connection from another connection type without first re-initializing the frame connection. This is an internal software failure where the calling software did not re-initialize the frame connection as an unsupported frame connection first (i.e., failure was not the result of a user action).

Axis-end frame connection is missing a required input. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Axis-end frame connection expects three objects as input: a supported

member, a supporting member to be axis-end with, and the end port of the supporting member. This is an internal software failure where not all the inputs were provided to the axis-end connection.

(44)

Axis-end frame connection is missing the supporting member information. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Improper placement of the axis-end connection where the axis-end

member's supporting member was not provided. This is an internal software failure where the calling software did not properly call the frame connection with its required inputs.

Axis-end frame connection is related to an end port that is different from the supporting member end port. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Inconsistent relations where the input end port of the supporting member

does not match the related end port of the axis-end connection. This is an internal software failure where the axis-end connection was defined incorrectly.

Axis-end frame connection is related to something other than a member system. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: This is an internal software failure where one of the two input members is

not member systems.

Axis-end frame connection is related to something other than a supporting member system. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Improper invocation of the placement of the axis-end connection where the

axis-end member's supporting member input is not a member system. This is an internal software failure where the calling software did not properly call the frame connection with its required inputs.

(45)

Axis-end frame connection is using the same member system for both the supporting and supported member. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Improper placement of the axis-end connection where the supported

member and the supporting member are the same object. This is an internal software failure where the calling software is attempting to make a member axis-end with itself.

Axis-end frame connection relationships are inconsistent. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Inconsistent relations between the axis-end connection defined inputs and

the actual related supporting member system end port. This is an internal software failure and not the result of a user action.

Axis-end frame connection requires the same permission group for both member systems. Edit one of the permission groups to match the other. (Structure)

Meaning: To establish the axis-end connection the permission group of the

supporting member and the supported member must be the same. The software prevents this from occurring during placement and paste; hence, this should never occur unless something unexpected happened.

Recovery: Reset the permission group of either the supporting or supported member

and they should both get the same permission group. One can also correct this by changing the frame connection to unsupported and then re-define it as axis collinear reselecting the supporting member.

Axis-end frame connection was re-verified and found to be invalid. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Re-verification of the axis-end connection indicates that it was not

(46)

To Do List: B

Messages are listed in alphabetical order.

Base plate connection has an invalid number of inputs. Delete and replace. (Structure)

Meaning: The base plate connection was expecting two end ports for placement, but

the input count was not two. This is a software failure, not the result of any user action.

Recovery: Replace the existing assembly connection with an new one by deleting the

current assembly connection and placing a new one.

Bolt length cannot be calculated due to incomplete bolt extension data! To correct this error: (1) verify that bolt extension data is properly defined in SmartPlant 3D reference data or (2) turn off bolt length calculations. (Piping, HVAC, Electrical)

Meaning: The bolt length cannot be calculated due to incomplete bolt extension data. Recovery: Turn off the bolt length calculations, or update the data in the Bolt

Extension rule in the catalog.

Both ends of the cable are not connected to equipment. (Electrical)

Meaning: The software detected that both ends of the cable are not connected to

equipment. This situation can occur if the equipment was deleted after the cable was placed.

Recovery: Edit the cable, and make sure both ends are connected to equipment.

Boundary condition's analysis model is different from the member part's analysis model. (Structural Analysis)

Meaning: The boundary condition belongs to one analysis model, but the member

part to which the boundary condition is associated belongs to another analysis model. Both the boundary condition and the member part must belong to the same analysis model.

Recovery: Edit the analysis model of either the boundary condition or the member

(47)

Brace end is not located near the first supporting member in the vertical corner brace frame connection. Change the connection to unsupported and then re-select the supporting members. (Structure)

Meaning: The X, Y, Z brace end coordinates do not seem to be located near the first

supporting member. This is an internal software failure where the software allowed an improperly connected vertical corner brace.

vertical corner brace reselecting the supporting members.

Brace end is not located near the second supporting member in the vertical corner brace frame connection. Change the connection to unsupported and then re-select the supporting members. (Structure)

Meaning: The X, Y, Z brace end coordinates do not seem to be located near the

second supporting member. This is an internal software failure where the software allowed an improperly connected vertical corner brace.

Brace is not in the same plane as the supporting members. (Structure)

Meaning: Vertical corner brace placed out of plane with respect to the supporting

members.

Recovery: Edit the brace's section size such that it is smaller than the member being

braced. Also, verify the cardinal point of the brace is correct with respect to the braced member.

Brace is not point-on related to a split connection or an end-joint of a member. Change connection to unsupported and then re-select the intersection. (Structure)

Meaning: The brace must be related (using a point-on relationship) to a split

connection or an end-joint of a member. This is an internal software failure where the relationships for the vertical corner brace were not established correctly.

Branch nominal diameter is larger than header nominal diameter (Piping, HVAC, Electrical)

(48)

Branch reinforcement calculations could not be made due to an instantiation error in calculation component. If this component has been customized, your programmer should debug this code. Otherwise, a service request should be logged with

Intergraph. (Piping, HVAC, Electrical)

Meaning: The BranchreinforcementProgID is defined and registered, but there is an

error instantiating it.

Recovery: Contact Intergraph support for assistance.

Branch reinforcement calculations could not be made. The software component used to perform these calculations has not been registered on this client. Please check the ProgID specified in your catalog data and ensure it is properly registered. (Piping, HVAC, Electrical)

Meaning: The BranchreinforcementProgID is defined, but is not registered. Recovery: Register the component.

Branch reinforcement calculations could not be made. The software component used to perform these calculations has not been defined. Please check that a valid ProgID has been specified in your catalog and that it ahs been registered. (Piping, HVAC, Electrical)

Meaning: BranchreinforcementProgID is not defined for the Design Standard in the

Calculation ProgIDs rule.

(49)

To Do List: C

Messages are listed in alphabetical order. Cannot apply bound operation. (Structure)

Meaning: The bound operation failed.

Recovery: Check the boundaries of the slab or opening. The boundaries should form

a closed contour.

Cannot apply cutout(s) (Structure)

Meaning: The cutout operation failed.

Recovery: Edit the opening shape and verify its placement.

Cannot calculate reference ports (Hangers and Supports)

Meaning: The software could not calculate the reference ports with the given

configuration of the route and structure. This generally happens you place a support by a structure with the Rule option set to OFF; then the structure is modified in a way that the route and structure are not properly configured for the support.

Recovery: Select a new structure reference port for the support.

Cannot compute weight and CG (Structure)

Meaning: The evaluation of the weight and CG failed. Recovery: Try to re-compute the slab.

Cannot create cutout (Structure)

Meaning: The evaluation of the operator (cutting tool) of the cutout operation failed. Recovery:

Cannot delete connected Tap Feature without deleting Tapped Feature too. (Piping, HVAC, Electrical)

Meaning: You cannot delete a connected tap feature without also deleting the tapped

feature.

(50)

Cannot delete run change feature. (Piping, HVAC, Electrical)

Meaning: A run change feature must exist between two connected features of

different runs. Deletion of this run change is not allowed.

Recovery: Delete one of the adjacent features or change its run such that the run

change is no longer required.

Cannot modify a read-only object (Structure)

Meaning: Attempting to apply a cope feature to a read-only member part (that is, the

approval status is non-working or the member part's permission group does not allow write access). Changes to the model may trigger already approved member parts features to be recomputed so this could happen as a result of many different actions.

Recovery: Ask you local administrator for permissions to the member part to perform

this action on the member part.

Cannot project bounding line on supporting plane (Structure)

Meaning: One of the opening's or slab's boundary lines cannot be projected on the

support plane.

Recovery: Check the opening or slab boundaries.

Cannot use this frame connection as Obj1 to SetRelatedObject. See To Do List messages in the Troubleshooting Guide for more information. (Structure)

Meaning: Improper use of an unsupported connection where an unexprected frame

connection was provided as input. This is an internal software failure and not the result of a user action.

Recovery: This is a software problem and it is likely that the frame connections

provided by Intergraph were customized and a custom code failure occurred. It is not recommended users override the delivered frame connections because they are difficult to write and debug. The originally Intergraph delivered frame connections should be used instead.

Cannot use this frame connection as Obj2 to SetRelatedObject. See To Do List messages in the Troubleshooting Guide for more information. (Structure)

Meaning: Improper use of an unsupported connection where an unexprected frame

connection was provided as the second input into defining the connection. This is an internal software failure and not the result of a user action.

(51)

difficult to write and debug. The originally Intergraph delivered frame connections should be used instead.

Catalog Connection Part has been deleted. (Piping, HVAC, Electrical)

Meaning: The connection part (clamp, gasket, bolt, nut, washer) in the catalog was

deleted.

Recovery: User the Verify Consistency tool to verify that connection information in

the catalog and make any necessary corrections.

Catalog Parts were not obtained from Assembly Information Rule. (Hangers and Supports)

Meaning: The Assembly definition may have been deleted from the catalog database

after placement.

Recovery: Check the Assembly definition spreadsheet. Add the appropriate assembly

definition if necessary. Bulk load the spreadsheet and use the Synchronize Model

with Catalog command in the Project Management task to update the catalog

information with the model.

Centerline frame connection is invalid because the previous connection was not removed. Change connection to unsupported and the re-select the supporting member. (Structure)

Meaning: Improper invocation of the placement of the centerline connection where

the member's frame connection was converted to a centerline connection from another connection type without first re-initializing the frame connection. This is an internal software failure where the calling software did not re-initialize the frame connection as an unsupported frame connection first.

centerline reselecting the supporting member.

Centerline frame connection is missing a required input. Change connection to unsupported and then re-select the supporting member. (Structure)

Meaning: Centerline frame connection expects two objects as input: a supported

member and a supporting member to be centerline with. This is an internal software failure where not all the inputs were provided to the centerline connection.

Troubleshooting Guide

SmartPlant 3D

Table of Contents

Preface

What's New with Troubleshooting

Troubleshooting: An Overview

Customer Support and Documentation Comments

Troubleshooting Tips: An Overview

Common

Core

Drawings and Reports

Electrical

Equipment and Furnishings

Grids

Hangers and Supports

HVAC

Integration

Piping

Paste and Restore Limitations

Setting Colors Based on Fluid Codes

Project Management

Space Management

Structural Analysis

Paste/Restore Limitations

Loads/Load Cases/Load Combinations/Boundary Conditions

Structure

Paste Restore Behavior/Status/Limitations

Members

Frame Connections

Split Connections

Assembly Connections

Footings

Ladders/Stairs

Equipment Foundations

Handrails

Slabs

Openings

Missing Frame Connections

To Do List Messages

To Do List: A

To Do List: B

To Do List: C