PlantTracks has a number of error messages it can emit. Some of them are comprehensible to most Punch! users, and these are listed here, along with reasons for them and corrective actions. As in all software, however, there are other things that can go wrong that are beyond the ability of all but a programmer to understand. (In some cases, even the programmer is clueless!) They usually represent happenstances beyond the Punch! user's control (but not necessarily beyond the control of the system owner, who may be the same person). They may be associated with system maintenance, disk file errors and so on.
It is important that when reporting an error that caused an error message, the entire error message be reported exactly as it was displayed. A screen capture is ideal means for such reporting; a cut/paste is good too. Copying into a message by retyping is sometimes necessary, but strive for accuracy in the message itself.
These errors usually cannot be fixed by a Punch! user. Please report them as described on the License page.
A fixed format item's specification file could not be located. Error in the pxf file or programming error.
An object specification file contained unexpected object types. Report this to us.
A cabinet wizard specification included an unexpected object type. As above, report this to us.
Another unexpected object type.
A Punch! files was expected to be available, but wasn't. Please report this (with the full text of the message and the circumstances preceeding it).
The following messages are generally due to file corruption in the file <Punch! Main Folder>\PlugIns\PlansPlus\data.pxf. Since Punch! creates the file in question as part of the PowerTool process, it may be due to an error in Punch! or PlantTracks processing, a flakey disk drive, and so on. Fixing this problem will require the file be sent along with the error report.
The following errors are PlantTracks specific, and are discussed on the referenced pages of this document:
The data saved from a previous PlantTracks session has an unexpected, unrecognized format. It will be ignored, meaning that previously saved measurement formatting data is lost, and the formats will revert to Punch! standard. When you exit the program the new PlantTracks data you establish in this session should replace that stored earlier.
A plant has somehow been assigned to more then one scheme. The assiggnment to one of the schemes is dropped.
An attempt has been made to assign a plant to a scheme that doesn't exist. The assignment is dropped.
In invalid plant identifier has been involved in an assignment; the assignment is dropped.
A name enter for the name of a new scheme (or to rename an existing one) is already in use. Re-enter a new name.
The user has requested that the PlantTracks dialog be cancelled, thereby dropping all changes made in the session. This question asks if that was intended by the user.
The PlantCat.ini file in the Punch! main folder is malformed; the expected name could not be found in the section.
PlantTracks and the contents of this help file are
Copyright©2006 by ThistleKeep Engineering; all rights are reserved.
Comments and suggestions, as well as support, are entertained at Lmc@ThistleKeep.com.
"Punch!" and other titles of Punch! operations are trademarks of Punch! Software L.L.C.