HighRise 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.
The following messages are generally due to file corruption in the file <Punch! Main Folder>\PlugIns\HighRise\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 HighRise processing, a flakey disk drive, a full disk drive, permissions problems and so on. Fixing this problem will require the file be sent along with the error report.
The following errors are HighRise specific, and are discussed on the referenced pages of this document:
When HighRise executes to completion it stores data in the .pro file so that it can pick up right where it left off the next time it is started. In this case, however, the data stored in the file is not in an expected format. Rather than guess, HighRise ignores the data and starts as if the data wasn't recorded in the file. It will overwrite that data when it finishes with the current session's data.
This occurs when the user Cancels out of a HighRise window. This actian causes all edits made in this session (not just those done in the last window) to be lost.
The level reminder windoe could not launch. Please refer this message to support.
Somehow the named measurement was negative, and does not make sense.
An object was unbexpectedly found on Floor 1 without an assigned level. It is assigned the level indicated, the lowest level currently on Floor 1.
A new table of measurements is about to be written out, but an older one was found. You may intend to keep it, so answer appropriately.
The text of the reminder message dropped on a floor when swapping. The ceiling height on that floor needs to be adjusted. Check all the floors for this after swapping levels.
Adejustments are about to begin on selected items, at your request. Indicate whether or not you want to save a text file log of those changes.
Opening the change log file resulted in an error. You may indicate a new file or turn off logging.
The highest lelevl in the list of swapping levels cannot be chosen, since floors 2 and 3 must have levels assigned. The highest you can select is the next-to-highest level, thereby assigning the highest level to Floor 3.
Verification is sought of your assignment command.
When assigning objects to newly created levels, the objects on the 3rd Floor must have a level to go to. Since Floor 2 and 3 are assigned together, you cannot selelct the top level for Floor2. Select a lower one.
HighRise 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.