User’s Guide – FileFixer for V8

Chapter 9 — Repair Settings

Factory defaults

Unless indicated otherwise, the settings illustrated in the following screen images reflect FileFixer’s factory default settings.

B-spline

“Repair Settings”, “B-spline” category.

Open the closed b-spline that has duplicate b-spline poles

A b-spline pole element (type 21) normally doesn’t have duplicated first and/or last poles, and its first and last poles normally don’t match.

To avoid problems, for example to retain backward compatibility with MicroStation SE, change the closed b-spline to an open b-spline.

The search setting that detects this error is Settings | Change Settings | Search... | Vertices | Duplicate b-spline poles detected in a closed b-spline.

The error number reported is 905.

Cell

“Repair Settings”, “Cell” category.

Adjust non-shared cell class map.

This repair setting corrects the list of classes (which is stored in the cell header element) used by elements in the cell.

The search setting that detects this error is Settings | Change Settings | Search... | Cell | Non-shared cell class map is incorrect.

The error number that is reported is 717.

Correct null cell names (type 2s only) by setting the H-bit.

In this context, “null” means empty — no cell name. A type 2 cell in a cell library is not required to have a name, but nameless type 2 cells should not exist in a cell library unless their H-bit is set to indicate they are “orphan cells”.

FileFixer will ensure nameless type 2 cells have their H-bit set.

The repair setting is “Correct null cell names (type 2s only) by setting the H-bit.” This setting is ON by default.

The error number reported is 570.

Delete cell nested within itself.

Use this setting to delete any cell nested within itself. All duplicate nested cells will be deleted.

The search setting that detects this error is Settings | Change Settings | Search... | Cell | Cell is nested within itself.

The error number that is reported when the nested cell is in a design file is 383.

This setting is OFF by default.

Delete shared cell definition with no shared cell instances.

Delete the shared cell definition that has no shared cell instance. This happens quite often when importing DWG files to MicroStation.

The search setting that detects this error is Settings | Change Settings | Search... | Cell | Shared cell definition with no shared cell instance.

The error number reported is 303.

Handle missing shared cell definitions.

When a shared cell instance is found with no corresponding shared cell definition, then use this repair setting to fix it in one of two ways.

Add the shared cell definition from an available cell library. When this option is chosen FileFixer creates a shared cell definition using a cell with the same name found in one of the cell libraries searched in the active MicroStation workspace. If a matching cell name is not found FileFixer will report that it could not be found in the report.

Note: FileFixer uses its own seed file during repair, therefore it will not know of a cell library that is attached to the original file being fixed. For this reason it is important that the cell libraries containing the cells you want use are found in one of the directories MicroStation searches in the active workspace.

Create a dummy shared cell definition. When this option is chosen FileFixer creates a dummy shared cell definition with a single component text element that displays the shared cell’s name.

The search setting that detects this error is Settings | Change Settings | Search... | Cell | Shared cell instance has no shared cell definition.

The error number reported is 768.

Complex

“Repair Settings”, “Complex” category.

Add line to bridge gap in 2D complex shape or chain.

When creating a 2D complex shape or chain from multiple linear elements that have gaps between the endpoints, MicroStation will not actually create the connecting lines, but MicroStation will display a line between those endpoints. If these complex elements are later dropped, gaps will exist between the component elements.

The search setting that detects this error is “Settings | Change Settings | Search... | Complex | Gap exists in 2D complex shape or chain. This repair option is off by default.

The error number reported is 151.

Correct complex bit errors.

FileFixer clears the complex bit for an element that is not a component of a complex element but does have the complex bit set. The error number reported for this error is 702.

FileFixer sets the complex bit for an element that is a component of a complex element but does not have its complex bit set. The error number reported for this error is 703.

The search settings that detect these errors are Settings | Change Settings | Search... | Complex | Complex bit is on for a non-component element and Settings | Change Settings | Search... | Complex | Complex bit is off for a component element.

Delete shared cell instance nested in a shared cell definition with the same cell name.

Use this repair setting to delete the shared cell instance nested in a shared cell definition with the same name.

The search setting that detects this error is Settings | Change Settings | Search... | Complex | Shared cell instance nested in a shared cell definition with the same name.

The error number reported is 733.

Move components to same level as complex header.

Use this repair setting to move the component element to the same level as the complex header.

The search setting that detects this error is Settings | Change Settings | Search... | Complex | Component on different level than its header.

The error number reported is 336.

