Issue:
A Worx plugin has reported an error, or the log shows an Error# number, and you need to know what it means and what to do about it.
Every Worx plugin (ANNOWorx, ATTEWorx, BUBBLEWorx, Diagrams, ELECTROWorx, ISOWorx, LINKWorx, MTOWorx, VIEWWorx and the shared engine underneath them) reports problems with a numbered error. This article lists every error number the software can raise, what it means, and what to try.
Causes:
Worx errors are numbered by the area that failed, not by a single root cause. The same number can be raised from several places, so the specific cause is given by the message recorded alongside the number in the log. The most common underlying causes are:
- A file, folder or network path named in the plugin Settings no longer resolves — moved, renamed, offline, or permission-denied.
- A drawing or Xref containing a damaged object, or an object on a locked layer.
- A database or SOCKETWorx connection that is unreachable, misconfigured, or missing credentials.
- A required setting left blank — user information, server address, spec or catalog location.
- A command interrupted part-way through, leaving the session in an odd state.
- A stale plugin build, or a licence that has not been activated for the feature in use.
Solution:
How to read a Worx error
The on-screen notification shows a short title and a description. The error number is written to the log file in this form:
Error#8001: MTOWorx-Failed To Gather Line Numbers Please retry.
Viewing the log
Open the Worx log viewer — it always shows the current log file:
- In a browser, go to http://localhost:1968/worxlogs. This is served by the Worx service on your own machine, so it works offline and nothing leaves your network.
- In AutoCAD, BricsCAD or Plant 3D, type
ECESHOWLOGFILEat the command line and the same page opens in a tab inside CAD. - In ATTEWorx or the Worx Project Manager, use the Log File button.
Then search the page for Error#, or for the text of the message you saw. The log entry also carries the full technical detail — that is the part support needs.
The log usually tells you more than the pop-up did. The same number is reused in many places, so the log line names the specific situation. For example, error 20045 is generically "the argument is null", but in the log it reads:
WorxException: Error#20045: User Information Missing-User information is empty. Please fill out the User Information found on the Licensing Palette tab.
That is a five-second fix, and only the log said so. Each entry in the tables below lists the specific messages known to be reported under that number, so it is worth finding your exact wording.
About the scrambled method names. Under the message the log prints the code path, with names like
U1EPt3GEfs(n1m4FazBoedtHJmCfU ). That is expected — released Worx code is obfuscated. You do not need to make sense of it; just include it when you contact us.
Error#-1 — "Unspecified error has occurred" means the software raised an error number it could not look up. There is no specific guidance for it; go straight to What to send ECE Design support below.
Try these five things first
These resolve the large majority of Worx errors, whatever the number:
- Press Esc twice, run REGEN, and try again. Many errors are the after-effect of a cancelled command.
- Back up the drawing, then run AUDIT on it and on every attached Xref, with Fix errors set to Yes.
- Check that every path in the plugin's Settings still resolves — symbol libraries, templates, output folders and project folders on network drives are the most common culprit.
- Restart the CAD session. Palette, dialog and theme errors are usually a stale session.
- Install the current Worx Plugins release. If the message mentions licensing or an evaluation limit, check the License tab of the palette.
What the number tells you
The first digits identify the area that failed:
| Range | Area |
|---|---|
| 1000–1999 | ANNOWorx |
| 2000–2999 | BUBBLEWorx |
| 3000–3999 | Diagrams (P&ID) |
| 6000–6999 | ISOWorx |
| 7000–7999 | LINKWorx |
| 8000–8999 | MTOWorx |
| 10000–10999 | SHEETWorx |
| 12000–12999 | VIEWWorx |
| 14000–14999 | Database (all plugins) |
| 20000–20999 | General / shared engine (all plugins) |
| 30000–30499 | DBWorx |
| 30500–30999 | ATTEWorx / ODA drawing engine |
| 40000–40999 | Developer |
| 41000–41999 | CAD / Plant 3D integration (all plugins) |
Ranges are reserved for products that do not currently raise numbered errors (4000–4999 DIMWorx, 5000–5999 INSTALLWorx, 9000–9999 RIBBONWorx, 11000–11999 STRESSWorx). ELECTROWorx reports through the General, Database and CAD ranges.
Suggested actions, referenced from the tables
Each row in the tables below points to one or more of these. Work through them in the order given.
| Ref | Action | How |
|---|---|---|
| A | Retry cleanly | Press Esc twice, run REGEN, then repeat the action. A surprising number of these are one-off states left behind by a cancelled command. |
| B | Audit the drawing and its Xrefs | Back up the DWG first, then run AUDIT (Fix errors = Yes) on the drawing and every attached Xref. Do this on a copy for CADWorx drawings, since AUDIT can occasionally alter CADWorx objects. |
| C | Check the file or folder | Confirm the path still exists, that you can reach it (VPN / mapped drive / network share), that the file is not read-only, and that nobody else has it open. Prefer a UNC path over a mapped letter for shared locations. |
| D | Check the Worx settings and support files | Open the plugin's Settings and confirm the configured locations (symbol library, configuration file, template, project folder, output folder) still point at files that exist and that you can write to. |
| E | Check the database connection | Re-test the connection in the plugin's database setup screen: server reachable, correct database/schema selected, credentials valid, and your Windows/SQL account has read and write rights to the tables. |
| F | Unlock the drawing objects | Unlock/thaw the layer the object is on, unlock the viewport, and make sure the object is not inside a locked or externally referenced block, then retry. |
| G | Save first | Save the drawing (and close/reopen the project if you were prompted to), then run the command again. Several Worx operations need a saved file on disk. |
| H | Restart the CAD session | Close AutoCAD / BricsCAD / Plant 3D completely and reopen. Palette, theme, form and module errors are usually a stale session, not bad data. |
| I | Update to the current Worx build | Install the latest Worx Plugins release. If the error mentions licensing or an evaluation limit, verify your license in the License tab of the palette. |
| J | Send it to support | Send us the error number, the log file, and (if possible) the drawing or project. See What to send ECE Design support at the end of this article. |
| K | Check the Plant 3D / CADWorx spec and catalog | Confirm the component's specification and catalog are the ones the project expects, that the spec file is reachable, and that the part exists in the spec at the size you are using. |
ANNOWorx — 1000 to 1999
Tag and label creation, and syncing labels back to the model.
| Error | What it means | What to do |
|---|---|---|
| 1000 | Annotation failed. Failed to annotate a line number. | Try A, J. |
| 1001 | Annotation failed. Failed to annotate a line elevation. | Try A, J. |
| 1002 | Annotation failed. Failed to annotate a piece of equipment. | Try A, J. |
| 1003 | Annotation failed. Failed to annotate a nozzle. | Try A, J. |
| 1004 | Annotation failed. Failed to annotate a component. | Try A, J. |
| 1005 | Annotation failed. Failed to annotate a steel component. | Try A, J. |
| 1006 | Syncing failed. Failed to sync annotations. | Try A, J. |
BUBBLEWorx — 2000 to 2999
Material mark bubbles, MLeaders and BOM tables.
| Error | What it means | What to do |
|---|---|---|
| 2000 | Failed To Auto Tag Bubble. Failed to Bubble Components with Tag in Full Auto. Specific messages reported under this number: • Failed during Semi Auto MML | Try A, J. |
| 2001 | Failed To Single Tag Bubble. Failed to Bubble Components with Tag in Single Mode. Specific messages reported under this number: • Failed To Bubble Single - Tagging. | Try A, J. |
| 2002 | Failed To Semi Auto Tag Bubble. Failed to Bubble Components with Tag in Semi Auto. | Try A, J. |
| 2003 | Failed To Replace Object Connected To Bubble. | Try A, J. |
| 2004 | Invalid ViewPort. Specific messages reported under this number: • Circular Viewports are not allowed at this time. Please contact support for additional information. • Front and back clip planes coincide; nothing to extrude. • Perspective viewports are not supported. • Viewport is off. | Try F, A, J. |
| 2005 | Failed To Flush Graphics. | Try H, A, J. |
| 2006 | Failed To Change Tag Bubble Style. The system was unable to change the bubble style. | Try A, J. |
| 2007 | Failed To Load Tag Bubble Style. The system was unable to load the bubble style. Specific messages reported under this number: • Please select a Bubble Style using the Combo Listbox in the palette. Ensure a Valid Image is displayed before proceeding. | Try A, J. |
| 2008 | Failed To Simulate Clash Area. The system was unable to simulate the area to be Bubbled. | Try A, J. |
| 2009 | Failed To Collect All Entities. An error occurred while collecting all the entities. Please Audit the drawing and all XRefs as this usually indicates a corrupt object. Specific messages reported under this number: • Failed To Collect all items in entity collection routine. BUBBLEWorx encountered an error in a component, indicating an audit is required. Please audit this model and xrefed models • Failed to collect Steel entities • Failed to collect Pipe entities | Try B, A, J. |
| 2010 | Failed To Switch To Model Space. The system was unable to switch to model space. | Try A, J. |
| 2011 | Failed To Get Bubble Object Id. | Try A, J. |
| 2012 | Failed To Get List Of Bubbles. An error occurred while collecting a list of the existing bubbles. | Try A, J. |
| 2013 | Failed To Load MLeader Styles. An error occurred while loading the mleader styles. | Try A, J. |
| 2014 | Failed To Get Isogen Supplemental Attribute Information. An error occurred while getting Isogen Supplemental Information. | Try H, A, J. |
| 2015 | Failed To Get MLeader Landing Point. An error occurred while getting MLeader Landing Point. | Try A, J. |
| 2016 | Failed To Get MLeader Stack Point. An error occurred while getting MLeader Stack Point. | Try A, J. |
| 2017 | Failed To Get MLeader. An error occurred while getting MLeader. Specific messages reported under this number: • Failed to create MLeader by Jig. | Try A, J. |
| 2018 | Failed To Set MLeader Scale. An error occurred while setting the MLeader scale. | Try D, A, J. |
| 2019 | Failed To Set MLeader Layer. An error occurred while setting the MLeader layer. | Try D, A, J. |
| 2020 | Failed To Place MLeader. An error occurred while placing the MLeader in space. Specific messages reported under this number: • Invalid MTextAttribute detected for AttributeReference:….… Attribute must be a Multiple Line Attribute. • Failed during BOM Auto Tagging • Failed during MML Auto Tagging • Failed to annotate BOM item • Failed to annotate MML item • Failed during Auto Tagging • …and 1 more variations. | Try A, J. |
| 2021 | Failed To Sync Bubbles. Failed to sync the bubbles. | Try A, J. |
| 2701 | Failed To Get Component Length. Failed to get the component length. Specific messages reported under this number: • Failed to get component length • Failed to get elbow length | Try A, J. |
| 2702 | Failed Bom Bubbling Process. Failed the process. Check the underlying error. | Try A, J. |
| 2703 | Failed In Add M Leader Process. Failed M Leader Insertion. Please check the log file for more information. Specific messages reported under this number: • Failed to add leader | Try C, H, A, J. |
| 2704 | Invalid Part Family Long Description. Please contact support. | Try K, A, J. |
Diagrams (P&ID) — 3000 to 3999
P&ID symbol library, project file, line breaking, data tables and connections.
| Error | What it means | What to do |
|---|---|---|
| 3000 | Section Name not found in the library file. Specific messages reported under this number: • The section … cannot be found in the symbol library! | Please check the symbol library file integrity. Then try C, A, J. |
| 3001 | Failed To Get Section Name. Failed to get the section name from the configuration file. | Please check the configuration file integrity. Then try D, C, A, J. |
| 3002 | Element not found in the library file. Specific messages reported under this number: • The group is missing its element data. | Please check the symbol library file integrity. Then try C, A, J. |
| 3003 | Failed to Get Element. Failed to get the element from symbol library file section. Specific messages reported under this number: • Could not find any lines in the currently loaded project symbol library! • Line with name … cannot be found in the symbol library. • Could not find any routes in the current project! • Could not find any lines in the current project! • Failed to get route names from symbol library • Element Name: …. | Please check the symbol library file integrity. Then try D, C, A, J. |
| 3004 | Invalid LayerId. The LayerId is invalid. | Please check the configuration file integrity. Then try A, J. |
| 3005 | Failed to Get Layer. Failed to get the layer from configuration file layer area. | Please check the configuration file integrity. Then try D, C, A, J. |
| 3006 | Layer not found in the layer Area of the configuration file. | Please check the configuration file integrity. Then try D, C, A, J. |
| 3007 | Failed to Get Linetype. Failed to get the linetype from configuration file. | Please check the configuration file integrity. Then try D, C, A, J. |
| 3008 | Invalid Linetype. The linetype name is invalid. | Verify the linetype name in the settings. Then try A, J. |
| 3009 | Linetype Not Found. The linetype was not found in the specified location. | Verify that the location exists. Then try K, A, J. |
| 3010 | Failed To Process Line For Breaking. There was a failure while trying to break the line. Specific messages reported under this number: • A connector's insertion point must be inserted at the end of a route! Please check your connector symbol setup for accuracy or use another connector. • Unable to determine block and polyline intersection point! • A connector must be inserted at the end of a route! • Polyline end is already connected at connector 1! • Polyline end is already connected at connector 2! • Unable to determine how to break the polyline. • …and 4 more variations. | Try A, J. |
| 3011 | Failed To Process Line For Mending. There was a failure while trying to mend the line. | Try H, A, J. |
| 3012 | Failed To Collect Lines. There was a failure while trying to collect the P&ID lines in the drawing. Specific messages reported under this number: • Failed to determine if picked point lies on an existing line. • Not enough lines at the clicked point. | Try A, J. |
| 3013 | Failed To Break Lines. There was a failure while trying to break the P&ID lines. Specific messages reported under this number: • This component does not support inserting at the end of a line. Try using an insertion type that does support this operation. • Resulting line smaller than gap size. | Try A, J. |
| 3014 | Failed To Mend Lines. There was a failure while trying to mend the P&ID lines. | Try A, J. |
| 3015 | Failed To Determine Closest Line. There was a failure while trying to find the closest P&ID line. Specific messages reported under this number: • Picked point was determined to be on existing route but was unable to determine polyline or point. • Incorrect route count at picked point or picked location was incorrect. • Incorrect number of lines at selected point. • Picked routes must share a common point. • Incorrect route count at picked point. • Picked routes are not perpendicular. • …and 2 more variations. | Try A, J. |
| 3016 | Failed To Load Configuration File. Failed to load the configuration file. Specific messages reported under this number: • The configuration file cannot be null. | Please check the configuration file integrity. Then try D, C, A, J. |
| 3017 | Failed To Load Symbol Library File. Failed to load the Symbol Library File. Specific messages reported under this number: • The Symbol File Path is blank in the Project File: …. • The symbol file cannot be null. | Please check the Symbol Library File integrity. Then try D, C, A, J. |
| 3018 | Invalid Block Element. The element is not for a block. Specific messages reported under this number: • Not a valid name for the insertion type. • Legacy type cannot be null or empty. • Unknown insert type found: … • Missing Vessel Head Type • Missing Tank Roof Type | Please check the configuration file integrity. Then try A, J. |
| 3019 | Invalid Connector. The connector is invalid!. Specific messages reported under this number: • Failed to match the symbol connection points with the route connection points. The symbol insertion point must be inserted on the line, not adjacent to it. • Insert Connection: The From Id […] on the connection […] already exists in the connection table in the From Id column […]. • Insert Connection: The From Id […] on the connection […] already exists in the connection table in the To Id column […]. • Insert Connection: The To Id […] on the connection […] already exists in the connection table in the From Id column […]. • Insert Connection: The To Id […] on the connection […] already exists in the connection table in the To Id column […]. • Unable to update the new route information on a connected item. Has the route been moved or trimmed? It might need to be redrawn. • …and 12 more variations. | Try A, J. |
| 3020 | Failed To Get Line Break Priority. Failed to get the line break priority from the configuration file. Specific messages reported under this number: • The line break priority is missing from the element. | Please check the symbol library file integrity. Then try D, C, A, J. |
| 3021 | The symbol library file does not exist at the location provided. Specific messages reported under this number: • Filepath: … | Please check the file exists at the location and you have read/write access. Then try D, C, A, J. |
| 3022 | Configuration File Does Not Exist. The configuration library file does not exist at the location provided. Specific messages reported under this number: • Filepath: … | Please check the file exists at the location and you have read/write access. Then try D, C, A, J. |
| 3023 | The project directory does not exist in that location. Specific messages reported under this number: • Project Directory: … | Verify that the directory exists and you have access to it and try again. Then try C, A, J. |
| 3024 | Invalid Process Startup Variable. Cannot read the startup variable from the cfg file. | Verify the integrity of the selected cfg file. Then try D, C, A, J. |
| 3025 | Invalid Symbol Variable. Cannot read the symbol command from the dat file. | Verify the integrity of the selected dat file. Then try D, C, A, J. |
| 3026 | Failed To Handle Project Location Change!. The project location may not have been changed. | Please refresh the listing and/or check the log file. Then try A, J. |
| 3027 | Failed To Populate The Project Drawings Listing!. The project drawing listing was not refreshed. | Please refresh the listing and/or check the log file. Then try A, J. |
| 3028 | Failed To Determine Block Rotation. Failed to determine the block rotation angle. Specific messages reported under this number: • Takeoff 1 is not 90 degrees from main line. • Takeoff 2 is not 90 degrees from main line. | Verify that the block is built correctly and is attached to a line. Then try A, J. |
| 3029 | Failed To Modify Setting. An error occurred while trying to modify the settings. | Try D, A, J. |
| 3030 | Failed To Save Setting. An error occurred while trying to save the settings. Specific messages reported under this number: • Failed To Save Layer Settings • Layer Validation Failed. | Try D, A, J. |
| 3031 | Failed To Add New Layer. An error occurred while trying to add the layer to the window. | Reload the dialog to try the operation again, check the log file and if the problem persists contact support. Then try D, H, A, J. |
| 3032 | Failed To Locate Diagrams Xml. The Diagrams.Xml file path no longer appears valid. Specific messages reported under this number: • Failed To Add Project Drawings as diagrams.xml file was not found in the project folder: … • Cannot obtain the project file name from the project folder! • Please select the Diagrams.xml Project File. | Please check windows explorer, check the log file and if the problem persists contact support. Then try D, C, A, J. |
| 3033 | Failed To Create Diagrams Directory. The Diagrams directory was not created successfully. | Try C, A, J. |
| 3034 | Failed To Locate Diagrams LineType File. The Diagrams Line Type File (diagrams.lin) file should be located in the Symbol Library Directory with the Symbol.Xml but could not be found. | Set the Symbol Library Location and/or copy the default diagrams.lin file is located in %programdata%\ECE Design\Diagrams\Support. Check the log file. Then try D, C, A, J. |
| 3035 | Failed To Load Layers. An unexpected error occurred while loading the layers. Specific messages reported under this number: • Failed to load linetypes — Could not parse diagrams.lin Check the file format and path | Please check the log file and contact support if the issue can not be resolved. Then try A, J. |
| 3036 | Failed To Locate Configuration File. The configuration file in the Diagrams Project File is inaccessible. Network drive share error? Specific messages reported under this number: • Please select a valid configuration.xml file only | Please check network connections and access to the configuration file in question. Please contact support if the issue can not be resolved. Then try D, E, C, J. |
| 3037 | Failed To Load Diagrams Project Xml File. An error occurred while trying to load the project file. | Please check the log file and contact support if necessary. Then try C, A, J. |
| 3038 | Failed To Create the Diagrams Project Xml File. An error occurred while trying to create the project file. | Please check the log file and contact support if necessary. Then try C, A, J. |
| 3039 | Diagrams Project Xml Drawing Check Failed. An error occurred while trying to check if the drawing was in the project. | Please check the log file and contact support if necessary. Then try A, J. |
| 3040 | Failed Permission To Create Or Modify Project. Read/Write permission to both the selected (and previous) configuration.xml File(s) is required. | Please check the log file and contact support if necessary. Then try D, C, A, J. |
| 3041 | Failed To Save The Project File. An unexpected error occurred while trying to save the project. Specific messages reported under this number: • Project file opened in Read Only Mode. | Please check the log file and contact support if necessary. Then try C, A, J. |
| 3042 | Failed To Load The Project File. An unexpected error occurred while trying to load the Project. Specific messages reported under this number: • The active project is not set or it does not contain any sections. • You must have a current project to reload first! | Please check the log file and contact support if necessary. Then try C, A, J. |
| 3043 | Match Command Error. An error occurred during the Match Command. | Please check the log file and contact support if necessary. Then try A, J. |
| 3044 | Failed To Add Drawing To Diagrams Project Xml. An error occurred during add. | Please check the log file and contact support if necessary. Then try A, J. |
| 3045 | Failed To Load Existing Diagrams Project Xml for editing. An error occurred during add. Specific messages reported under this number: • You must first open a project! | Please check the log file and contact support if necessary. Then try A, J. |
| 3046 | Failed To Load Recent Projects. An error occurred while loading the recent projects from the Application Settings. | Please check the log file and contact support if necessary. Then try D, A, J. |
| 3047 | Failed To Add To Recent Projects. An error occurred while adding the opened project to the recent projects list. | Please check the log file and contact support if necessary. Then try A, J. |
| 3048 | Failed To Remove Recent Project. An error occurred while removing the recent project entry. | Please check the log file and contact support if necessary. Then try A, J. |
| 3049 | Failed To Find Existing Table By Id. An unexpected error occurred. | Please reload the dialog and contact support if necessary. Then try A, J. |
| 3050 | Failed To Load Project Settings Form. An unexpected error occurred. Please check log file. Corrupt Configuration? | Please try to reload the dialog and contact support if necessary. Then try D, C, B, J. |
| 3051 | Failed To Save The Configuration File. An unexpected error occurred while trying to save the configuration file. Specific messages reported under this number: • Configuration file opened in Read Only Mode. | Please try to save again and contact support if necessary. Then try D, C, A, J. |
| 3052 | Failed To Initialize Fields Grid. An unexpected error occurred while trying to initialize the fields. Please check log file. | Please try again and contact support if necessary. Then try C, H, A, J. |
| 3053 | Failed To Change Tables And Load The Fields Grid. An unexpected error occurred while trying to load the fields. Please check log file. | Please try again and contact support if necessary. Then try C, H, A, J. |
| 3054 | Failed To Load Tables From Configuration File. An unexpected error occurred while trying to load the tables in the configuration file. Please check log file. | Please try again and contact support if necessary. Then try D, C, A, J. |
| 3055 | Failed To Copy Default Configuration. An unexpected error occurred while trying to copy the default configuration file to the new location. | Please check the default configuration file location and make sure it exists. Then try D, C, A, J. |
| 3056 | Duplicate Section Names Prohibited. Please use a different section name as this name is already in use. | Try A, J. |
| 3057 | Failed to Save the Symbols File. An unexpected error occurred while trying to save the symbols library. Specific messages reported under this number: • Library file opened in Read Only Mode. | Please try to save again and contact support if necessary. Then try C, A, J. |
| 3058 | Reached New Section Limit. Please rename one of the new sections before adding another. Specific messages reported under this number: • Rename some of the Sections to add more sections | Try A, J. |
| 3059 | Reached New Insert Routine Limit. Please rename one of the new insert routines before adding another. Specific messages reported under this number: • Rename some of the Insert Routines to add more Insert Routines | Try A, J. |
| 3060 | Symbol Sections Must Contain At Least One Element. Please add an element. | Try A, J. |
| 3061 | Failed To Save Data To Entity. Failed to save the data to the entity. Specific messages reported under this number: • Failed to update the data on the entity. UniqueID: … • Failed to update the data on the entity. UniqueID… • Unknown error creating data for newly created route. • Failed to deserialize data to the entity. • Failed to serialize data to the entity. | Try A, J. |
| 3062 | Failed To Load Data From Entity. Failed to load the data from the entity. Specific messages reported under this number: • The diagrams entity is not a line or a symbol. If you selected a group use a tag/label instead. • Unable to get the route data from the line. Drawging: … • Unable to get the component data from the object. • Failed to get the fields from the entity data • Unable to get the route data from the line. | Try A, J. |
| 3063 | Failed To Get Table. Failed to get the table from the configuration file. Specific messages reported under this number: • The group Table Name and Table ID were not found in the current configuration. ID: …; Name: … • The route Table Name and Table ID were not found in the current configuration. ID: …; Name: … • The item Table Name and Table ID were not found in the current configuration. ID: …; Name: … • Table Id […] and Table Name […] is missing form the current configuration file. • The table name and the table id were not found in the current configuration file. • Concatenation not saved. The … not found in the configuration file. • …and 17 more variations. | Try D, C, A, J. |
| 3064 | Failed To Get View From Table. Failed to get the view from the table in the configuration file. Specific messages reported under this number: • The View is no longer valid. Please reload list • Current Table Views is null. • Unable to locate view | Try D, C, A, J. |
| 3065 | Failed To Remove Field. Failed To Remove the Field. Specific messages reported under this number: • Field is used in a concatenation and must be removed from the concatenation first. | Try A, J. |
| 3066 | Failed To Insert Field. Failed To Insert the Field. Specific messages reported under this number: • Failed to insert the […] table fields to the Diagrams database | Try A, J. |
| 3067 | Failed To Move Field. Failed To Move The Field. | Try A, J. |
| 3068 | Failed To Edit Views. Failed to edit the views. | Try A, J. |
| 3069 | Failed To Reload View. Failed to reload the view. Specific messages reported under this number: • Failed to find the selected view. • No Fields Exist In View. | Try A, J. |
| 3070 | Failed To Add View. Failed to add the view. Specific messages reported under this number: • Failed to create a tooltip view for Table; ID […], Name […] • Failed To Add System Views | Try A, J. |
| 3071 | Failed To Remove View. Failed to remove the view. Specific messages reported under this number: • …: You cannot remove a system view. | Try A, J. |
| 3072 | Failed To Copy View. Failed to copy the view. | Try A, J. |
| 3073 | Failed to Rename View. Failed to rename the view. Specific messages reported under this number: • …: You cannot rename a system view. | Try A, J. |
| 3074 | Failed to Save View. Failed to save the view. | Try A, J. |
| 3075 | Failed To Get Fields From View. Failed to get the Fields assigned to the view. Specific messages reported under this number: • No Views Available. Please add a view. • Unable to locate view | Try A, J. |
| 3076 | Unknown Field Type found. | Try A, J. |
| 3078 | Cannot Write To Default Project. Cannot write to the default project. | You cannot save a drawing to the default project. Then try A, J. |
| 3079 | Failed To Get Concatenation. Failed to get the concatenation from the configuration file. Specific messages reported under this number: • The field is of type concatenation, but the concatenation does not exist in the configuration file. | Try D, C, A, J. |
| 3080 | Failed To Get Field. Failed to get the field from the table. Specific messages reported under this number: • The annotation field was not found in the picked table field list. Was it deleted? Table Name: …; Field Id: … • The annotation field was not found in the picked table field list. Was it deleted? Table Name: …; Field Id… • The Primary Route Field was missing from the symbol. BlockName …; Position: … • Required Field: Drawing Name is missing from the route with Unique Id […] • The annotation field […] was not found in the current configuration file. • The SYS_PRIMARYROUTEID field is missing from the entity. UniqueId: … • …and 16 more variations. | Try A, J. |
| 3081 | Button Creation Failed. Failed to create palette button. | Try H, A, J. |
| 3082 | Failed Settings Retrieval. Failed to retrieve palette settings. | Try D, H, A, J. |
| 3083 | Button ReSize Failed. Failed to resize the buttons. | Try H, A, J. |
| 3084 | Tool Palette Creation Failed. Failed to create the tool palettes from the symbol library. | Please check the symbol library file integrity and that the Images sub-directory exists in your Support directory. Then try D, H, A, J. |
| 3085 | Missing Table Name. The table name is missing from the component in the Symbol Library. Specific messages reported under this number: • Table name […] found on element but missing in database configuration. • Annotation must have a valid table name. | Please add the table name and/or set to None if it does not exist. Then try D, A, J. |
| 3086 | Missing Scale Element. The Scale is missing from the component in the Symbol Library. | Please add the scale and/or set it to 1 if there is no scaling. Then try D, A, J. |
| 3087 | Missing BreakDistance1. The BreakDistance1 value is missing from the element. | Please add the BreakDistance1 to the element. Then try A, J. |
| 3088 | Missing BreakDistance2. The BreakDistance2 value is missing from the element. | Please add the BreakDistance2 to the element. Then try A, J. |
| 3089 | Missing BreakDistance3. The BreakDistance3 value is missing from the element. | Please add the BreakDistance3 to the element. Then try A, J. |
| 3090 | Missing BreakDistance4. The BreakDistance4 value is missing from the element. | Please add the BreakDistance4 to the element. Then try A, J. |
| 3091 | Invalid Element Value. The element has an incorrect value. | Please modify the value. Then try A, J. |
| 3092 | Entity Not A Line. The Entity is not a line. | Try again and if the error persists contact support. Then try A, J. |
| 3093 | Missing Primary Line Data. The entity is missing the primary line reference. Specific messages reported under this number: • Main Line Dictionary not found in drawing. • The Data Dictionary does not exists. • The Data Xrecord does not exist | Try A, J. |
| 3094 | Missing Auxiliary Line Data. The entity is missing the auxiliary line reference. | Try A, J. |
| 3095 | Missing Element Line Data. The entity is missing the element line reference. | Try A, J. |
| 3096 | Duplicate Primary Data. The Primary Data ID is a duplicate of of another line. Specific messages reported under this number: • Duplicate Unique Id found on Symbol. • Duplicate Unique Id found on Route. | Try A, J. |
| 3097 | Existing Auxiliary Data. The line already has Auxiliary Data attached. | Try A, J. |
| 3098 | Primary Data Mismatch. The Primary Data does not match. Specific messages reported under this number: • Selected routes and symbols do not belong to the same primary route! • Entity Table Id and MLeader Table Id do not match! • Line Table Id and MLeader Table Id do not match! • Line Table Id and DBText Table Id do not match! | Try A, J. |
| 3099 | Auxiliary Data Mismatch. The Auxiliary Data does not match. | Try A, J. |
| 3100 | Missing Field Name. The field name is missing from the table. Specific messages reported under this number: • The Drawing Name system field is missing from the connecter. • Annotation must have a valid field name. | Check the configuration file or proper setup. Then try A, J. |
| 3101 | Failed To Update Concatenation. Failed to update the concatenation. | Try A, J. |
| 3102 | The Symbol Library path is empty. | Please check the configuration file and verify that the symbol library path has a value. Then try D, C, A, J. |
| 3103 | Failed to find image file. Specific messages reported under this number: • Failed To Set The Image • Failed To Get Image | Please check that you have an Images sub-directory in your Support directory. Then try C, A, J. |
| 3104 | Duplicate Ribbon Group Names Prohibited. Please use a different Ribbon Group name as this name is already in use. Specific messages reported under this number: • The Group Name already exists! | Try H, A, J. |
| 3105 | Failed To Find Diagrams.lin File. Diagrams.lin file was not found in the .Support Folder. Specific messages reported under this number: • Failed to find Diagrams.lin file: … | Please ensure you have a Diagrams.lin file in your .Support folder. Then try D, C, A, J. |
| 3106 | Block Data Mismatch. Block Data cannot be added. Specific messages reported under this number: • Item is being removed that is marked as neither DbObject or BlockReference • Block […] no longer exists in …. | Try A, J. |
| 3107 | Failed To Get Drawings From Database. Unable to get the project drawing list from the database. Specific messages reported under this number: • An error occurred while fetching data from the database. | Try E, A, J. |
| 3108 | Missing Direction. The Direction property is missing from the element. Specific messages reported under this number: • Missing stored connector direction information on the connector entity. Please delete the connector and reinsert it. | Please add the Direction to the element. Then try A, J. |
| 3109 | Table Configuration Error. Failed To Update Table System Fields. | Try D, A, J. |
| 3110 | Table Configuration Error. Failed To Load Table Fields. | Please add the Direction to the element. Then try D, A, J. |
| 3111 | Settings General Error. Failed To Switch Sections General Failure. | Try D, A, J. |
| 3112 | Data Error. Failed To Add Default Data. | Try A, J. |
| 3113 | Data Error. Failed To Display Entity Properties. Specific messages reported under this number: • No Views Exist | Try A, J. |
| 3114 | Missing Unique Guid. The guid is missing from the object. | Try A, J. |
| 3116 | Failed To Delete Line. Failed to delete the line. Specific messages reported under this number: • Unknown failure during the erase polyline process. • Unique Guid not found in item table. • Failure of the erase line process. | Try A, J. |
| 3117 | Failed To Process Erased Entities. Failure during the erase entities process. Specific messages reported under this number: • Unknown failure during the erase entities process. | Try B, A, J. |
| 3118 | Failed To Get Drawing From Database. The drawing was not found in the database. | Try E, A, J. |
| 3119 | Form Error. Failed To Get Data Editor. Specific messages reported under this number: • The data manager of the entity does not exist | Try H, A, J. |
| 3120 | Failed To Create Concatenation Type Editor. | Try H, A, J. |
| 3121 | Failed To Create Concatenation Type Editor. | Try H, A, J. |
| 3122 | Failed To Create Date Type Editor. | Try H, A, J. |
| 3123 | Failed To Create Currency Type Editor. | Try H, A, J. |
| 3124 | Failed To Create Double Type Editor. | Try H, A, J. |
| 3125 | Failed To Create Int Type Editor. | Try H, A, J. |
| 3126 | Failed To Create Boolean Type Editor. | Try H, A, J. |
| 3127 | Failed To Create Decimal Type Editor. | Try H, A, J. |
| 3128 | Linked Items. Failed To Update Linked Entities. | Try A, J. |
| 3129 | Edit Form. Failed To Show Hidden Attributes. | Try H, A, J. |
| 3130 | Edit Form. Failed To Clear Data. Specific messages reported under this number: • Unable to automatically remove the orphan data. CommonDataId: … | Try H, A, J. |
| 3131 | Edit Form. Failed To Add Data Editor. | Try H, A, J. |
| 3132 | Edit Form. Failed To Add Data Label. | Try H, A, J. |
| 3133 | Edit Form. Failed to display the data. Specific messages reported under this number: • Failure in Show/Hide Hidden Attributes - Unable To Display Data • Failed to populate the table and field dropdowns for tracing. • All lines numbers have been used or all route data is empty. • Failed to populate field dropdowns for tracing. • Unable to deserialize the treeview. • Failed To Display Data | Try H, A, J. |
| 3134 | Edit Form. View Contains Field That No Longer Exists. Specific messages reported under this number: • View Name: ToolTips; TableName: …; FieldId: … • ViewName: …; TableName: …; FieldId: … | Please open the view and re-save. Please check the log file for more information. Then try H, A, J. |
| 3135 | Edit Form. Failed To Get Value From Data Manager. | Try H, A, J. |
| 3136 | Configuration Save. Failed Layer Validation. | Try D, A, J. |
| 3137 | Failed To Select Layer Color. | Try A, J. |
| 3138 | Failed To Edit Tables. | Try A, J. |
| 3139 | Failed To Delete System Table. Deletion of Systems Tables is prohibited. Specific messages reported under this number: • Unable to remove system table. | Try A, J. |
| 3140 | Table Name Exists. Please enter a new table name as the one entered already exists. Specific messages reported under this number: • The table name already exists! | Try A, J. |
| 3141 | Invalid Table Id. Specific messages reported under this number: • Failed To Find Table in Configuration File! • Table Not Found! Unable to load fields • Please reload the configuration file • Failed to add table: … • Failed To Locate Table | Try A, J. |
| 3142 | Failed To Add Table. Specific messages reported under this number: • Failed to add the […] table to the Diagrams database • Failed To Add System Tables | Try A, J. |
| 3143 | Failed To Update Table. | Try A, J. |
| 3144 | Failed To Get Image From Resources. | Try A, J. |
| 3145 | Failed To Get Connection. Failed to get the connection from the database. Specific messages reported under this number: • The connector does not exist in the … table or multiple connections with the connector id exist! Id: … • Connector with Id … is in the connector table but missing in the item table. • The selected connector does not exist in the Connections table of the database. • The connector does not exist in the connections table. ConnectorId …. • Multiple connections in database for connector with ID: …. • Failed to find the connection […]in the item table • …and 4 more variations. | Try E, A, J. |
| 3146 | Failed To Initialize Grid. The grid failed to initialize correctly. Specific messages reported under this number: • There was an error initializing the Edit Connections Grid. | Try H, A, J. |
| 3147 | Failed To Initialize Filter. The grid filter failed to initialize. Specific messages reported under this number: • The column selection drop down button failed to initialize | Try H, A, J. |
| 3148 | Failed To Show All Connections. All connections were not able to be displayed. | Try E, A, J. |
| 3149 | Failed To Add System Field. | Try A, J. |
| 3150 | Failed To Set Concatenation Button Status. | Try H, A, J. |
| 3151 | Failed To Update Fields. Specific messages reported under this number: • Failed to regenerate the uniqueId and the Primary Route Id of the blockReference. • Failed to regenerate the uniqueId and the Primary Route Id of the route. | Try A, J. |
| 3152 | Invalid Field Id. Specific messages reported under this number: • Please reload the configuration file as there appears to be a field in the table without a valid Id. | Try A, J. |
| 3153 | Layer Update Error. Failed To Update Layer Settings. | Try D, A, J. |
| 3154 | Invalid Group. Failed To Find Group. Specific messages reported under this number: • The Group Id was invalid. Unable to locate in symbol file. • The Group Id was invalid | Try A, J. |
| 3155 | Failed To Initialize Library Editor. | Try H, A, J. |
| 3156 | Invalid Insert Routine. | Try A, J. |
| 3157 | Failed To Remove Group. | Try A, J. |
| 3158 | Failed To Add Group. Specific messages reported under this number: • You cannot make a group from an existing Diagrams group. Use add instead. | Try A, J. |
| 3159 | Failed To Change Insert Type. | Try A, J. |
| 3160 | Section Node Not Found. | Try A, J. |
| 3161 | Failed To Move Section. | Try A, J. |
| 3162 | Failed to create drawing and add to project. | Try A, J. |
| 3163 | Failed To Initialize Project. | Try A, J. |
| 3164 | Failed To Load Diagrams Module. Specific messages reported under this number: • Failed To Load the Diagrams Module from the Diagrams.XML file! • Failed To Load the Diagrams Project Module! | Try H, A, J. |
| 3165 | Failed To Locate Symbol Library File. Specific messages reported under this number: • Please select a valid SymbolLibrary.xml file only | Try D, C, A, J. |
| 3166 | Failed To Update Project File. | Try C, A, J. |
| 3167 | Failed To Add Connector To Connection. | Try E, A, J. |
| 3168 | Failed To Update Connection. Failed to update the connection. Specific messages reported under this number: • Failed to update the CommonDataId on connector with UniqueId … • Unable to set the common data id of connection … to … | Try E, A, J. |
| 3169 | Duplicate Drawing Error. That drawing name already exists. Specific messages reported under this number: • The drawing […] exists in the database more than once. | Try A, J. |
| 3170 | Failed To Construct Command. Failed to construct the command from the element. Specific messages reported under this number: • Unable to create the command for the symbol library element. | Try A, J. |
| 3171 | Failed To Add Primary Route Data. Unable to update the route data. Specific messages reported under this number: • Unable to get … value from the … table. Lookup Route Guid: … • Unable to replace the … values in the … table. | Try A, J. |
| 3172 | Failed To Parse Link Dictionary. Unable to query the link dictionary for linked items. | Try A, J. |
| 3173 | Failed To Get Linked Objects. Unable to get the linked objects from the link dictionary. | Try A, J. |
| 3174 | Failed To Link Objects. Unable to link the objects in the link dictionary. | Try A, J. |
| 3175 | Failed To Load Link Dictionary. Failed to load the link dictionary from the drawing. Specific messages reported under this number: • Failed to load the primary route dictionary from the database. • Failed to load the dictionary from the database. | Try A, J. |
| 3176 | Failed To Save Link Dictionary. Failed to save the link dictionary to the drawing. | Try A, J. |
| 3177 | Failed To Remove Link. Unable to remove the link between objects. | Try A, J. |
| 3178 | Failed To Load Edit Connection Column Names. Unable to load the edit connection dialog column list from the configuration file. | Try D, E, C, J. |
| 3179 | Failed To Save Edit Connection Column Names. Unable to save the edit connection dialog column list to the configuration file. | Try D, E, C, J. |
| 3180 | Failed To Load Project Information. | Try H, A, J. |
| 3181 | Failed To Collect Items. Failed to collect the drawing items. | Try A, J. |
| 3182 | Failed to load views into list. Specific messages reported under this number: • No Views Available • Table Not Found. | Try A, J. |
| 3183 | Invalid View found in listing. Specific messages reported under this number: • The View Fields are not stored correctly. • The View Selected is not valid • The View can not be found | Try A, J. |
| 3184 | Failed To Get Data Manager. Specific messages reported under this number: • Entity with UniqueID of … indicates that it has data but is missing from the entity. • You cannot add a label or tag to an entity that contains no data. • Failed to get the data from the item. ItemId: … • Found unknown Diagram item type. ObjectId: … • BlockName: …; BlockPosition: … • Selected entity is missing data! | Try A, J. |
| 3185 | Failed To Disconnect Connection. Failed to remove the connectors from the connection. Specific messages reported under this number: • Connector 1: …, Connetor 2: … are not pointing to the same connection. • Unable to remove the connectors from the connection. • Connection failed to be deleted. | Try E, A, J. |
| 3186 | Invalid Data Manager. The data manager is invalid. Specific messages reported under this number: • Sync Routine Invalid Data. Connectors cannot have invalid common data id • Sync Routine Invalid Data. Inserts cannot have invalid common data id • Sync Routine Invalid Data. Groups cannot have invalid common data id • Sync Routine Invalid Data. Invalid item type found. • Data Manager Name is empty! | Try A, J. |
| 3187 | Inner Sync Exception. There was an error during the sync progress. | Try A, J. |
| 3188 | Sync Exception. There was an error during the sync process. Specific messages reported under this number: • Error Validating Connection Common Data Id in drawing. • Failed to get the group ObjectIds in the drawing. • Failed to handle the items not in the database. • Failed to update the internal route dictionary. • Failed to handle the items not in the drawing. • Failed to start the sync. | Try A, J. |
| 3189 | Failed To Remove Drawings. Failed to remove the drawings(s) from the database. | Try E, A, J. |
| 3190 | Failed To Add Drawings. Failed to add the drawings(s) to the database. | Try E, A, J. |
| 3191 | Failed To Process Route. Failed to process the route. Specific messages reported under this number: • The route element cannot be deserialized. Please select a route with element information. • Error during the process routes in the add drawing process. • Error during the add drawing process. • Route Connector Data Is Missing | Try A, J. |
| 3192 | Failed To Process Item. Failed to process the item. Specific messages reported under this number: • Error during the process inserts in the add drawing process. • Error during the add drawing process. | Try A, J. |
| 3193 | Failed To Process Group. Failed to process the group. Specific messages reported under this number: • Error during the process groups in the add drawing process. • Error during the add drawing process. | Try A, J. |
| 3194 | Failed To Load Drawing Dictionary. Failed to load the internal drawing info. | Try A, J. |
| 3195 | Failed To Save Drawing Dictionary. Failed to save the internal drawing info. | Try A, J. |
| 3196 | Failed To Initialize Data Viewer. Failed To Initialize DataViewer. | Try A, J. |
| 3197 | Table Type Mismatch. The table type does not match the insertion type. Specific messages reported under this number: • The element cannot be assigned to a table that supports routes. • The element must be assigned to a table that supports routes. | The element is assigned to the wrong table type. Then try A, J. |
| 3200 | Table Editor. Symbol Already Assigned To Table With Non 'Line Insert' Type. | Try H, A, J. |
| 3201 | Table Editor. Symbol Already Assigned To Table With 'Line Insert' Type. | Try H, A, J. |
| 3202 | Failed To Import Drawing. Failed to import the drawing. Specific messages reported under this number: • Failed to import drawing … to project. Aborting... | Try A, J. |
| 3301 | Entity Data Save Canceled. The entity save event was canceled. | Try A, J. |
| 3302 | Failed To Copy Data. Failed to copy the data between elements. Specific messages reported under this number: • Update Block Attributes: Failed to update the block attributes from the data. Block Name: …; Block Position: …; Block Unique Id: … • TABLE … MERGE PROCESS ERROR: Failed to create the temp table. SQL Command: […] • Object with handle … is in the clipped data but missing from original drawing. • TABLE … MERGE PROCESS ERROR: Failed to merge the data. SQL Command: […] • TABLE … UPSERT PROCESS ERROR: Failed to merge data via PostgreSQL ON CONFLICT. • TABLE … MERGE PROCESS ERROR: Failed to BulkCopy the data to the database. • …and 6 more variations. | Try A, J. |
| 3303 | Failed To Copy Element. Failed to copy the element. Specific messages reported under this number: • The route is missing its data. | Try A, J. |
| 3304 | Failed To Join Routes. Failed to join the routes. Specific messages reported under this number: • Unable to determine if selected route spans multiple drawings • No route tables found in the dropdown list. • Failed to join polylines | Try A, J. |
| 3305 | Missing Line Break Distance. The route is missing the line break distance property. Specific messages reported under this number: • The selected instrument route is missing the line break distance. | Please add via the Project Manager. Then try A, J. |
| 3306 | Missing Saved Element Information. Element information is missing from the internal cache of the object. Specific messages reported under this number: • Failed To get data from database for tooltip Table Id: …, Table Name: … • Element data not found on the symbol. • Element data not found on the route. | Try redrawing the object. Then try H, A, J. |
| 3307 | Failed To Audit Drawing. Failed to audit the drawing(s). | Try B, A, J. |
| 3308 | Failed To Import Tracing Styles. Failed to import the project tracing styles. | Try A, J. |
| 3309 | Failed To Export Tracing Styles. Failed to export the project tracing styles. | Try A, J. |
| 3310 | Failed To Publish Pdf. Failed to Publish the Pdfs. | Try C, A, J. |
| 3311 | Failed To Rename Drawing. Failed to rename the drawing. | Try A, J. |
| 3312 | Missing Tank Roof Type. The tank symbol is missing the roof type setting. Specific messages reported under this number: • The symbol type is set to tank but it is missing its roof type. Name: … | Try D, A, J. |
| 3313 | Missing Vessel Type. The vessel symbol is missing the vessel type setting. Specific messages reported under this number: • The symbol type is set to vessel but it is missing its vessel type. Name: … | Try D, A, J. |
| 3314 | Missing Vessel Head Type. The vessel symbol is missing the vessel head type setting. Specific messages reported under this number: • The symbol type is set to vessel but it is missing its vessel head type. Name: … | Try D, A, J. |
| 3315 | Missing Component Type. The vessel symbol is missing the vessel head type setting. Specific messages reported under this number: • The symbol type is set to equipment component but it is missing its component type. Name: … | Try D, A, J. |
| 3316 | Failed To Initialize Tracing Viewer. Failed To Initialize TracingViewer. | Try A, J. |
| 3317 | Failed To Add Visibility CheckBox. Failed to add the visibility checkbox to the form. | Try H, A, J. |
| 3318 | Missing Drawings. The database contains drawings that are not in the project folder. | Try E, C, A, J. |
| 3319 | Failed To Get Drawing Name. Unable to obtain the drawing name from the internal drawing cache. Specific messages reported under this number: • Connector with ID … has an incorrect DrawingID … | Try A, J. |
| 3320 | Failed To Get Connector Data. The entity should have Diagrams xdata on it but it is missing. Specific messages reported under this number: • Symbol … should have connector data but it is missing. Block Position: … | Try B, A, J. |
| 3321 | Failed To Reset Connector. The connector was not reset automatically and needs to be reset manually. Specific messages reported under this number: • Failed to reset the connector. It will need to be done manually. | Try A, J. |
| 3322 | Orphaned Common Data. Common Data Appears that does not appear in the Items or Connections Table. | Please run Clear Orphan Common Data from Project Manager. Then try E, B, A, J. |
| 3323 | Missing Template File. Failed to find the template file at the specified location. Specific messages reported under this number: • The template file location must be set to create drawings. | Check the Project Screen template location and make sure that the file exists. Then try D, C, K, J. |
| 3324 | Invalid Parameter Count. The expected number of parameters was not found. Specific messages reported under this number: • The command […] expected at least … parameter(s) but received … parameter(s) at Line Number … • The command […] expected … parameter(s) but received … parameter(s) at Line Number … | Try A, J. |
| 3325 | Failed To Parse Point Text. Failed to parse the text as a Point3d. Specific messages reported under this number: • The x value cannot be parsed. • The y value cannot be parsed. • The z value cannot be parsed. | Try A, J. |
| 3326 | Failed To Parse Rotation Text. Failed to parse the text as a double value. Specific messages reported under this number: • The rotation value cannot be parsed. | Try A, J. |
| 3701 | Project File BackUps. Failed To Create Backup. | Try C, A, J. |
| 3702 | Connections. Failed to initialize Connection Viewer. | Try E, A, J. |
| 3703 | Database. Failed to Sync Drawing. | Try E, A, J. |
| 3704 | Failed to update the Change System Status. | Try A, J. |
| 3705 | Invalid Setting. Failed to load setting. Setting no longer found. Erased? Specific messages reported under this number: • The setting was not found based on the filter. Erased? | Settings will be reloaded. Please try again. Then try D, B, A, J. |
ISOWorx — 6000 to 6999
Isometric production, post-processing and the line list.
| Error | What it means | What to do |
|---|---|---|
| 6000 | Folder Selection Error. Failed To Select PDF Output Directory. | Try C, A, J. |
| 6001 | Invalid Cell Value. | Please check your line list for invalid cell values. Then try A, J. |
| 6002 | Post Processing. Failed to post process isos. | Try A, J. |
| 6003 | The Evaluation Version only allows post-processing of the first 3 Line Numbers in the Excel Spreadsheet. | You must purchase the full release of ISOWorx to process all line numbers in your spreadsheet. Then try I, C, A, J. |
| 6701 | Invalid SOCKETWorx Line List Setup. Specific messages reported under this number: • Please setup the SOCKETWorx Line List from the setup palette. The Fields are not mapped correctly | Try A, J. |
| 6702 | Failed To Get Line List From SocketWorx. Specific messages reported under this number: • The return information was null. | Try A, J. |
| 6703 | Failed To Update ISOWorx Status in SOCKETWorx. Specific messages reported under this number: • Failed To Update SOCKETWorx Line Status after move. | Try A, J. |
| 6704 | ISOWorx. Failed To Detect Iso Production Styles. | Try A, J. |
| 6705 | No Matching Lines Found In SOCKETWorx. Specific messages reported under this number: • The returned table is empty | Try A, J. |
LINKWorx — 7000 to 7999
Database-linked data, tracing and hyperlinks.
| Error | What it means | What to do |
|---|---|---|
| 7000 | LINKWorx. Failed to initialize database information. | Please set up the database connection. Check the log for more information. Then try D, E, H, J. |
| 7001 | LINKWorx. Failed to configure the database tables. | Try D, E, A, J. |
| 7002 | LINKWorx. Invalid button pressed. Specific messages reported under this number: • The button pressed does not appear to be valid. | Try D, H, A, J. |
| 7003 | LINKWorx. Custom grid position not found. | Possible setting file corruption. Please check the log for more information. Then try D, H, A, J. |
| 7004 | LINKWorx. There are no available fields set in the current custom grid position. | Try D, H, A, J. |
| 7005 | LINKWorx. The select table does not exist in the setting. Refresh? | Try D, A, J. |
| 7006 | LINKWorx. No active fields found for the custom grid. Adjust field selection for current grid. | Try D, E, H, J. |
| 7007 | LINKWorx. No fields found for custom grid. | Please refresh and check the log for more information. Then try D, H, A, J. |
| 7008 | LINKWorx. Failed to get data from database. | Please refresh the database and check the log for more information. Then try D, E, A, J. |
| 7009 | LINKWorx. Tracing database process lines field categories not setup. Specific messages reported under this number: • List is missing from the settings file. | Please setup the Tracing Database Process Lines Field Categories in settings for this feature to work. Then try D, E, A, J. |
| 7010 | LINKWorx. The current database does not contain a process line table. | Please connect to a proper database. Then try D, E, A, J. |
| 7011 | LINKWorx. Failed to refresh tracing database categories. | Try D, E, A, J. |
| 7012 | LINKWorx. Failed to find any category items in database for drawing. Specific messages reported under this number: • Check that the correct drawing is open. | Try D, E, A, J. |
| 7013 | LINKWorx. Tracing category field does not exist in Process Line table. Specific messages reported under this number: • Field: … - Does not exist in the process line table. The settings are incorrect. | Try D, A, J. |
| 7014 | LINKWorx. Failed to initialize the tree grid. | Try D, H, A, J. |
| 7015 | Failed to clear tracing. Specific messages reported under this number: • Failed to clear existing tracing • Failed To Clear Tracing | Try D, A, J. |
| 7016 | Failed to add tracing. Specific messages reported under this number: • Failed to highlight group of combined 2d lines • Failed to highlight group of 3d solids • Failed to highlight group of 2d lines | Try D, A, J. |
| 7017 | Failed to set tracing Visibility. Specific messages reported under this number: • Failed to set highlight visibility | Try D, A, J. |
| 7301 | Failed To Add Root Node. There was a failure while adding the root node. | Try D, A, J. |
| 7302 | Failed To Add Category Node. There was a failure while adding the category node. | Try D, A, J. |
| 7303 | Failed To Add Line Number Node. There was a failure while adding the line number node. | Try D, A, J. |
| 7304 | Failed to add hyperlinks. There was a failure while trying to add hyperlinks to the drawing. | Try A, J. |
MTOWorx — 8000 to 8999
Material take-off collection, lists, snapshots, compares and the SOCKETWorx API.
| Error | What it means | What to do |
|---|---|---|
| 8000 | MTOWorx. Failed to gather sub-entity data. | Try A, J. |
| 8001 | MTOWorx. Failed To Gather Line Numbers. | Try A, J. |
| 8002 | MTOWorx. Failed to find mark layout. | Try A, J. |
| 8301 | Get List API. Deleted list requested and ignored. All other lists returned. | Please update your list selections. Then try A, J. |
| 8302 | Get List API. Failed To Get Valid List Request. The List Request was not in the correct format, encryption, or class. | Please update your API Request. Then try H, A, J. |
| 8303 | Get List API. Failed To Get Lists. An unexpected error occurred. Please try again later. Troubleshoot on the server. Specific messages reported under this number: • Failed to retrieve some or all SocketWorx List items. Lists Requested: …, Lists Received: … • Failed to retrieve SocketWorx List items. Lists Requested: …, Lists Received: … • Failed to retrieve lists from SocketWorx • Failed to retrieve SocketWorx Lists. | Try A, J. |
| 8304 | List Items API. Failed To Get List(s) Items. An unexpected error occurred. Please try again later. Troubleshoot on the server. | Try A, J. |
| 8305 | List Items API. Failed to get a valid List Items request. The List Items Request was not in the correct format, encryption, or class. | Please update your API Request. Then try H, A, J. |
| 8306 | Get SPECWorx Fields API. Failed To Get Valid SPECWorx Field Request. The SPECWorx Field Request was not in the correct format, encryption, or class. | Please update your API Request. Then try H, K, A, J. |
| 8307 | Get SPECWorx Fields API. Failed To Get SPECWorx Material Fields. An unexpected error occurred. Please try again later. Troubleshoot on the server. | Try K, A, J. |
| 8308 | Get SPECWorx Fields Items API. Failed To Get SPECWorx Material Fields Items. An unexpected error occurred. Please try again later. Troubleshoot on the server. | Try K, A, J. |
| 8309 | Get SPECWorx Fields Items API. Failed To Get SPECWorx Material Fields Items. An unexpected error occurred. Please try again later. Troubleshoot on the server. | Try K, A, J. |
| 8310 | Failed To Replace. An unexpected error occurred. Please try again later. Troubleshoot on the server. | Try A, J. |
| 8311 | Mismatch Columns In Snapshot. Mismatch Columns. Please review Current Snapshot Gird and Snapshot. Specific messages reported under this number: • The columns collected for the Current Model do not match the Snapshot Loaded. Please view the Current and Snapshot Grids to determine the issue. | Try A, J. |
| 8312 | Failed To Compare. Failed to load the compare screen. Specific messages reported under this number: • Failed To load the comparer. | Try A, J. |
| 8701 | Failed To Create List. Failed to create the list. | Try A, J. |
| 8702 | Failed to add item to list. | Try A, J. |
| 8703 | Failed To Reload List Items. Failed to reload the items in the list. | Try A, J. |
| 8704 | Empty Template List. The template list cannot be empty! Specific messages reported under this number: • The list […] cannot be empty. | Try D, A, J. |
| 8705 | Failed To Load List. Failed to load the list items. Specific messages reported under this number: • There are no local lists in the settings. Please add some first. | Try A, J. |
| 8706 | List In Use By Template. The list is currently being used by a template and cannot be deleted. Specific messages reported under this number: • The List is currently in use by Template located at […]. Please delete from template first. | Try D, A, J. |
| 8707 | The list does not exist in settings. Specific messages reported under this number: • The list name […] is stored in the settings but the actual list is missing from settings. • The item named […] is defined as a list but that list cannot be found in the settings. • The list name […] with ID […] is no longer found in SOCKETWorx. • There is no list item selected. Please select a list item • List does not exist in settings. | Please close and restart the current dialog. Then try D, A, J. |
| 8708 | Null Rest Response. The response from the server was null. Specific messages reported under this number: • The response was null. | Try A, J. |
| 8709 | Invalid Rest Response. The response from the server was invalid. Specific messages reported under this number: • Failed to login to server. | Try A, J. |
| 8710 | Empty Result Grid. There are no results to export! Specific messages reported under this number: • The Result Grid is empty! | Compare to a snapshot that will generate results. Then try H, A, J. |
| 8711 | There is a duplicate column in the grid. Specific messages reported under this number: • Field […]: The assigned column […] has previously been assigned. | Try H, A, J. |
| 8712 | Invalid Part Number State. Part Number is not selected and must be to use AutoLookup. Specific messages reported under this number: • Part Number must be checked in or to use an AutoLookup field. | Try A, J. |
SHEETWorx — 10000 to 10999
Worksheet, template and completed-drawing folders.
| Error | What it means | What to do |
|---|---|---|
| 10000 | Folder Selection Error. Failed To Select Completed Directory. Specific messages reported under this number: • Failed to open Completed directory: … | Try C, A, J. |
| 10001 | Folder Selection Error. Failed To Select Template Directory. Specific messages reported under this number: • Failed to open Template directory: … | Try D, C, A, J. |
| 10002 | Folder Selection Error. Failed To Select Worksheet Directory. Specific messages reported under this number: • Failed to set iso drawing directory: … • Failed to open Worksheet directory: … • Failed to set output directory: … | Try C, A, J. |
VIEWWorx — 12000 to 12999
Orthographic and isometric detail view creation.
| Error | What it means | What to do |
|---|---|---|
| 12000 | Failed To Set Current View. Failed to set the current view. | Try A, J. |
Database (all plugins) — 14000 to 14999
Shared database layer used by any plugin that stores data in Access, SQL Server or ODBC.
| Error | What it means | What to do |
|---|---|---|
| 14000 | Database Error. Failed to open database. Specific messages reported under this number: • The Sql Command failed to execute on the Sql Server Database: …; Error Message: … • The Sql Command failed to execute on the Sql Server Database: … • The Sql Command failed to execute on the Access Database: … • The Sql Command failed to execute on the Database: … • The Sql Command failed to execute: …; … • Failed to execute trigger block: …; … • …and 5 more variations. | Try E, A, J. |
| 14001 | Database Errors. Failed to close database. Specific messages reported under this number: • Fail To Close Sql Server Database: … • Fail To Close Access Database: … • Fail To Close Database: … | Try E, A, J. |
| 14002 | Database Errors. Database file not found. Specific messages reported under this number: • Database file does not exist in the specified location: … • Access Database file not found: … • Excel file not found: … • Failed to load recent file | Try E, C, A, J. |
| 14003 | Database Errors. Failed To Dispose Connection. Specific messages reported under this number: • Failed to dispose Sql Server Database: … • Failed to dispose Database: … | Try E, A, J. |
| 14004 | Database Errors. Fail To Get Data From Database. Specific messages reported under this number: • Failed to retrieve the selected connector with UniqueId … Connection from the database. • Unable to obtain the Routes from the … table based on primary route id …. • Unable to get connector information from the … table. Connector Id: … • Unable to obtain the … from the … table for the drawing …. • Failed to get the unique values for TableID: …, Field Name: … • Unable to retrieve the connectors from the … in drawing Id …. • …and 45 more variations. | Try E, A, J. |
| 14005 | Database Errors. Failed To Get Primary Key Column Name. Specific messages reported under this number: • Failed To get primary key column name from table: … | Try E, A, J. |
| 14006 | Database Errors. Failed To Get Database Field Schema. Specific messages reported under this number: • Failed To Get Database Field Schema for Sql Server Database: … • Failed To Get Database Field Schema for Access Database: … • Failed To Get Schema: … | Try E, A, J. |
| 14007 | Database Errors. Failed To Get Database Schema. Specific messages reported under this number: • Failed To Get Database Schema for Sql Server Database: … • Failed To Get Database Schema for Access Database: … • Failed To Get Database Schema: … • Failed to retrieve column names. | Try E, A, J. |
| 14008 | Database Errors. Schema Table Empty. Specific messages reported under this number: • Schema table is empty | Try E, A, J. |
| 14009 | Database Errors. Failed To Read Database Tables. Specific messages reported under this number: • Failed to read database tables: … • Unable to get the Items datatable. • Failed to read database tables | Try E, A, J. |
| 14010 | Database Errors. Failed To Test Connection. Specific messages reported under this number: • Failed To test Sql Server Database: … • Failed To test Access Database: … • Failed To test Database: … | Try E, A, J. |
| 14011 | Database Errors. Invalid Connection Database Type. Specific messages reported under this number: • Unsupported database type for ItemsNonCadDatabaseManager: … • Unsupported database type for CommonDataDatabaseManager: … • Unsupported database type for ConnectionDatabaseManager: … • Unsupported database type for DrawingsDatabaseManager: … • Unsupported database type for ItemsDatabaseManager: … • Invalid Database Connection Type | Try E, A, J. |
| 14012 | Database Errors. Failed to Get List of Databases in Server. | Try E, A, J. |
| 14013 | Database Errors. Failed to Refresh Databases and Schemas. | Try E, A, J. |
| 14014 | Database Errors. Failed to List of Schemas. | Try E, A, J. |
| 14015 | Database Errors. Failed to populate the table data. Unable to read database information. Specific messages reported under this number: • Unsuccessful attempt to populate tables | Try E, H, A, J. |
| 14016 | Database Error. Failed to encrypt password. | Try E, A, J. |
| 14017 | Database Error. Failed to decrypt password. | Try E, A, J. |
| 14018 | Database Error. Failed to get query based on field list. | Try E, A, J. |
| 14019 | Database Error. Failed to get SQL Query. Specific messages reported under this number: • Unknown error obtaining drawing name information from the database. • The Sql Command failed to execute on the Access Database: … | Try E, A, J. |
| 14020 | Spreadsheet Not Found. The Excel file used for this data connection could not be found. Specific messages reported under this number: • Excel file not found: … | Verify the spreadsheet still exists at the configured location and that you can open it. If it lives on a network share, check that the share is available. Then try E, C, A, J. |
| 14021 | Field Exists. The Field Already Exists. | You cannot add a field to the table if it already exists. Then try A, J. |
| 14022 | Table Exists. The Table Already Exists. | You cannot add a table if it already exists. Then try A, J. |
| 14023 | Failed To Add Field. Failed to add the field to the list. Specific messages reported under this number: • The … column is not empty! The connector must be empty before a new one can be added to the connection. • The … is not empty! The connector must be empty before a new one can be added to the connection. • Failed to add the field with the name of … to the list of table fields. • Failed to add the field with the name of … to the entity data. • Failed to add the field with the name of … to the line data. | Verify the field doesn't already exist and try again. Then try A, J. |
| 14024 | Failed To Remove Field. Failed to remove the field from the list. Specific messages reported under this number: • Unable to remove the connector from the connection. | Verify the field exists and try again. Then try A, J. |
| 14025 | Field Not Found. The Field was not found in the list. Specific messages reported under this number: • Checkbox tag is missing the field. | Verify the field name is correct and try again. Then try A, J. |
| 14026 | Failed To Set Field Value. Failed to set the field value. Specific messages reported under this number: • Failed to find the field in the data. TableName: …; Field Name: …; Field Id: …; Value: … • Unable to remove the connected drawing name on the connector. • Unable to set the Connected Drawing Name field in the data. | Verify the field exists and try again. Then try A, J. |
| 14027 | Failed To Copy Fields. Failed to copy the fields to another table. | Verify the table integrity and try again. Then try A, J. |
| 14028 | Failed To Add Record. Failed to add the record to the database. Specific messages reported under this number: • Unable to insert the drawing with name … into the … table. • Failed to duplicate the route data in the … table. • Failed to add the connector record to the database. • Failed to add the connection to the database. | Try E, A, J. |
| 14029 | Failed To Delete Record. Failed to delete the record from the database. Specific messages reported under this number: • Unable to remove the records with … of {string.Join( , commonDataIds)} from the … table. • Failed to delete the route data from the … table and/or the … table. • Unable to remove the record with … of … from the … table. • Unable to remove the data from the … table with primary key …. • Unable to remove the drawing with name … from the … table. • Failed to execute the command to delete the orphaned records. • …and 3 more variations. | Try E, A, J. |
| 14030 | Database Form Error. Failed To Switch To Access. | Try E, H, A, J. |
| 14031 | Database Form Error. Failed To Switch To SQL Direct. | Try E, H, A, J. |
| 14032 | Database Form Error. Failed To Switch To SQL ODBC. | Try E, H, A, J. |
| 14033 | Database Error. Failed To Select Access Database. | Try E, A, J. |
| 14034 | Database Form Error. Failed To Update Recent History. | Try E, H, A, J. |
| 14035 | Database Form Error. Invalid Connection Found. Specific messages reported under this number: • Failed to connect to AutoCad Plant3d Master Catalog Database. • Database connection is not configured properly. • Invalid Connection Found - Reloading List. | Try E, H, A, J. |
| 14036 | Database Form Error. Failed To Load Recent History Item. | Try E, H, A, J. |
| 14037 | Database Form Error. Failed To DisplayTables. | Try E, H, A, J. |
| 14038 | Database Error. Failed To Configure SQL Server. Specific messages reported under this number: • The Sql Server is not setup • The Server is not setup | Try D, E, A, J. |
| 14039 | Database Form Error. Failed To Select Table. Specific messages reported under this number: • Legacy table not found | Try E, H, A, J. |
| 14040 | Database Errors. Failed to save the data to the database. Specific messages reported under this number: • Failed to update the CommonDataId in the items table for item with Id: …; New CommonDataId: … • Failed to update the CommonDataId on Connector: ConnectorId: …; CommonDataId: … • Unable to save the data with … of … to the … table. • Unable to update the drawing with ID […] to new name […]. • There were no records affected in the database. SQL: … • Unable to set the Connected Drawing Name for the connector. • …and 6 more variations. | Try E, A, J. |
| 14041 | Database Query. Failed To Execute SQL Query. Specific messages reported under this number: • Failed to get delete Orphaned Common Data Id from the database. SQL: … • Failed to get Orphaned Common Data Id list from the database. SQL: … • Failed To Get 'Bi Directional' Connectors Not Conncected. • Failed To Get 'From' Connectors Not Conncected. • Unable to add the NonCad Items Table: …. • Failed To Get 'To' Connectors Not Conncected. • …and 2 more variations. | Try E, A, J. |
| 14042 | SQL Server Listing. Failed To Get List Of Servers. | Try E, A, J. |
| 14043 | Failed to execute stored procedure. | Try E, A, J. |
| 14044 | Spreadsheet Read Error. Failed to read data from the Excel file. Specific messages reported under this number: • Unable to retrieve stress system information | Close the spreadsheet if it is open in Excel, confirm the expected worksheet and column headings are present, then try again. Then try C, A, J. |
| 14301 | Duplicate SQL Primary Key. The primary key in the SQL Database already exists. | Try E, A, J. |
| 14302 | Failed To Get Record. Failed to get the record from the database. Specific messages reported under this number: • Failed to find Common Data Id on Primary Route Segment in the … table. Primary Route Id: … • Common Data Id not found in the … table. Common Data Id: … • The UniqueId […] was not found in the … table. • Failed to update the drawing name. | Verify the record exists and try again. Then try E, A, J. |
| 14303 | Failed to Update Record. Failed to update the record. Specific messages reported under this number: • Failed to remove timestamp columns from CommonData table. • Failed to add a stored procedure in the ItemData table. • Failed to remove timestamp columns from ItemData table. • Failed to create stored procedure in CommonData table. • Unable to update AssetGroupId for item …. • Failed to add table type in the ItemData table. • …and 2 more variations. | Try E, A, J. |
| 14304 | Invalid Permission. The user does not have the correct permissions. Specific messages reported under this number: • The user does not have permission to perform that action | Try C, A, J. |
| 14305 | Timeout Expired. The time to perform the database operation has expired. | Try E, H, A, J. |
| 14701 | Database connection broken. The database communication failed even after retry. | Try E, A, J. |
General / shared engine (all plugins) — 20000 to 20999
The shared Worx engine: files, settings, entities, palettes, grids, plotting and units. Any plugin can raise these.
| Error | What it means | What to do |
|---|---|---|
| 20000 | Duplicate Error Status Found. Specific messages reported under this number: • Field Names may not be duplicated • … is a duplicate | Try A, J. |
| 20001 | Invalid registered application. The registered application name was invalid. Specific messages reported under this number: • Register Application Table Invalid! | Try I, A, J. |
| 20002 | Unknown Command Failure. The command was stopped for unknown reasons. Specific messages reported under this number: • An error occurred during the ISOGENBATCH command. • An error occurred during the Iso Create command. • Failed to start the command …. • Failed in Isobatch End Command • Failed to cancel a command. • Failed to cancel command. • …and 3 more variations. | Try A, J. |
| 20003 | Failed to Create Layer. The layer failed to create. Specific messages reported under this number: • Failed to clone | Try A, J. |
| 20004 | Failed to Add To Database. The dbobject could not be added to the database. Specific messages reported under this number: • The destination drawing must be different than the source. Please use the copy command instead. • Failed to bind the xrefs | Try E, A, J. |
| 20005 | Failed to Create Palette. Failed to create a palette of the Palette Set. Specific messages reported under this number: • Failed to create the Worx.Cad.Tools main palette. • Palette: DIAGRAMS Properties Palette. • Palette: Iso Post Processing Palette. • Failed to create … palette. • Palette: Diagrams Control Center. • Failed to create ISOWorx palette • …and 3 more variations. | Try H, A, J. |
| 20006 | Failed To Open Entity. Failed to open the entity from the database. Specific messages reported under this number: • Requested object is not an MultiLeader. • Requested object is not a text object. • Requested object is not a group. | Try E, A, J. |
| 20007 | Failed to read config file. Specific messages reported under this number: • Failed to read: … for production iso location. • Failed to read: … for Sheet Numbering. • Failed to read config file: … • Failed to read config | Try D, C, A, J. |
| 20008 | Failed to read config section. | Try D, A, J. |
| 20009 | Failed to read config setting. | Try D, A, J. |
| 20010 | Invalid config setting. Specific messages reported under this number: • Invalid ISOWORX.MTC Header. Please refer to Setup Instructions. There is a Setup Issue in the ISOGEN MLD file for the Material Takeoff Header. It appears the end position: … on column … is longer than the line being read: …. • Invalid … Header.…Column Header: ……Has a Start Column or End Column that does not parse to an integer. …Please fix your ISOWorx.MTC Column Headers. • Invalid … Header.…Column Header: ……Has a Start Column: … greater than End Column: ……Please fix your ISOWorx.MTC Column Headers. • Configuration File is set up to default to the drawing file location. Please turn off the ISOWorx Setting to select the project configuration manually. | Try D, A, J. |
| 20011 | Invalid Dat command. | Try A, J. |
| 20012 | Failed to read Dat File. Specific messages reported under this number: • Dat File processing complete but some lines were skipped. | Try D, C, A, J. |
| 20013 | Failed to read Dat Dialog Name. | Try H, A, J. |
| 20014 | Failed to read Dat Section. | Try A, J. |
| 20015 | Failed To Insert Entity. Failed to insert the entity. Specific messages reported under this number: • Failed to insert labor based on program code. • Failed To Insert Block Into Drawing. • Failed to insert part from palette. • Failed to add label routine error • Failed to insert Plant3D fitting. • Failed to insert Labor item. | Try A, J. |
| 20016 | Block Not Found. The requested block could not be found. Specific messages reported under this number: • Failed To get Isogen Supplemental Block Information • Failed to check CADWorx data • Cannot find the Tag block. | Try A, J. |
| 20017 | Invalid Dat File Function. | Try D, C, A, J. |
| 20018 | Empty Dat File. Specific messages reported under this number: • Dat File is empty | Try D, C, A, J. |
| 20019 | Log Files. Failed to get Log File Listing. | Please check the log file location exists in %PROGRAMDATA%ECE DesignLogs. Then try C, A, J. |
| 20020 | Log Files. Log File Read Failure. | Please check the log file location in %PROGRAMDATA%ECE DesignLogs and try to open in Notepad. Then try C, A, J. |
| 20021 | Null Registry Value. Registry Value Not Found. | Try A, J. |
| 20022 | Failed To Read File Bitmap Preview. Specific messages reported under this number: • FileName: … | Try C, A, J. |
| 20023 | Failed To Collect Entity. Failed to collect the entity during the collection routine. Specific messages reported under this number: • Failed to collect all items!…Attribute Editor encountered an error in a component during collection, indicating an audit is required.…Please audit this model and xrefed models then refresh the grid • …: contains CADWorx Structure objects and these drawings are not listed in the grid. …Modifying CADWorx Structure drawings without CADWorx Structure running will corrupt the drawing. • Failed to collect all items! … CAD Tools encountered an error in a component, indicating an audit is required. … Please audit this model and any xref models then refresh the grid • Failed to collect all items! … BUBBLEWorx encountered an error in a component, indicating an audit is required. … Please audit this model and xrefed models then refresh the grid • Failed to collect all items!… BUBBLEWorx encountered an error in a component, indicating an audit is required.…Please audit this model and xrefed models then refresh the grid • Failed to collect all items!…BUBBLEWorx encountered an error in a component, indicating an audit is required.…Please audit this model and xrefed models then refresh the grid • …and 9 more variations. | Try auditing the drawing and if the problem persists contact support. Then try B, A, J. |
| 20024 | Failed To Find Extents. The entity does not have any extents on it. Specific messages reported under this number: • Failed to get extents of Support Assembly. • Failed To Reset Form Position | Try B, A, J. |
| 20025 | Entity Is Null. The entity object is null. Specific messages reported under this number: • The ObjectId Route Segment List is invalid. • Primary Route Segment ObjectId is invalid. • Unable to find Primary Route. Deleted? • An Invalid Entity is in this model. • Unable to find component. Deleted? • The ObjectId is invalid. | Try A, J. |
| 20026 | Entity Is Not Open For Read/Write. The entity is not open for read or write. | Try C, A, J. |
| 20027 | Failed To Get XData. There was an error getting the xdata on the entity. Specific messages reported under this number: • Failed to gather CADWorx data. To gather data on this item, you must upgrade to CADWorx 2020 R1 or open this file in Vanilla AutoCAD without the CADWorx 2020 object enabler loaded. • Failed to show bubble data on BOM Palette • Failed to show bubble data on MML Palette • Failed to get Plant 3D xData for MLeader • Failed to build field data string • Failed to get fields from XData. • …and 3 more variations. | Try B, A, J. |
| 20028 | Failed To Create Data Structure. Failed to create the entity data structure. | Try A, J. |
| 20029 | Failed To Open Drawing. Failed to open the drawing. Specific messages reported under this number: • Failed to populate the table and field dropdowns after loading drawing • Failed to open the drawing: … • Failed to open the temporary file • Failed to open drawing(s) • You must select a drawing • Failed to Open: … • …and 2 more variations. | Try A, J. |
| 20030 | Failed To Resize Panel. Specific messages reported under this number: • Failed to resize Post Processing Palette | Try H, A, J. |
| 20031 | Failed To Open Folder In Windows Explorer. An error occurred while trying to open the folder. Specific messages reported under this number: • Failed to open labor workbook folder. • Failed to open block library folder. • Failed to open the Completed folder • Failed to open the … folder • Failed to open the Models folder • Failed to open the Iso folder • …and 3 more variations. | Try C, H, A, J. |
| 20032 | Failed To Set Folder Location. An error occurred while trying to select the folder. Specific messages reported under this number: • Failed to set the Stage Folder for …. • Failed to select the Labor directory. • Failed to select the Text directory. • Directory Already Added. | Try C, A, J. |
| 20033 | An error occurred after selecting the file - file not found. Specific messages reported under this number: • The following drawing does not appear to exist: ……Please note that the other drawings will still be processed. • The ISOWorx.MTC file does not exist in the following location: … • The ISOWorx.WSO file does not exist in the following location: … • The BOM.txt file does not exist in the following location: … • The MTC.csv file does not exist in the following location: … • The CL.csv file does not exist in the following location: … • …and 43 more variations. | Try C, A, J. |
| 20034 | Failed To Select The File. An error occurred while trying to select the File. Specific messages reported under this number: • Failed to select the Labor Sheet. • Please select at least 1 item • Please Select A Model | Try C, A, J. |
| 20035 | Failed To Get Themes. An error occurred while trying to get the themes. | Try H, A, J. |
| 20036 | Failed To Load Old Window Position. An error occurred while trying to load the stored window position. | Try H, A, J. |
| 20037 | Error on Form Close. An error occurred while trying to close the form. | Try H, A, J. |
| 20038 | Failed to change themes. An error occurred while trying to change the theme. | Please try a different theme, check the log file and if the problem persists contact support. Then try H, A, J. |
| 20039 | Directory No Longer Available. Unable to access directory. Specific messages reported under this number: • Failed To find … folder to archive drawings. • Failed to find specification directory: …. • The project directory is not available. • Error Locating Directory with UNC Path • Failed to find .Images directory • Failed To find … folder • …and 1 more variations. | Try E, C, A, J. |
| 20040 | Failed To Remove Item. An error occurred while trying to remove the item from the list. | Try A, J. |
| 20041 | Failed To Add Item. An error occurred while trying to add the new item. Specific messages reported under this number: • Failed to get block names from title block drawing:… • Failed to get attributes from title block drawing:… • Failed to get block names from drawing:… • Failed To Add Component To Input Panel • Layer: … already exists • Failed To Add DataEditor | Try A, J. |
| 20042 | Failed To Load Recent Documents. An error occurred while load the recent documents. | Try A, J. |
| 20043 | Failed To Initialize Recent Documents. An error occurred while initialize the recent documents. | Try A, J. |
| 20044 | Failed To Create Pretty Path. An error occurred while trying to create a 'pretty path' for display purposes. | Try C, A, J. |
| 20045 | Argument Null Exception. The argument is null. Specific messages reported under this number: • User Information Missing — User Information is empty. Please fill out the User Information found on the Licensing Palette tab. • The parameter […] cannot be null, empty, or a whitespace! • Please start the cad tools main palette first. • The parameter […] cannot be null! • The entity collection cannot be null • … cannot be null or empty! • …and 3 more variations. | Try A, J. |
| 20046 | Argument Exception. The argument is incorrect. Specific messages reported under this number: • The condition for the argument […] is not met. … • The primary route Id cannot be empty or null! | Try A, J. |
| 20047 | Failed To Convert Result Buffer To Memory Stream. There was a conversion error. | Try A, J. |
| 20048 | Failed to create file, ensure permissions and file is not opened. Specific messages reported under this number: • Unable to rename the modified I-Config Style file to the correct name:…NEW • Unable to rename the modified FLS file to the correct name:…NEW • An unexpected error occurred during processing of the BOM.txt file • Failed to create BOM file per spool. • WELD per spool File Creation Failed. • Failed to create the xlsx Bom file. • …and 6 more variations. | Try C, A, J. |
| 20049 | ObjectID Is Null. The object id is null. Specific messages reported under this number: • Failed to open the drawing ViewTable. • The From ObjectId key cannot be null. • The Linked Object key cannot be null. • The To ObjectId key cannot be null. • The ObjectId key cannot be null. • The … cannot be null. • …and 1 more variations. | Try A, J. |
| 20050 | General. Failed To Commit Change. Specific messages reported under this number: • Textbox Change Committed | Try A, J. |
| 20051 | General. Failed To Convert To Fraction. | Try A, J. |
| 20052 | General. Failed To Convert String To Date. | Try A, J. |
| 20053 | General. Failed To Initialize Form. Specific messages reported under this number: • Failed to initialize flex grid host search panel: … • Failed to clear the flex grid host search panel: … • Failed to initialize flex grid host: … • Failed To Initialize Ribbon Group Manager. • The Progress Dialog has not be initialized • Failed To Initialize the Library Editor • …and 6 more variations. | Try H, A, J. |
| 20054 | General. Failed To Process Tab Key. | Try A, J. |
| 20055 | General. Failed To Change Check Box State. | Try A, J. |
| 20056 | General. Failed To Get Plant 3D Property. Specific messages reported under this number: • Failed to get all the part ports. • Failed to get principal port. | Try K, A, J. |
| 20063 | General. Failed Owner Draw In Flex Grid. | Try H, A, J. |
| 20064 | General. Entry Can Not Be Empty. Specific messages reported under this number: • Field […]: Excel Column must be filled out • Archive folder in Setup Palette needs a value • All name fields must be filled out. • Please select a table to remove. • The Table Display Name is Empty! • From folder can Not be Nothing • …and 3 more variations. | Try A, J. |
| 20065 | General. Invalid Entry. Specific messages reported under this number: • There is an invalid Cell Value (Formula?) in the TAG_ Column. Row: … • Enum Helper can not Get Value from Description of the Enumeration! • Field Name can not start with a numerical digit or an underscore! • Reserved. Field Names may not start with SYS_ • List No Longer Exists. Please reload dialog • Field […]: Excel Column is invalid. • …and 1 more variations. | Try A, J. |
| 20066 | General. Failed To Resize Image. | Try H, A, J. |
| 20067 | General. Failed To Get File. Specific messages reported under this number: • MML File is missing. Please create or select one on the MML Tables table • Failed to load the tracing style file. • Failed to select the Config file | Try C, A, J. |
| 20068 | General. Failed to select a single item. Specific messages reported under this number: • Please select a single insert routine item. • You must choose one item from above! • Failed to Single Tag P3D MML Item • Please select field(s) to copy. • Selected Nested Entity failed. • Failed to Single Tag MML Item • …and 3 more variations. | Please select a single item and try again. If the problem persists contact support. Then try A, J. |
| 20069 | General. Failed To Move Item. Specific messages reported under this number: • Failed To Move Item Down • Failed To Move Item Up | Try A, J. |
| 20070 | General. Failed To Validate As Number. | Try A, J. |
| 20071 | General. Failed To Select Item. Specific messages reported under this number: • Failed To Select New Section and/or Insertion Routine • You must be in PaperSpace to populate weld numbers! • Failed to get filtered objects from current space • Failed to get leader landing point • Failed to select existing leaders • Please select at least one item. • …and 5 more variations. | Try A, J. |
| 20072 | General. Failed To Load Image. Specific messages reported under this number: • Failed to set selected bubble image. • Failed to load command type image | Try A, J. |
| 20073 | General. Failed To Apply Updates. Specific messages reported under this number: • Failed to reset the attribute alignment point. Block: …; Position: …; Attribute: …; Justification: … • Failed to add support in drawing ……The drawing changes will be aborted and the process will continue. • An unexpected error occurred while trying to add pipe support sketch to drawing: … • Failed Properties Palette Update: Attribute Text Alignment Position Issue • An Error occurred while processing the following drawing: … • Failed to update: … with the ECE Placeholder Joint. • …and 23 more variations. | Try A, J. |
| 20074 | General. Failed To Open File For Read/Write. File Is Read Only. Specific messages reported under this number: • The Drawing … is currently open. Please close the drawing before attempting to delete. | Try C, A, J. |
| 20075 | General. Argument Out Of Range. Specific messages reported under this number: • The parameter … must be greater than or equal to zero. • True Color is incorrect format | The argument is out of range. Please contact support. Then try A, J. |
| 20076 | General. Failed To Read File. Specific messages reported under this number: • Excel attribute value appears more than once with conflicting block names. Attribute value: … • An error occurred while trying to load or refresh the Job Attributes spreadsheet. • Error Review Log File: An error occurred while processing the Lines Completed • There was an error gathering the Short and Long Pipe Descriptions. • An unexpected error occurred while parsing the BOM.TXT file • An error occurred during process the Cut file • …and 6 more variations. | Try C, A, J. |
| 20077 | General. Failed To Get Directory Information. Specific messages reported under this number: • Failed to get the Stage Folder for …. • Failed to set the Stage Folder for …. • Failed to get the Previous Stage directory. • Failed to get the Current Stage directory. • Failed to get the First Stage directory. • Failed to get the Next Stage directory. • …and 8 more variations. | Try C, H, A, J. |
| 20078 | General. Directory Must Be Empty. Specific messages reported under this number: • Folder is not empty! | Please empty the selected folder before retrying. If the problem persists contact support. Then try C, A, J. |
| 20079 | General. Failed To Start New Process. | Try A, J. |
| 20080 | General. Failed To Validate. Specific messages reported under this number: • Failed to validate the … Header LINENUMBER Column Not Found! • Failed to validate the … Header. DRG Column Not Found! • Failed to validate the … Header. SP Column Not Found! • Failed to setup and run AutoMode • Failed To Validate Section Name • Failed to read ISOGEN locations • …and 2 more variations. | Try A, J. |
| 20081 | General. Failed To Load Grid Information. Specific messages reported under this number: • Failed To Load the Grid Header Information! • Failed to populate grid from a data table. • Failed To Load the Grid Data Information! • Failed to load Felker Labor spreadsheets • Failed to populate current grid • Refresh Non CAD Data Failed • …and 1 more variations. | Try H, A, J. |
| 20082 | General. Failed To Start Editing. | Try A, J. |
| 20083 | General. Failed To Export To Excel. Specific messages reported under this number: • Failed to upload Snapshot to SOCKETWorx. • Failed to export the Model files. • Failed to create MML Spreadsheet • No data in the grid. Abort. • Failed to export all files • Failed to export line list • …and 1 more variations. | Try C, A, J. |
| 20084 | General. Failed To Clear Filter. | Try A, J. |
| 20085 | General. Failed To Read XData. | Try B, A, J. |
| 20086 | General. Failed To Modify Control Status. | Try A, J. |
| 20087 | General. Failed To Handle Implied Selection. Specific messages reported under this number: • Failed to handle an implied selection. | Try A, J. |
| 20088 | General. Failed To Lock View Ports. | Try F, A, J. |
| 20089 | General. Failed To UnLock View Ports. | Try F, A, J. |
| 20090 | General. Failed To Recolor. | Try A, J. |
| 20091 | General. Failed To Sync. Specific messages reported under this number: • Failed to Sync MMLs • Failed to sync BOM | Try A, J. |
| 20092 | General. Invalid Result Buffer. Specific messages reported under this number: • Failed to get result buffer for connections and directions | Try A, J. |
| 20093 | General. Failed To Add Xdata. Specific messages reported under this number: • Failed to add bubbleworx xdata. | Try B, A, J. |
| 20094 | General. Invalid Block Table. Specific messages reported under this number: • Failed to get block attributes from the block. • Failed to get block names from the block table | Try B, A, J. |
| 20095 | General. Invalid Block Table Record. Specific messages reported under this number: • Paper Space Block Table Record Not Found | Try E, B, A, J. |
| 20096 | General. Failed To Clear Grid. | Try H, A, J. |
| 20097 | General. Failed To Get Working Database. Specific messages reported under this number: • Failed to determine the type of the Plant3D connection. • Failed to get the Plant3D SQL connection. • Failed to get CAD database | Try E, A, J. |
| 20098 | General. Failed To Set Mark Number on Line. | Try A, J. |
| 20099 | General. Failed To Load Palette. Specific messages reported under this number: • Failed to load Post Processing palette | Try H, A, J. |
| 20100 | General. Failed To Clear Errors. | Try A, J. |
| 20101 | General. Failed To Find Table. | Try A, J. |
| 20102 | General. Failed To Add Row To Table. Specific messages reported under this number: • Failed to add rows to the Highlight Legend Table • Failed to add Job Attributes to the grid. • Failed to add a Directory row. | Try A, J. |
| 20103 | General. Failed To Update Table. Specific messages reported under this number: • Failed to Update Bom Data Table with Groups • Failed to Update Excel Sheet with Groups • Failed to sync BOM table | Try A, J. |
| 20104 | General. Failed To Return Command Prompt. | Try A, J. |
| 20105 | General. Failed To Exit Message Box. | Try A, J. |
| 20106 | General. Failed To Clear Mark Number. | Try A, J. |
| 20107 | General. Failed To Select All Items. Specific messages reported under this number: • Error selecting all Diagrams routes in the drawing. | Try A, J. |
| 20108 | General. Failed To Clear Selection. | Try A, J. |
| 20109 | General. Failed To Refresh Grid. Specific messages reported under this number: • Failed To Refresh Non CAD Grid after inactive toggle. • An Error occurred during the refresh of the files. • Failed To Refresh on Segment Checkbox Change • Failed To Refresh on Cancel Pending Changes • Failed To Highlight | Close and reopen the palette to reload the grid, then retry. If the problem persists contact support. Then try H, A, J. |
| 20110 | Operation Canceled. The operation was canceled. Specific messages reported under this number: • User canceled the selection | Try A, J. |
| 20111 | General. Failed To Set Sketch Drawing. | Try A, J. |
| 20112 | General. Failed To Set Palette Width. | Try H, A, J. |
| 20113 | General. Failed To Update Palette. Specific messages reported under this number: • Failed to initialize Delete and Insert Labor fields in the palette . • An error occurred while loading the labor types into the drop down. • Failed to update tooltip for Selected Stage Folder … tooltip • An Error occurred during the refresh of the Isogen Folder Files. • An Error occurred during the refresh of the Models Folder Files. • An error occurred while Refreshing the Felker Job Attributes. • …and 121 more variations. | Try H, A, J. |
| 20114 | General. Failed To Get Units. Specific messages reported under this number: • Cannot convert … due to current units. | Try A, J. |
| 20115 | General. Failed To Remove Event Handlers. | Try A, J. |
| 20116 | General. Failed To Dispose Palette. Specific messages reported under this number: • Failed to terminate the ISOWorx Palette. • Failed to dispose ISOWorx Palette. | Try H, A, J. |
| 20117 | General. Failed To Change Document. | Try A, J. |
| 20118 | General. Failed To Finalize Object. | Try A, J. |
| 20119 | General. Failed To Open File. Specific messages reported under this number: • An error occurred while trying to open the Excel Report: … • Failed to open exported worksheet • Failed to open the linelist. • Incorrect file extension. • File to open: … • Failed to open file. | Try C, A, J. |
| 20120 | General. Failed To Set Filter. | Try A, J. |
| 20121 | General. Failed To Write To Cell. Specific messages reported under this number: • Failed to refresh headers in MML • Failed to remove row in MML file • Failed to update MML file • Failed to write to cell. | Try A, J. |
| 20122 | General. Failed To Change Units. Specific messages reported under this number: • Failed to convert the distance to a string. Value: …; Precision: …; | Try A, J. |
| 20123 | General. Failed To Set Grid Columns. Specific messages reported under this number: • Failed to set column Caption and Name for index: … and caption: … • Failed to update column header names. • Failed to set column headers. | Try H, A, J. |
| 20124 | General. Failed To Set Grid Header. | Try H, A, J. |
| 20125 | General. Failed To Set Grid Column Width. | Close and reopen the palette to reset the grid layout, then retry. If the problem persists contact support. Then try H, A, J. |
| 20126 | General. Failed To Create Directory. Specific messages reported under this number: • Failed To Create Directory: …. Please create manually as the ISOWorx does not have permissions to create the directory. | Please create the directory manually and re-run. Then try C, A, J. |
| 20127 | General. There was an error setting the xdata on the entity. Specific messages reported under this number: • Failed to add XData | Try D, B, A, J. |
| 20128 | General. Failed To Zoom To Item. | Try H, A, J. |
| 20129 | General. Failed To Hover For Tool-tip. | Try H, A, J. |
| 20130 | General. Failed To Set Folder Location. Specific messages reported under this number: • Failed to set the stage output directory. The Current Stage Output Directory: … is invalid or empty. • Failed to get the output directory. The Completed Files Directory: … is invalid or empty. • Failed to update folders after Worx Settings were saved • Failed to select the Completed folder • Failed to select the … folder • Failed to select the Archive folder • …and 14 more variations. | Try C, A, J. |
| 20131 | General. Failed To Open Folder In Explorer. Specific messages reported under this number: • Failed to open the ISO output folder. • Failed to open the Archive folder • Folder does not exist: …. • Failed to open … folder • Failed to open the PDF Folder | Try C, A, J. |
| 20132 | Failed To Create Drawing. Failed to create the drawing. Specific messages reported under this number: • Failed To Create Drawing | Try A, J. |
| 20133 | Failed Setting Current Layout. Specific messages reported under this number: • Failed to set layout to modelspace and zoom extents. • Failed to set Model Space | Try D, A, J. |
| 20134 | Failed during plot setup. Specific messages reported under this number: • The block […] does not contain any attributes in the drawing […]. • The block […] could not be opened in the drawing […]. • The block […] does not exist in the drawing […]. • Failed to load the plot settings validator module. • Failed to load the plot styles services module. • Failed to create PDF: … | Try C, A, J. |
| 20135 | Failed Setting Plot Settings. Specific messages reported under this number: • Failed Setting Plot Settings. | Try D, C, A, J. |
| 20136 | Failed Validating Plot Settings. Specific messages reported under this number: • Failed Validating Plot Settings. • Failed Setting Plot Settings. | Try D, C, A, J. |
| 20137 | Failed To Create MLeader. Specific messages reported under this number: • MLEADER Style Standand Does not exist in Block Drawing: … • MLEADER Style Standard Does not exist in Block Drawing: … • Failed to create MLEADER Style with Block Drawing: … • Failed to add single MML leader • Failed to create MML Leader • Failed to place mark bubble • …and 2 more variations. | Try A, J. |
| 20138 | There are no active transactions. Specific messages reported under this number: • Turning off all layers requires an active transaction. | Try A, J. |
| 20139 | This is an invalid URL. Specific messages reported under this number: • Invalid link address: … please try again! • Invalid link address please try again! | Try A, J. |
| 20140 | Listbox Creation Failed. Failed to create listbox. | Try H, A, J. |
| 20141 | Failed to delete file. Specific messages reported under this number: • Failed to delete the ISOGEN Log file:……. Please delete the file manually and retry.…Note: CADWorx may need to be shutdown and restarted. • There is an existing FLS file with NEW appended to it. This must be deleted before recreation. Unable to delete the FLS(NEW) file:…NEW • There was an error trying to delete the Printed Material Listing:……Please delete the file manually and retry. • There was an error trying to delete the Cut Listing:……Please delete the file manually and retry. • Failed to delete the Printed Material Listing:……Please delete the file manually and retry. • Failed to delete the Material Control List:……Please delete the file manually and retry. • …and 18 more variations. | Try C, A, J. |
| 20142 | Failed to move file. Specific messages reported under this number: • Failed to move BOM spreadsheet: …. Please move the file manually to the next stage. • Failed to move PCF to the Completed folder. • Failed to move files to the … folder • Failed to archive the batched isometrics. • Failed to move files to next stage folder • Failed to move the Attribute File report. • …and 5 more variations. | Try C, A, J. |
| 20143 | Failed to remove hyperlink. Specific messages reported under this number: • Failed to remove SOCKETWORX hyperlink | Try A, J. |
| 20144 | Failed to create object. Specific messages reported under this number: • Solid3d build failed: status=… message=… • Failed to create list of standard properties. • Error Creating Hyperlink Hatch. | Try A, J. |
| 20145 | Failed to get plot device. Specific messages reported under this number: • Failed to find DWG To PDF.pc3 plot device. • Failed to find PNG_Icons.pc3 in: …. • Failed to find PNG_Icons.pc3 plot device. • Failed to find … plot device. | Make sure your plot device is found in your %APPDATA% plotters folder and please retry. If the problem persists contact support. Then try C, A, J. |
| 20146 | Failed to plot. Specific messages reported under this number: • Error plotting drawing …. • Failed to create PDF | Try C, A, J. |
| 20147 | File Locked for editing. Specific messages reported under this number: • File is open and locked for editing and cannot be created or overwritten. File: … • The project file is locked for editing by … on machine … at …. • Unspecified Lock Error. Assuming File Locked. • File is locked by …: … • File is locked for sharing. … • File is currently in use! • …and 1 more variations. | Try C, A, J. |
| 20148 | File To Remove Locks. Failed to remove file project locks. | Please remove the locks manually. Then try C, A, J. |
| 20149 | Failed to copy file. Specific messages reported under this number: • Error during the file import process. Some files might have already been copied and may need to be deleted manually. • Failed to copy PNG_Icons.pc3 from: … to: … • Failed to copy convert.exe from: … to: … • Failed to copy … from: … to: … • Failed to copy … to …. • Failed to copy: …! | Try C, A, J. |
| 20150 | Failed To Lock File. Specific messages reported under this number: • Unspecified Lock Error. Failed To Lock File! | Try C, A, J. |
| 20151 | File Not Saved. You must save your current file before proceeding. Specific messages reported under this number: • Failed to save the excel file to […] • Your file must be saved before proceeding. • Unable to determine the current document. • Failed to populate current grid | The file has not been saved, Please save file and try again. Then try C, G, A, J. |
| 20152 | Failed To Model 3D Component. CAD Modeling Error. Specific messages reported under this number: • General Modeling Failure at point: … This may be due to the line thickness. If the highlight line is too wide then the elbows can not be drawn as the bend can not be made. Reduce the line thickness to almost .01 and try again. This may also be due to flange type and engagement length of the components. Please contact support | Try A, J. |
| 20153 | Failed to create CAD Table. Specific messages reported under this number: • No matching items were found to create a table. • Failed to insert Highlight Legend Table • Failed to create BOM table | Try A, J. |
| 20154 | Failed To Delete Entity. Failed to delete an entity. Specific messages reported under this number: • Failed to delete existing labor blocks and insert new blocks. • Failed to delete existing labor blocks. | Try A, J. |
| 20155 | Failed To Model Solid. Failed to model a solid. Specific messages reported under this number: • Failed to generate solid for viewport. • Failed to highlight extrusion to pipe • Failed to highlight elbow extrusion | Try A, J. |
| 20156 | Failed to convert to double. Specific messages reported under this number: • Failed to convert quantity. Value: … • Failed to convert weight. Value: … • Failed to convert the length to decimal. • Failed to convert quantity. | Try A, J. |
| 20157 | Failed to set layer. Specific messages reported under this number: • Block: […] does not have its layer set. Please set all layers before proceeding. • Current layer is null or empty. • Failed to update layer state. | Try A, J. |
| 20158 | Failed to set scale. | Try A, J. |
| 20159 | Item was on a locked layer. Specific messages reported under this number: • The block reference is on a locked layer. Unable to update attributes. Abort. • A pipe component is on a locked layer. Please unlock the layer and re-run! • A pipe support is on a locked layer. Please unlock the layer and re-run! • Attribute on a locked layer.Attribute has been skipped • … is locked or frozen... Aborting command. | Please unlock the layer and try again. Then try C, F, A, J. |
| 20160 | Failed to process enumerable. Specific messages reported under this number: • Failed to check for existing piping item • Failed to check for existing steel item • Failed to process items in viewport • Failed to process selected items • Failed to collect all entities • Failed to get the tag list • …and 1 more variations. | Try A, J. |
| 20161 | Failed to get point. Specific messages reported under this number: • Cannot determine selected table position. • Failed to get leader landing point • Failed to get insertion point. • Failed to get stacked point | Try A, J. |
| 20162 | Failed to update view depth. | Try A, J. |
| 20163 | Failed to get setting. Specific messages reported under this number: • The BOM.TXT file was parsed and it appears that Weight is not turned on through the Project Manager. This must be enabled to parse the BOM.TXT file Properly as 'TOTAL FABRICATION WEIGHT' is required • Unable to find one of the ISOGEN attributes. … Please use the IsogenProjectDataSetup command to populate all required values. • Unable to find a value for: …. … Please use the IsogenProjectDataSetup command to populate this value. • Unable to find a value for: …. … Please contact support. • Failed to get the ISOGEN settings from the AppData IsoDirList.xml. • Failed to get the ISOGEN settings from the AliasIsoDirList.xml. • …and 5 more variations. | Try D, A, J. |
| 20164 | Failed to save setting. Specific messages reported under this number: • The following Error has occurred in the Restore Configuration of Felker Job Attributes Palette. • The following Error has occurred in the Restore Configuration of Post Processing Palette. • The following Error has occurred in the Restore Configuration of Isogen Set up Palette. • The following Error has occurred in the Restore Configuration Routine. • Failed to save the annotation settings. | Try D, A, J. |
| 20165 | Failed to destroy document. | Try A, J. |
| 20166 | Failed to create string. Specific messages reported under this number: • Failed to clean up line number to be Windows Explorer naming safe. • Failed to extract multi-sheet sheet number. • Failed to extract continuation string. | Try A, J. |
| 20167 | Failed to set drawing space. Specific messages reported under this number: • Failed to switch to layout: … | Try A, J. |
| 20168 | Failed To Get Data Structure. Failed to get the entity data structure. Specific messages reported under this number: • Failed to get Plant3D data. | Try A, J. |
| 20169 | Failed to update MLeader. Specific messages reported under this number: • Failed to update Mleader Attributes | Try A, J. |
| 20170 | Failed To Get Row. Failed to get the row. Specific messages reported under this number: • Failed to get the Maximum Row of spreadsheet. General Error. • Failed to get the row data. | Try A, J. |
| 20171 | Please Restart Plant 3D. We had to modify settings in Plant 3D that require a restart. | Please restart Plant 3D. Then try D, K, A, J. |
| 20172 | Loaded modules not found. Failed to get the loaded ARX modules. Specific messages reported under this number: • Failed to get check if module was loaded. • Failed to get loaded modules. | Try H, A, J. |
| 20173 | Duplicate GUID found. Your model contains duplicate GUIDs. | Try B, A, J. |
| 20174 | General. Failed To Set Plant 3D Property. Specific messages reported under this number: • DataLinksManager DataLink Operation: … on link row id … • DataLinksManager Error: … - … • Failed to set port properties. • Failed to update weld number | Try K, A, J. |
| 20175 | General. Failed To Get Version. Specific messages reported under this number: • Error setting the dwg check variable. • Failed to get version. | Try A, J. |
| 20176 | General. Failed to update the drawing. Specific messages reported under this number: • Failed to Change Dynamic Block Visibility State • Failed to prepare the drawing for conversion. • Failed To Remove NoChange From TextStyle • Failed To Append NoChange To TextStyle • Failed To Change Attribute Visibility • Failed To Change Attribute Height • …and 3 more variations. | Try A, J. |
| 20177 | General. Failed to delete a row. Specific messages reported under this number: • At least one view is required. • Failed to delete a row. | Try A, J. |
| 20178 | General. Failed to modify a file. Specific messages reported under this number: • Unable to update existing BOM. Please re-run the ISOBATCH before Post Processing. Failed to delete the Existing BOM file(s) • An unexpected error occurred trying to create the first row in the required text file: process the cut file • An Error occurred while updating the Project Config File • Unable to update the xml Style File! Aborting! • An Error occurred while updating the FLS File • Unable to update the PIP file! Aborting! • …and 3 more variations. | Try C, A, J. |
| 20179 | General. The file cannot be empty. Specific messages reported under this number: • The script file is empty. | Try C, A, J. |
| 20180 | General. Failed to dispose of object. | Try A, J. |
| 20181 | General. Failed to find directory. Specific messages reported under this number: • Failed to ensure output directory exists for drawing '…' at path '…'. • Failed to get directory of Project List: … • The following directory does not exist: … • Failed to find directory: …. • The output directory was not found. • Directory Not Found: … • …and 2 more variations. | Try C, A, J. |
| 20182 | General. Failed to add event handlers. | Try A, J. |
| 20183 | General. Failed to update a file. Specific messages reported under this number: • Failed to update the drawing with Processing data. • Failed to set 'Count' column in MML Spreadsheet. • Failed to get the Alt text for continuations. • Failed to update end codes in Plant 3D files. • Failed to gather data for updating the BOM. • Failed to get the title block name. • …and 1 more variations. | Try C, A, J. |
| 20184 | General. Failed to iterate to the next. | Try A, J. |
| 20185 | General. Failed to display the license manager. | Try I, A, J. |
| 20186 | General. Failed to delete data. | Try A, J. |
| 20187 | Invalid Piping Platform Found. Specific messages reported under this number: • This command is only available in AutoCAD Plant 3D. | Please contact our sales department to discuss using in another piping software. Then try I, H, A, J. |
| 20188 | Collection Is Empty. No items were found during the collection. Specific messages reported under this number: • No items were found during collection. Please try setting the front clip to 1 and the back clip to -1, or running the ECESIMULATEVIEWPORT command to verify the viewport collection solid overlaps the items in the model. | Please check your filters or viewport settings. If the problem persists contact support. Then try A, J. |
| 20301 | Null Reference. Specific messages reported under this number: • Failed to get Attribute Definition from Attribute Reference: Block: …; Position: …; Attribute: …. • Failed to get Block Definition from Block Reference. Block: …; Position: …. • DataLinksManager was null for project part 'Piping' in AcP3dPropertyService constructor. • The reference […] cannot be null, empty, or a whitespace! • ObjectId is marked as a Group but could not create group. • The reference […] cannot be null! • …and 8 more variations. | Try A, J. |
| 20302 | Invalid Parameter Type. Specific messages reported under this number: • Failed to check if component was a fitting. • Failed to check if component was pipe. | Try A, J. |
| 20303 | Invalid Selection. The selection was invalid. Specific messages reported under this number: • You must select a drawing to duplicate and rename. • You must select a single drawing only. • You must select a drawing to rename. • You select must a custom category. | Please choose another selection. Then try A, J. |
| 20304 | The worksheet does not exist. Specific messages reported under this number: • Invalid Template or Worksheet number saved in settings does not exist in the currently selected template. • The 'SNAPSHOT' worksheet was not found in the Excel File. | The worksheet does not exist in the Excel file. Please choose another. Then try C, A, J. |
| 20305 | Failed To Convert To Integer. Failed to convert the value to an integer. Specific messages reported under this number: • Failed to convert the program code from string to integer value. | Try A, J. |
| 20306 | File Exists. Specific messages reported under this number: • The file […] already exists in the project directory! • QR Code image was not generated here:… • Failed to check for MTC.csv or CL.csv. | Try C, A, J. |
| 20307 | Invalid Settings File. The settings file is invalid. Specific messages reported under this number: • Please make sure to select a worx settings file and not another type of xml file. | Settings file is missing the root node <WorxSettings>. Then try D, C, A, J. |
| 20308 | Failed To Set View Current. Failed to set the view current. Specific messages reported under this number: • View […] exists in view table but was unable to be opened. • The View […] does not exist in the view table. | Try A, J. |
| 20309 | Failed To Remove View Clips. Failed to remove the clipping from one or more views. | Check that the views are not on a locked layer and that the drawing is not read-only, then retry. Then try A, J. |
| 20310 | Invalid Canonical Media Name. The media is invalid for the current printer. | Try A, J. |
| 20311 | Missing Plot Style. The plot style cannot be found in the plot style directory. Specific messages reported under this number: • Monochrome.ctb was substituted for missing … but it is also missing from the plot style folder. | Try C, A, J. |
| 20701 | Failed To Get the xData Type from the component. An error occurred while trying to acquire the xData Type. | Try B, A, J. |
| 20702 | Failed To Create Report. An error occurred while trying to create the report. | Try A, J. |
| 20703 | Failed To Expand or Collapse All Nodes. An error occurred while trying to expand or collapse all nodes. | Try H, A, J. |
| 20704 | Failed To Check or Uncheck All Nodes. An error occurred while trying to check or uncheck all nodes. | Try A, J. |
| 20705 | Failed To Update Grid. An error occurred while trying to update the Grid. Specific messages reported under this number: • Failed to load grid with files | Try H, A, J. |
| 20706 | Invalid File Extension. Specific messages reported under this number: • The Line List Spreadsheet File Extension is Invalid; … | Try C, A, J. |
| 20707 | Invalid Spreadsheet. Specific messages reported under this number: • The Line List is missing the ISO_MS_SHEET_NUM_ Column • The Line List is missing the ISO_MS_LINE_NUM_ Column • The Line List could not be verified. General Error. • The Line List is missing the ISO_DWG_NAME_ Column • The Line List is missing the SPOOL_AREA Column • The Line List is missing the TAG_ Column • …and 4 more variations. | Try C, A, J. |
| 20708 | List. Failed To Owner Draw Grid. Specific messages reported under this number: • Completed Grid List • Isogen Grid List • Model Grid List | Try H, A, J. |
| 20709 | Failed To Communicate To SOCKETWorx. Specific messages reported under this number: • The response was valid and was deserialized but the content could not be deserialized • Invalid content type returned from server. Expected application/octet-stream • The response is valid and was deserialized but the Message Key Not Present • Invalid content type returned from server. Expected application/zip • Invalid content type returned from server. Expected text/plain • Invalid Rest Response: Response is neither true or false. • …and 14 more variations. | Try A, J. |
| 20710 | Failed To Find Item. Specific messages reported under this number: • Item selected is not and ELECTROWorx straight piece. Please select again. • Invalid Drawing Id | Try A, J. |
| 20711 | Find/Replace. Failed To Replace Text. | Try A, J. |
| 20712 | Find/Replace. Failed Search By Row. | Try A, J. |
| 20713 | Find/Replace. Failed Search By Column. | Try A, J. |
| 20714 | Grid View. Failed To Format Cells. | Try H, A, J. |
| 20715 | Failed To Get User Information. Specific messages reported under this number: • Please Fill out user information on ECE License Palette. | Please fill out the information on the License Tab of the Palette. Then try H, A, J. |
| 20716 | Failed To Upload Information To SOCKETWorx. Specific messages reported under this number: • Failed to upload Script to SOCKETWorx. | Please fill out the information on the License Tab of the Palette. Then try H, A, J. |
| 20717 | General. Invalid Data. Specific messages reported under this number: • WeldStartNumber must be a valid integer. • No line numbers found in the model. • The package body data was null. • Failed to get view table. • No line numbers selected. | Invalid Data was received. Then try A, J. |
DBWorx — 30000 to 30499
Project data browsing and reporting.
| Error | What it means | What to do |
|---|---|---|
| 30000 | DBWorx. Failed To create 'where clause' query. | Please review the report 'where clause' query saved. Then try A, J. |
| 30001 | DBWorx. Failed to refresh data. | Try A, J. |
| 30002 | DBWorx. Failed to find document record. No longer exists? | Try E, A, J. |
| 30003 | DBWorx: Reporting. Report Selection: The tables REPORT AND DISTINCTPREFIXES are not available. Please check log file and contact support. | Try C, A, J. |
| 30004 | DBWorx: Reporting. Failed to load the selected report. | Try A, J. |
| 30005 | DBWorx. Failed to load the requested window. | Try H, A, J. |
| 30006 | DBWorx: Reporting. Failed check for a valid prefix. | Try A, J. |
| 30007 | DBWorx: Reporting. Failed to find and add project data. Table exists? | Try A, J. |
| 30008 | DBWorx: Reporting. Failed to save report. | Try A, J. |
| 30009 | DBWorx: Reporting. Failed to open report. | Try C, A, J. |
| 30010 | DBWorx: Reporting. Failed to export report. | Try A, J. |
| 30011 | DBWorx: Reporting. Failed to find the report template. Template file deleted? | Try D, C, A, J. |
| 30012 | DBWorx: Reporting. Failed to create SQL query for report. | Try E, A, J. |
| 30013 | DBWorx: Reporting. Failed to create process line SQL query for report. | Try E, A, J. |
| 30014 | DBWorx: Reporting. Failed to load the Excel file for import. | Try C, A, J. |
ATTEWorx / ODA drawing engine — 30500 to 30999
The standalone (non-CAD) drawing reader and preview used by ATTEWorx.
| Error | What it means | What to do |
|---|---|---|
| 30500 | ODA. Failed To Read Drawing File. Specific messages reported under this number: • Failed To load drawing … | Try C, A, J. |
| 30501 | ODA. Failed to Initialize Graphics. Specific messages reported under this number: • Unable to locate .txv file | Try H, A, J. |
| 30502 | ODA. Resize Dev. | Try H, A, J. |
| 30503 | ODA. Failed Resize. | Try H, A, J. |
| 30504 | ODA. Failed To Paint Drawing. | Try H, A, J. |
| 30505 | ODA. Failed To Zoom In. | Try H, A, J. |
| 30506 | ODA. Failed To Zoom Out. | Try H, A, J. |
| 30507 | ODA. Failed To Pan. | Try H, A, J. |
| 30508 | ODA. Failed To Zoom Extents. | Try B, H, A, J. |
| 30509 | ODA. Failed To Locate Item In Drawing. Specific messages reported under this number: • Unable to locate in drawing. | Try A, J. |
| 30510 | ODA. Failed To Zoom Window. | Try H, A, J. |
| 30511 | ODA. Drawing File Open By Another User/Application. Specific messages reported under this number: • Computer Name …, User Name:… | Try C, A, J. |
| 30512 | ODA. Failed To Find Config Path. | Try D, C, A, J. |
| 30513 | ODA. Failed To Save Data. | Try A, J. |
| 30600 | ODA. Failed To Set Tool Tip State. | Try H, A, J. |
Developer — 40000 to 40999
Internal diagnostics.
| Error | What it means | What to do |
|---|---|---|
| 40000 | Failed To List XData. The Xdata failed to list. | Try B, A, J. |
CAD / Plant 3D integration (all plugins) — 41000 to 41999
Reading and writing AutoCAD, BricsCAD, CADWorx and Plant 3D objects, specs, categories and styles.
| Error | What it means | What to do |
|---|---|---|
| 41000 | Failed To Create Bitmap. The system failed to create a 16x16 bitmap from the color choice. | Try A, J. |
| 41001 | Failed To Read Line Type (.Lin) File. The system failed to read the line type files. | Ensure they are correct and they are in the default locations. Please check the log file and call support if necessary. Then try D, C, A, J. |
| 41002 | Failed To Determine If Drawing Open. The system failed to determine if the drawing is open in CAD. | Try A, J. |
| 41003 | Failed To Read File Lock Information. The system failed to read the file lock information on the dwg file. | Please check the log file and call support if necessary. Then try C, H, A, J. |
| 41004 | Failed To Read Drawing File. The system failed to read the drawing file. Specific messages reported under this number: • Template was created in newer version of AutoCAD. Please down save to current version. • Template was created in newer version of AutoCAD. Please downsave to current version. • Failed to read the drawing template file … | Please check the log file and call support if necessary. Then try C, A, J. |
| 41005 | Failed To Save Drawing File. The system failed to save the drawing file. Specific messages reported under this number: • Please ensure the default drawing name is not used and the drawing is initially saved. • Failed to add drawing … to project. Aborting... • Error adding drawings to the database. | Please check the log file and call support if necessary. Then try C, A, J. |
| 41006 | Drawing Exists. That drawing already exists in that location. Specific messages reported under this number: • The file named … already exists in the project folder! | Rename the drawing and try again. Then try A, J. |
| 41007 | Failed To Get Document. The document was not found. | Please try again. Then try A, J. |
| 41008 | Failed to create custom project category. Specific messages reported under this number: • Failed to create custom project category: …. | Try K, A, J. |
| 41009 | Failed to get custom category property values. Specific messages reported under this number: • Failed to get … values from …. | Try K, A, J. |
| 41010 | Failed to get custom project category property. Specific messages reported under this number: • Failed to get property: … from …. | Try K, A, J. |
| 41011 | Failed to find custom project category property. Specific messages reported under this number: • Failed to find property: … from …. | Try K, A, J. |
| 41012 | Failed to get custom project category properties. Specific messages reported under this number: • Failed to get custom project category properties from …. | Try K, A, J. |
| 41013 | Failed to find custom project category. Specific messages reported under this number: • Failed to find custom project category. | Try K, A, J. |
| 41014 | Failed to get custom project categories. Specific messages reported under this number: • Failed to get custom project categories. • Failed to get custom property names. • Failed to get property names. | Try K, A, J. |
| 41015 | Failed to create custom project category property. Specific messages reported under this number: • Failed to create … in … | Try K, A, J. |
| 41016 | Failed To Get Block Reference. Specific messages reported under this number: • Object Erased? | Try A, J. |
| 41017 | Failed To Get Specification. Failed To Get Block Specification. Specific messages reported under this number: • Failed to get components from the current spec. | Try K, A, J. |
| 41018 | Failed To Get Part From Specification. Specific messages reported under this number: • Failed to get piping component from a spec. | Try K, A, J. |
| 41019 | Failed To Get Parts List From Specification. Specific messages reported under this number: • Failed to get parts list from a spec. | Try K, A, J. |
| 41020 | Failed To Get Fitting Class Part Data. Specific messages reported under this number: • Failed to force the Fitting Class Parts data from a spec. • Failed to get the Fitting Class Parts data from a spec. | Try K, A, J. |
| 41021 | Failed To Get SpecManager. Specific messages reported under this number: • Failed to get spec manager from the current spec. | Try K, A, J. |
| 41022 | Failed to find Plant3d component property. Specific messages reported under this number: • Failed to find custom component property. | Try K, A, J. |
| 41023 | No Current Plant 3d Project. Failed to find an open Plant 3d project. Specific messages reported under this number: • Failed to find a current Plant3d project. • The current Plant3d Project is null. | Try K, A, J. |
| 41024 | Drawing Is Not Part Of Current Plant 3d Project. Failed to find current drawing in the current Plant 3d project. Specific messages reported under this number: • Failed to find a current Plant3d project. | Try K, A, J. |
| 41025 | Failed To Explode Block. The block has failed to explode. | Try A, J. |
| 41026 | Dynamic Block Was Found. | Try A, J. |
| 41302 | Audit Error. Failed to complete internal drawing audit. | Try B, A, J. |
| 41303 | Failed To Process Drawing. Failed to complete internal drawing process. Specific messages reported under this number: • Failed to process the database for inserting specification items. • Failed to process the drawing for Plant3d Redraw. | Try A, J. |
| 41701 | Failed To Get Current Space. Internal Error - Space was not determined as Model or Paper. Returning Model space Default. | Please try again. Then try A, J. |
| 41702 | Failed To Get Model Space Block Table Record Not Found. Internal Error - Model Space Block Table Record Not Found. Specific messages reported under this number: • Cannot get model space from database • Cannot get paper space from database | Audit Drawing Required. Then try E, B, A, J. |
| 41703 | Failed To Get PaperSpace Block Table Record Not Found. Internal Error - Paper Space Block Table Record Not Found. | Audit Drawing Required. Then try E, B, A, J. |
| 41704 | Failed To Get Required Active Transaction. An open transaction was not found. Please retry. Specific messages reported under this number: • … requires an active transaction | Try A, J. |
| 41705 | Failed To Get Database. The database reference is invalid. Please retry action. Specific messages reported under this number: • Failed To Open Drawing …. Drawing Open? • You must supply a valid database • Drawing is not opened. | Try E, A, J. |
| 41706 | Prompt Status Error. An error occurred during selection. Prompt Error. Specific messages reported under this number: • Reassignment not supported in Model Space. • Reassignment No supported in Model Space. | Try A, J. |
| 41707 | Failed To Create Plant 3D DataStructure from Object Id. An error occurred during creation of the entity structure. | Try K, A, J. |
| 41708 | Failed To Get Object Id From Stored Handle. Specific messages reported under this number: • Object Erased? | Try A, J. |
| 41709 | Failed To Get Attribute Reference. Specific messages reported under this number: • Attribute Deleted? | Try A, J. |
| 41710 | Invalid Text Style Table. | Try A, J. |
| 41711 | Invalid Text Style Table Record. Specific messages reported under this number: • Original TextStyle Name Not Found! | Try E, A, J. |
| 41712 | Text Style Name Not Found. | Try A, J. |
| 41713 | Failed To Clone Text Style. | Try A, J. |
| 41714 | Failed To get cached layer information during entity collection. | Try H, A, J. |
When the log shows a technical exception instead of an error number
Sometimes the log has no Error# at all, just a .NET exception name and a code path:
System.UriFormatException: Invalid URI: The format of the URI could not be determined. at System.Uri..ctor(String uriString) at Worx.Tools.Socket.Communication.GetSizeLongDescriptionDataBasedOnPartNumberProcessor.Process(...)
These are unhandled faults, so there is no number and no friendly wording. You can still often place them, because the exception name says what kind of thing went wrong and the last readable line names which feature was running. In the example above: a malformed web address (UriFormatException) while talking to SOCKETWorx — which in practice means the SOCKETWorx Server box is empty or missing its http:// prefix. Setting it correctly on the Licensing/SOCKETWorx settings tab fixes it.
Use this table the same way — match the exception name, then confirm against the feature named in the last readable line.
| Exception in the log | What it actually means | What to do |
|---|---|---|
UriFormatException | A web address the software was given is blank or malformed (most often missing http://). | Check the server address in Settings — usually the SOCKETWorx Server box. Enter it with the scheme, e.g. http://myserver:1968. |
NullReferenceExceptionArgumentNullException | Something the command needed simply was not there — no selection made, a setting left blank, or a drawing not yet saved. | Save the drawing, make a selection, and check that the relevant Settings fields are filled in, then retry. A |
FileNotFoundExceptionDirectoryNotFoundException | A file or folder the software was told to use no longer exists at that path. | Re-check the paths in Settings; a moved or renamed network folder is the usual cause. C, D |
UnauthorizedAccessException | Windows refused access — no write permission, or the file is marked read-only. | Confirm you can write to the location, and clear the read-only flag on the file. C |
IOException ("being used by another process") | The file is open somewhere else — in Excel, in CAD, or by a colleague. | Close it everywhere and retry. On a share, check whether another user has it open. C |
SqlExceptionOdbcException | The database itself rejected the request, or could not be reached. | Re-test the connection; check the server is up and your account still has rights. E |
TimeoutExceptionSocketExceptionHttpRequestExceptionWebException | The server or share did not answer in time — network, VPN or a server that is down. | Check your connection/VPN and retry. If it only happens on large jobs, try a smaller selection. E |
FormatException | A value could not be read as the number or date it was expected to be. | Look for a stray character in the cell, spreadsheet column or setting being read — a letter in a numeric field, or a text-formatted date. D |
InvalidOperationException | The action was attempted in the wrong state — wrong space, nothing active, or a dialog already open. | Return to Model space, close any open Worx dialog, then retry. A, H |
KeyNotFoundException | A named entry was expected in a configuration, spec or catalog and was not found. | Check the item exists in the configuration/spec being used. D, K |
Autodesk.AutoCAD.Runtime.Exception (e.g. eLockViolation) | CAD refused the edit — the drawing or object was locked at that moment. | Make sure the drawing is not read-only and no other command is mid-run, unlock the layer, then retry. F, A |
If the exception is not in this list, or the guidance does not apply, send it in — an unhandled exception is something we want to know about and turn into a proper numbered error.
What to send ECE Design support
If the actions above do not clear the error, open a ticket at https://support.ecedesign.com and include:
- The error number and the exact on-screen message (a screenshot is ideal).
- The log entries — open http://localhost:1968/worxlogs (or type
ECESHOWLOGFILEin CAD) and copy the entries from when it happened. - What you were doing — the command you ran and the last few steps before it failed.
- Versions — the Worx Plugins version (License tab of the palette) and your AutoCAD / BricsCAD / CADWorx / Plant 3D version.
- The drawing or project, if you are able to share it. If it cannot leave your network, tell us and we will work from the log.
Errors are logged whether or not you see a message on screen, so the log is worth sending even when the software appeared to carry on normally.
Notes:
- Errors are written to the log whether or not a message appeared on screen, so the log is worth checking even when the software seemed to carry on normally.
- Before running AUDIT on a drawing, take a backup. Auditing is safe in normal use but it does rewrite objects, and on CADWorx drawings a backup means you can always go back.
- The scrambled method names in a stack trace (for example
U1EPt3GEfs(n1m4FazBoedtHJmCfU )) are expected — released Worx code is obfuscated. They are not a sign of a damaged install. Error#-1means the software raised a number it could not look up. There is no specific guidance for it; please send it in so we can give it a proper entry.
Versions:
Applies to all current Worx Plugins releases on AutoCAD, BricsCAD, CADWorx and AutoCAD Plant 3D. Error numbers are stable across versions: a number keeps its meaning once assigned, and new errors take new numbers. Always install the latest release before troubleshooting — your version is on the License tab of the palette.