Error Messages Reference
b.i.m.m Tools › MultiPushTool
Error Messages Reference
This article lists all known error and warning messages with their cause
and recommended solution.
Errors When Loading Shortcuts and Files
Note: Load errors are warnings — affected rules are still
loaded but with missing or default values. Always verify rules after loading.
| Message |
Cause |
Solution |
|
Scope Box not found (Row X)
|
The saved Scope Box or SolidFilter does not exist in the current
project.
|
Manually reassign the geometry filter of the rule. |
|
Category not found (Row X)
|
The saved category is not present in the project or has a different
internal ID.
|
Select a different category in the rule. |
|
Invalid geometry filter mode (Row X)
|
The saved mode is unknown — possibly an outdated file. |
Set the geometry filter mode manually. |
|
Invalid data source (Row X)
|
The saved data source is unknown. |
Set the data source manually. |
|
Invalid parameter mode (Row X)
|
The saved parameter mode is unknown. |
Set the parameter mode manually. |
|
Invalid value (Row X)
|
The saved value does not match the parameter type. |
Check and correct the rule value. |
|
Invalid value type (Row X)
|
The saved value type is unknown. |
Re-select the target parameter; value type will be re-determined.
|
|
Invalid SolidFilter
|
SolidFilter could not be initialized (missing geometry). |
Check the SolidFilter in the SolidFilterTool or select a different
filter.
|
Execution Errors (Log)
| Message |
Cause |
Solution |
|
No parameter set
|
The rule has no target parameter — it is incomplete. |
Select a target parameter. |
|
No value
|
No value entered for a non-Text parameter. |
Enter a value. |
|
No elements found
|
No element in the project matched the filter criteria. |
Check data source, category, and geometry filter. Are there any
elements of this category in the model?
|
|
No parameters found
|
Found elements have no writable parameters. |
Check category, parameter mode, and project parameter bindings.
|
|
Parameter not found
|
Target parameter not present in found elements. |
Re-select the target parameter. |
|
N parameters not written
|
Revit rejected writing for N elements: formula binding, read-only
category, invalid unit value.
|
Check if the parameter has a formula binding. For doubles: verify
correct unit.
|
|
N elements do not have the parameter
|
N elements in the found set do not have this parameter. Typical
with mixed families.
|
Expected if mixed family types. Otherwise check project parameter
bindings.
|
|
N elements locked
|
Worksharing: N elements could not be checked out — another user
holds them.
|
Wait for other users to release them, then retry. |
|
Checkout failed
|
The worksharing checkout failed entirely (connection issue).
|
Check connection to central file. Restart Revit if needed. |
|
No elements checked out
|
Checkout ran but none of the needed elements could be acquired.
|
All elements are held by others. Wait and retry. |
Startup Errors
| Message |
Cause |
Solution |
| Revit version error on startup |
DLL compiled for a different Revit version than installed. |
Use the correct build for the installed version. |
| License dialog on startup |
No valid license found. |
Obtain or verify license from Planworks GmbH. |
| Add-in does not load (no Ribbon tab) |
Wrong DLL path in .addin file, or file in wrong folder. |
Check and correct the Assembly path in the .addin file. |
Value Input Errors
| Message |
Cause |
Solution |
| "Invalid value" |
Entered value does not match the parameter type (e.g. letters
in an integer field).
|
Correct the value for the parameter type. For formulas: check
the expression.
|
| "Reserved value" |
The text <No Value> is internally reserved
and cannot be set as a text value.
|
Use a different text value. |
| "Not a single token" |
The Pattern Parser expression for a Yes/No parameter is not a
single token.
|
For Yes/No parameters, use only simple tokens without concatenation.
|
Comments
0 comments
Please sign in to leave a comment.