Set graphic group of component to match its header.

FileFixer changes the graphic group number of the component element to match the header.

This error is not reported for component elements that are part of regular cells (type 2), shared cell definitions (type 34) or raster headers (type 87 or type 90).

This error is not reported for components of non-graphical complex headers, such as level table entries, etc.

The search setting that detects this error is Settings | Change Settings | Search... | Complex | Component graphic group doesn’t match header.

The error number reported is 341.

Handle illegal components in complex element.

For example, an ellipse should not be a component in a text node. When FileFixer encounters an illegal component, the complex element is normally broken up into its component parts. (Traditional jargon for this is to “drop complex status” or “drop status”.)

There are two special cases where other settings are available:

When deleted components are found in a complex header, FileFixer allows you to either break up the complex element into its component parts (traditional jargon is to “drop status on the complex header”) or remove (“squeeze out”) the deleted component elements.

The following specialized repair settings are available for nested shared cell definitions (type 34):

You won’t want to automatically delete the nested shared cell if it is referenced by a shared cell instance (type 35) or if it is used as a pattern. In these cases you can choose to convert the outer shared cell definition to a cell. The default handling with nested shared cells is “Don’t do anything”.

The search setting that detects this error is Settings | Change Settings | Search... | Complex | Complex element contains disallowed element type.

The error number reported is 721. This search setting also controls error numbers 121 and 323, but the only error repaired is 721.

Dimension

“Repair Settings”, “Dimension” category.

Remove dimension element with no data points or associative points.

Remove the dimension element that doesn’t have at least one data point or associative point. An associative point is a point that ties this dimension element to another element in the design file.

The search setting that detects this error is Settings | Change Settings | Search... | Dimension | Dimension element with no data points or associative points.

The error number reported is 722.

Element

“Repair Settings”, “Element” category.

Delete graphical element in non-graphical data.

Graphical elements in the non-graphical data area can cause MicroStation V8i to lock up or abort. This data area is for reference file attachments, application data elements, etc.

The search setting that detects this error is Settings | Change Settings | Search | Element | Graphical element in non-graphical data.

The error number reported is 819.

Fix invisible graphical element by:

MicroStation V8 has the ability to make an element “invisible”. It will not be displayed on MicroStation’s GUI or be plotted. This is a new MicroStation feature so these elements are not really corrupted, which is why this setting is OFF by default.

If you use Cimmetry's AutoVue application, which does display these elements, then the AutoVue GUI can be a little confusing. This is the reason for this setting.

With this repair setting FileFixer either makes visible or deletes “invisible” graphical elements. FileFixer will not make visible or delete pattern control elements of tag elements.

The search setting that detects this error is Settings | Change Settings | Search... | Element | Graphical element is invisible.

The error number reported is 240.

Fix reserved bits by clearing them?

This repair setting FileFixer turns off the six reserved bits in element headers.

The search setting that detects this error is Settings | Change Settings | Search... | Element | Reserved bits are set in element header.

The error number reported is 103.

Remove elements with too few vertices.

With this repair setting FileFixer will remove any element with too few vertices.

Error number 788 is reported when a b-spline pole has less than two poles.

Error number 789 is reported when elements with vertices, points, etc., do not have the minimum number.

The search setting that detects this error is Settings | Change Settings | Search... | Vertices | Too few vertices on line string, shape, curve, etc.

Remove illegal element types.

FileFixer will delete illegal element types detected, such as type 0, 20 and 127. The error number reported is 380.

Error number 380 is controlled by the search setting Settings | Change Settings | Search...

| Type/Level | Illegal element type (0, 1, 20, 127, etc.).

Note: Also see description for error 302 — Type 1 (V7 cell library header) elements are not allowed in design files.

Set the element’s dimension to match the model’s dimension.

Set the element’s dimension to the model’s dimension.

The search setting that detects this error is Settings | Change Settings | Search ... | Element | Element’s and model’s dimensions are different.

The error number reported is 437.

Set illegal class to:

Set the illegal class (greater than 6) to the class you have specified.

The search setting that detects this error is Settings | Change Settings | Search... | Element | Element class is illegal (must be less than 7).

The error number reported is 333.

Turn off illegal H-bits.

The H-Bit means different things for different element types. The only elements whose H-Bit should be set are cells (type 2), lines (type 3), shapes (type 6), complex shapes (type 14), ellipses (type 15), and element types 21 through 28. The reported element was not one of these types, yet its H-Bit was set.

