Alarms and errors
Support documents providing advice and assistance on alarms and error messages which may be seen during operation of Productivity+™ applications.
Productivity+™ alarms and errors support documents
-
Help file: Support/knowledgebase material: 'Windows® Installer service error' during installation
During installation of Productivity+™ version 1.60.2 or later, a Windows® Installer service error may be displayed. This document explains how to correctly install Productivity+™ if this error is seen.
-
Help file: Support/knowledgebase material: Parent statement remains in error following an Undo operation
Editing or deleting a measure statement may cause a child statement below a different parent to fall into error. An Undo operation may not fully remove the error. The document explains how to overcome this issue.
-
Help file: Support/knowledgebase material: “Script Error” occurs when installing on 64-bit Windows®
When installing Productivity+™ software, a Script Error dialog may appear when the software CD is loaded. This document provides a workaround solution for instances where this error is seen.
-
Help file: Support/knowledgebase material: RenMF ‘machine kinematics’ upgrade warning for multiple rotary axis machines
Upgrading an installation of Productivity+™ to version 1.7 results in a change to the machine configuration (.RenMF) file and an error dialog may be encountered. This document provides an example of this dialog and advices how to proceed.
-
Help file: Support/knowledgebase material: Runtime error when GibbsCAM® plug-in Probing function is not used in Process Tile 1
When the Probing function (from the Machining Palette) is used in a Process Tile other than Tile 1, a runtime error will occur when creating a probing routine. This document outlines how to avoid this error.
-
Help file: Support/knowledgebase material: Importing a solid model from a local area network (LAN) causes a runtime error
Importing a solid model file into Productivity+™ Active Editor Pro from a network location which the user does not have write access to may generate a runtime error and cause a crash. This document provides a solution.
