Download SanityCheck - e-Node

Reported Items
pact. If you continue to have this error, recover from a backup.
21 Object Map problem. Object '<1>' claims to occupy the same space as '<2>'.
Detailed Description: The Object Map describes where each object exists on
disk, and how long each object is in size. Using this information, SanityCheck verifies that no two objects overlap. If they do overlap, this item is generated. Internal
Object IDs are used to describe the objects.
Actions: Run 4D Tools:Compact. After doing this, rerun SanityCheck, and you
may find that you now have one (or two) objects that are damaged. You will then
need to delete one or both of them and recreate them.
22 Unexpected end of procedure.
Detailed Description: This item occurs when SanityCheck cannot continue processing a procedure because the space allocated for the procedure has all been
parsed, yet SanityCheck is expecting more information.
Actions: Run
4D Tools:Compact. If this doesn’t help, delete the procedure and recreate it from scratch.
23 Invalid math token (<1>) on line <2>.
Detailed Description: This item occurs when SanityCheck encounters a Token
that defines a mathematical operator exists in the procedure, but the operator is
not a valid operator. This item will appear if the procedure is damaged, or if a new
operator has been added to the 4D language that SanityCheck doesn’t yet recognize.
Actions: If you can, inspect the line. If the line looks correct, try retyping it. If SanityCheck still reports this item, try retyping the whole procedure. If the operator
that is in the line appears to be OK, and has just been added to the 4D language,
then you should contact Committed Software for an upgrade. If SanityCheck still
encounters the item, delete the procedure and recreate it from scratch.
24 Invalid 4D function (<1>) on line <2>.
Detailed Description: This item occurs when SanityCheck encounters a 4D
Function within your procedure that is not valid. This item will appear if the procedure is damaged, or if a new function has been added to the 4D language that
SanityCheck doesn’t yet recognize.
Actions: If you can, inspect the line. If the line looks correct, try retyping it. If SanityCheck still reports this item, try retyping the whole procedure. If the 4D function
that is in the line appears to be OK, and has just been added to the 4D language,
then you should contact Committed Software for an upgrade. If SanityCheck still
encounters the item, delete the procedure and recreate it from scratch.
25 Invalid 4D constant type (<1>) on line <2>.
Detailed Description: This item occurs when SanityCheck encounters a constant whose type is not recognized. A constant is a number, or a piece of text.
There are several types of constants supported within 4D. This item will appear if
the procedure is damaged, or if a new constant type has been added to the 4D
language that SanityCheck doesn’t yet recognize.
Actions: If you can, inspect the line. If the line looks correct, try retyping it. If SanityCheck still reports this item, try retyping the whole procedure. If the constant
that is in the line appears to be OK, and has just been added to the 4D language,
then you should contact Committed Software for an upgrade. If SanityCheck still
62