The search setting that detects this error is Settings | Change Settings | Search... | Element | H-bit is set when it shouldn’t be.

The error number reported is 304.

Delete problem elements based on the error they generate.

This setting is provided for user convenience. If you decide to delete one or more problem elements based on the error number they generate, use this setting.

Example:

You can enter a series of error numbers separated by commas.

The <Select> button allows you to select from a list of error numbers and their descriptions.

FileFixer will delete all elements with matching error numbers.

Note: If the element that generated the error is a complex header element, FileFixer will break up the complex element into its individual components and delete just the complex header. You can use Problem Element Viewer to locate, view and delete all components.

ElementSize

“Repair Settings”, “ElementSize” category.

Filter factor

“Filter factor” is used only when repairing elementSize errors.

The default “Filter factor” usually works well, but trying different values can improve results in some cases.

The “Filter factor” determines how selective FileFixer is in determining when it has encountered a valid element chain. If the “Filter factor” is too low, FileFixer may think it has encountered a valid element chain when it has not. If the “Filter factor” is too high, FileFixer might ignore a valid element chain.

Fix element size warnings.

This repair setting directs FileFixer to fix error number 364 — the element’s attribute linkage extends beyond the end of the element. This means the element’s linkage overlaps the next element.

Enter-Data-Fields

“Repair Settings”, “Enter-Data-Fields” category.

Correct EDF/text length mismatches.

FileFixer deletes Enter-Data-Fields (EDFs) when there are more than 20 and when they exceed the length of the element.

FileFixer extends the text string when there are 20 or fewer EDFs and they don’t exceed the element’s length so that the largest Enter-Data-Field completes within the text string.

The search setting that detects the 191 error is Settings | Change Settings | Search... | EDF | Text element has more EDFs than characters.

The error number reported is 191.

Headers

“Repair Settings”, “Headers” category.

Correct the design file header’s level

FileFixer set the design file header’s level to 8.

When the design file header’s level number is not 8 then the “Unable to open design file. Please contact your local site administrator or technical support provider for further assistance.” message is displayed by MicroStation V8.

The search setting that detects this error is Settings | Change Settings | Search... | Headers | Design file header is on the wrong level.

The error number reported is 911.

Replace Non-Model Header or Table

There are a number of header elements and tables in the non-model section of the V8 design file. This section gives you the ability to replace them when you are having a problem with one or more of them.

Replace the design file header element.

The design file header (type 9) element is the first element in a MicroStation design file.

It stores a variety of vital information.

Design file header corruption can manifest itself in a number of ways:

  • Unable to open the design file in MicroStation.
  • FIT command behaves oddly.
  • After loading the file, MicroStation aborts.
  • Text elements do not display correctly.
  • Other odd, inexplicable behavior.

FileFixer can replace a corrupt design file header with a healthy one.

The error number is 21.

NoteFileFixer will never attempt to replace a design file header unless you explicitly activate the option Settings | Repair Settings | Replace the design file header element in the active session. Once you close FileFixer this option is turned off. Accordingly, error number 21 will never be reported by FileFixer’s Search for Problems command. There is no Search setting which enables or disables error number 21.

Copy or Replace Tables

You have the ability to copy or replace the level table, font table, text style table, dimension style table, dictionary table, multi-line style table, line style name table, line style definition table or the filter table.

Copy and replace work slightly differently. Replace will only replace the table if it already exist. Copy will replace the table if it already exists or just copy it in if it isn't already in the design file.

The error number is 22.

Note: FileFixer will never attempt to replace a non-model table unless you explicitly activate the copy or replace option for that non-model table in the active session. Once you close FileFixer all “Copy” and “Replace” settings you have made are turned off. Accordingly, error number 22 will never be reported by FileFixer’s Search for Problems command. There is no Search setting which enables or disables error number 22.

Levels

“Repair Settings”, “Levels” category.

Delete duplicate master file level numbers by:

The level number displayed by MicroStation (in the Level Manager dialog) is user-editable and, therefore, not guaranteed to be unique. Internally (not viewable by users) MicroStation assigns a unique level “code” to each defined level.

By default, FileFixer keeps the first duplicate level table entry associated with a master file level number. You can optionally keep the last level table entry for a duplicate master file level number.

Note: FileFixer always retains the “Default” level definition regardless of the repair option selected here. This is a MicroStation requirement.

