Errors are fatal problems which make impossible to complete the
code generation successfully. ASPC will not stop building process
after the first error but will try to generate as much as possible
and list all the errors and warnings if possible.
This behavior is similar to the C++ and Java compilers -
compilation continues up to the end and many errors are issued.
Note that one error may cause the others. ASPC will place VB
comments in the output files in the places where an error was
found - this may help to the advanced developers to trace the
problem.
An unpleasant situation may occur in some rare cases if the
structure of the program is corrupted too much. ASPC may show a
strange error if it is unable to determine the bounds of a
Function or Sub for example. In such cases look first the lines
before the error statement and see all the routine definitions
around are correct.
| Code |
Description |
| 0 |
Ungrouped errors
See the error description for details. |
| 1 |
File is not under the project site root
A file listed in the project is not under the project's
source root path. Check the project settings and the file
location. See ASPC Projects for
more information about the requirements. |
| 5 |
Class with the same name is already defined in another file
ASPC found VBScript class with the same name declared in a
different file. this means you are using two different class
declarations which share the same class name. Also the ASPC
may be wrong if you are using copies of one include file.
ASPC assumes that classes declared in different files are
different classes and classes declared in one file (no
matter how many asp files include it) are one class - i.e.
the class is processed during the first include. |
| 8 |
Root of the specified folder does not exist.
Issued when project contains wrong paths for the output
files or VBProject files. This may happen when trying to
compile project generated on another machine if some full
physical paths are recorded in the project file. |
| 201 |
Dim statement syntax
These messages are issued if wrong variable declaration
statement is found. Their description contains more details
about the error. A message with the statement dump is issued
after the error. |
| 301 |
Set and Let properties require at least
one argument
Found Set or Let property definition without arguments. Set
and Let properties require at least one argument - they
represent assignment and their last argument represents the
assigned variable/value. |
| 401 |
Property syntax
Property declaration syntax error. See the description for
details about the error. |
| 402 |
Constructor arguments
Found class constructor with arguments. VB/VBScript
constructors do not have any arguments. |
| 403 |
Constructor access
Found constructor declared as public. Constructors must be
declared Private. |
| 404 |
Destructor arguments
Found class destructor with arguments. VB/VBScript
destructors do not have any arguments. |
| 405 |
Destructor access
Found destructor declared as public. Destructors must be
declared Private. |
| 406 |
Argument list syntax error
Issued when Sub, Function or Property has an incorrect
argument list. for example missing comma or incorrect
parameter names. Message description contains more
information on the particular error and a message with the
argument list dump is issued after the error. |
| 407 |
Duplicate names
Two symbols share the same name in the same scope. This
means you have two variables with the same name or a
variable and method (Function, Sub or Property) with equal
names declared in the same scope. You should change names to
resolve the collision. Note that some of these scripts may
run without causing a run-time error, but duplication of
their names may lead to incorrect functionality. |
| 501 |
Syntax error
Miscellaneous syntax errors. See the error description
and the following message with the error statement dump (if
any). |
| 502 |
Unexpected statement
Issued when a statement of an unexpected type is found.
For example in class declaration assignment statement will
cause this error because classes may contain only members
and variables. Additional message is issued with the
statement type name (for example: Statement - which means
ordinary statement - not a Dim or Const or routine
declaration). In many cases this error may cause the
compiler to misplace the bounds of a class or a member thus
the following errors may look strange - it is recommended to
correct this error before continuing with the following
errors. |
| 10001 |
Unexpected
See the error description for details. These errors are
issued to indicate unexpected syntax constructions. Their
description always contains details about the syntax
construction type of the unexpected token. In most cases
they are accompanied with a message containing the problem
line dump. |
| 10002 |
Reserved name
Reserved name is used for user variable or method. ASPC uses
a few variables for internal purposes and this error
indicates that the developer uses a variable or method with
the same name. Error description contains the problematic
name. |
| 10004 |
Class not found
New operator is used with class name which is not
defined in the project. If the name looks correct - check if
some of the project files are not missed in the project's
file list. |
| 10005 |
Unaccessible
A symbol is not accessible. This means that a particular
variable or member cannot be accessed from within the
routine/class where the error occured. For example this will
happen if you are trying to access private variable of
another class. |
| 10006 |
Internal error
Internal errors are errors occurred in the structures
generated by the ASPC components. In most cases the reason
is incorrect configuration or corrupted installation. If the
description is not enough to understand what happens contact
us for support. |
| 10007 |
File not found
A file listed in the project, include file or another
required file is not found. Check the file location and the
include directive if it is an include file. |