The search setting that detects this error is Settings | Change Settings | Search... | Levels | Multiple level numbers.

The error number is 429.Delete unused master file level tables

FileFixer allows you to keep the master file level table with the lowest ID (typically the original) or to keep the first master file level table.

MicroStation V8.5.2.35 and later use the master file level table with the lowest ID (typically the original). Earlier versions of MicroStation V8 use the first master file level table found in the design file.

The search setting that detects this error is Settings | Change Settings | Search... | Levels | Multiple master file level tables.

The error number reported is 630.

Delete unused reference file level tables.

Select this setting if you would like FileFixer to delete unused reference file level tables. The search setting that detects this error is Settings | Change Settings | Search... | Levels | | Unused reference file level tables.

The error number is 267.

Display hidden levels

FileFixer makes hidden levels displayable in MicroStation’s Level Manager.

The search setting that detects hidden levels is Settings | Change Settings | Search... | Levels | Level is hidden.

The error number reported is 444.

Repair elements on corrupted levels

When error 415 appears in your FileFixer report, you can select from the following level renaming strategies — whichever is best suited for your project:

When an element is found to contain a level that is not present in the level table, FileFixer will change the element’s level to a new level or a user-selected level.

Automatically generate new level names prefixed with

FileFixer can automatically generate a new level name for each level missing from the level table. Using the following setting you can specify the prefix for the automatically generated levels:

The default prefix is “Repaired by FileFixer”. The level number used for the new level will be appended onto the end of the level name. The level numbers used will begin with

  1. The level name for the first level added using the default prefix will be “Repaired by FileFixer 4000000”.

Note: the level prefix you specify is used to create level names, so it cannot contain the

following illegal characters: <>\/”?*|,=’&.

Move all elements on undefined levels to the same level

FileFixer can also move all elements on undefined levels to the same level.

You can either use an already defined level name or specify a new level name. If the level name doesn’t already exist in the level table then FileFixer will use the level name entered as a prefix and append the level number (starting at 4000000) onto the end of the prefix.

Move all elements on undefined levels to the default level (level number 0).

FileFixer can also move all elements to the default level. Normally, the default level will be named “Default”, but not always. The default level’s displayed level number will always be zero.

Move component element on undefined level to its parent’s level.

FileFixer will set the corrupted component level to the same level as its complex header. This will only be done if the complex header’s level isn’t corrupted too. If it is then one of the other settings (“Automatically generate new level names prefixed with”, “Move all elements on undefined levels to the same level” or “Move all elements on undefined levels to the default level”) will be performed.

The error number reported is 415.

Linkage

“Repair Settings”, “Linkage” category

Add new line flag missing in a text element linkage that is part of a text node.

Normally there is a line feed between text strings in a text node. When the component text element of a text node doesn’t have its new line flag set, editing the text node will unexpectedly strip the line feeds.

When this repair option is turned on FileFixer will set the line feed flag in the text formatting linkage of a text node’s component text elements.

The search setting that detects this error is Settings | Change Settings | Search... | Linkage | New line flag is missing from a text element linkage in a text node.

This repair setting is off by default.

The error number reported is 544.

Delete duplicate text formatting linkage in a text node.

Normally line feeds are maintained between text strings when editing a text node. When more than one text formatting linkage exists in each of the text elements in a text node, and the line feed flag is turned off in one or more of those linkages, editing the text node will unexpectedly strip the line feeds from the text node.

FileFixer will delete the duplicate text formatting linkages and set the line feed flag in the one remaining text formatting linkage.

The search setting that detects this error is Settings | Change Settings | Search... | Linkage | Duplicate text formatting linkage in a text node.

This repair setting is off by default.

The error number reported is 545.

Remove siamese linkage.

A siamese linkage occurs when a linkage overflows into the next element. This can cause many problems, such as: elements that cannot be moved without MicroStation aborting or a file that cannot be plotted.

FileFixer will delete the siamese linkage.

The search setting that detects this error is Settings | Change Settings | Search... | Linkage | Siamese attribute linkage (linkage overlaying the next element).

This repair setting is off by default.

The error number reported is 764.

Clear “application required for element modification” flag in TriForma linkage.

Elements, created by TriForma, can be set to prevent MicroStation, when run without TriForma loaded, from allowing a user to modify them. This is done by setting the “application required for element modification” flag in the TriForma linkage.

Clearing this flag with FileFixer allows the element to be modified without TriForma present.

This repair setting is off by default.

The search setting that detects this error is Settings | Change Settings | Search... | Linkage | “Application required for element modification” flag in a TriForma linkage.

The error number reported is 235.

Models

“Repair Settings”, “Models” category.

Unlock models.

Unlock a locked model. After unlocking the model you will be able to add, modify and delete elements in that model.

The search setting that detects locked models is Settings | Change Settings | Search... | Models | Model is locked.

The error number reported is 250.

Range

“Repair Settings”, “Range” category.

Repair range of complex header elements.

Sets the range block of the complex header to be the union of the range blocks of the component elements.

The search setting that detects this error is Settings | Change Settings | Search... | Range | Complex header range doesn’t match components’ range.

The error numbers reported are 320 and 720. Error number 320 is generated when the range is off by more than the user specified tolerance, but within the tolerance –70% and 900%.

Repair range of displayable elements.

Use this repair setting to correct the range of displayable elements.

This repair setting also controls whether or not FileFixer repairs instances where the z-low or z-high range value is non-zero for an element in a 2D model.

The search setting that detects this error is Settings | Change Settings | Search... | Range | Range of graphic element is wrong.

The error numbers are 119, 169, 305, 307, 309, 312, 324, 325, 619, 704, 705, 707, 709, 712, 724, 725, and 912. Please refer to the search setting Settings | Change Settings | Search... | Range | Range of graphic element is wrong for more information on each of these error numbers.

Reference File

“Repair Settings”, “Reference File” category.

Delete missing reference file attachment.

Select this setting if you would like FileFixer to delete reference file attachments when the reference file cannot be found.

The error number is 343.

Display hidden reference files.

Select this setting if you would like FileFixer to make hidden reference file attachments displayable in MicroStation.

The search setting that detects this error is Settings | Change Settings | Search... | Reference File | Reference file is hidden.

The error number is 443.

Set duplicate slot number to an unused slot number

Use this option to set the duplicate slot number to one greater than the highest slot number currently being used by this model’s reference files.

The search setting that detects this error is Settings | Change Settings | Search... | Reference File | Duplicate reference file slot encountered.

The error number is 314.

Structured Storage

Each MicroStation V8 file is actually a compound file consisting of multiple internal directories and sub-files. This data organization scheme is also used in Microsoft Word documents and Excel spreadsheets.

“Repair Settings”, “Structured Storage” Category

Internal File Structure Damage

This section of the “Structured Storage” repair settings, gives you an option for repairing files that have severely damaged internal file structure. It also gives you an option for naming the repaired file. The following sections cover these options in detail.

Repair severely damaged internal file structure

When the internal file structure is corrupted the directories and sub-files cannot be accessed. When you try to open the file with MicroStation you will see an error such as the following:

Using this repair setting FileFixer reads through the corrupted design file to identify the start of all the sub-files. FileFixer determines which sub-files are readable (totally intact). Healthy sub-files are used to create a clean (healthy, empty) design file. Inaccessible sub-files are not copied to the new design file.

FileFixer renames severely damaged files by adding a “.” followed by a user-definable extension to the end of the file name. The extension is “corrupted” by default.

After all the available directories and sub-files have been copied into a clean V8 design file, the new file is given the original design file’s name. Then FileFixer continues processing this new design file.

Original file:

axiom.dgn

By default, original file is saved to:

axiom.dgn.corrupted

FileFixer then reconstructs axiom.dgn and repairs it.

The error number reported is 899.

Internal Compression Damage

This section of the “Structured Storage” repair settings contains one option for recovering complex elements, which is detailed in the following section.

Only recover a complex element when all components can be found.

Complex header elements, such as type 7s and type 12s, specify the number of component elements that are embedded within them. Use this repair setting to correctly set the number-of-components or to delete the complex element.

When recovering elements from a partially corrupted sub-file (stream) the whole complex element may not be recoverable. This repair setting gives you the option of either recovering part of the complex header or getting rid of it.

The error number reported is 322.

Internal Data Damage

The section of the “Structured Storage” repair settings gives you a number of options for recovering elements past missing or damaged data areas. It also gives you an option for rebuilding missing or damaged model header data. The following sections describe these options in detail.

Recover elements beyond missing or damaged graphical data.

Graphical data includes the visible geometry in your design.

The graphical data area is made up of one or more sub-files (streams). MicroStation cannot read sub-files after a missing or damaged sub-file. What FileFixer does to fix these problems is to put an empty sub-file in place of a missing or damaged sub-file.

MicroStation can then find and display the graphical elements in sub-files after a missing or damaged sub-file.

In the following illustration, sub-file 5 is missing. Elements stored in later sub-files are not displayed.

In the following illustration, sub-file 5 is damaged (unreadable). Elements stored in later sub-files are not displayed.

The error number for a damaged sub-file is 802. The search setting that detects this error is Settings | Change Settings | Search... | Structured Storage | Damaged graphical data.

The error number for a missing sub-file is 801. The search setting that detects this error is Settings | Change Settings | Search... | Structured Storage | Missing graphical data.

Recover elements beyond missing or damaged non-graphical data.

Non-graphical data includes reference file attachment elements and type 66 elements.

The non-graphical data area is made up of one or more sub-files (streams). MicroStation cannot read sub-files after a missing or damaged sub-file. What FileFixer does to fix these problems is to put an empty sub-file in place of a missing or damaged sub-file.

The error number for a damaged sub-file is 802. The search setting that detects this error is Settings | Change Settings | Search... | Structured Storage | Damaged non-graphical data.

The error number for a missing sub-file is 801. The search setting that detects this error is Settings | Change Settings | Search... | Structured Storage | Missing non-graphical data.

Recover elements beyond missing or damaged non-model data

Non-model data includes the design file header, view information, level tables and shared cell definitions in your design.

The non-model data area is made up of one or more sub-files (streams). MicroStation cannot read sub-files after a missing or damaged sub-file. What FileFixer does to fix these problems is to put an empty sub-file in place of a missing or damaged sub-file.

The error number for a damaged sub-file is 802. The search setting that detects this error is Settings | Change Settings | Search... | Structured Storage | Damaged non-model data.

The error number for a missing sub-file is 801. The search setting that detects this error is Settings | Change Settings | Search... | Structured Storage | Missing non-model data.

Rebuild missing or damaged model data.

Each V8 model (or cell) consists of

  • A model header (stores the model’s name, description, type and other model attributes).
  • Non-graphical elements (such as reference file attachments and type 66 elements).
  • Graphical elements (lines, circles, cells, etc.)

The model information (model’s name, description, type, etc.) for all models is also stored in the model index.

A missing or damaged model header makes that model and often the entire file unusable.

A damaged model index makes all models and often the entire file unusable.

If Design History is present in the design file, FileFixer restores model header data from Design History.

FileFixer can reconstruct a missing or damaged model header using information from the model index (which is stored elsewhere in a V8 file).

Model AttributeHandling
NameRestored by FileFixer.
DescriptionRestored by FileFixer.
Dimension Flag (2D/3D)Restored by FileFixer.
Type (Design, sheet, etc.)Restored by FileFixer.
“Can be placed as a cell” flagRestored by FileFixer.
Cell type (graphic or point)Restored by FileFixer only if “Can be
placed as a cell” setting was originally
ON. Otherwise, defaults to “Graphic”
(re-set to “Point” manually).
Working UnitsRestored by FileFixer if Design History
is available. Otherwise, working units
must be re-set manually — FileFixer’s
report reminds you to do this.

Due to the severity of this error, FileFixer terminates Search processing after the first instances of a damaged or missing model header is encountered.

FileFixer Repair processes all model headers.

A model index stream is rebuilt by using the information from all the model headers.

The error numbers reported are 801 (missing) or 802 (damaged).

Text

“Repair Settings”, “Text” category.

Correct the number of characters field in text element

Set the number of characters to the number of characters that actually exist.

The search setting that detects this error is Settings | Change Settings | Search... | Text | Text string overflows the element’s length.

The error number is 560.

Vertices

Repair Settings | Vertices dialog box

Fix line string’s vertex which is off the edge of the design plane by

One of the string’s vertices is off the edge of the design plane.

The vertex can either be adjusted or the element can be deleted. To adjust the corrupted vertex the vertices on both sides of it must be on the design plane (otherwise, the vertex cannot be adjusted).

The search setting that detects this problem is Settings | Change Settings | Search... | Vertices | Line string’s vertex is off the design plane.

The error number reported is 373.

Set number of vertices to maximum allowed

The number of vertices property of an element is greater than the maximum allowed of 5000. This option adjusts the value to the maximum allowed.The search setting that detects this problem is Settings | Change Settings | Search... | Vertices | Too many vertices on line string, shape, curve, etc.

The error number reported is 787.