A SERVICE OF

logo

7-6 Project Make Errors (PMK)
PMK# Description
4004
Can't delete intermediate folder <folder>: <reason> (system
error code <code>)[PMK#4004]
Failure to complete a "clean" command. Write-protected files or
folders in that area might cause this, or it could be caused by user-
defined data in the intermediate folder(s) ("IM" folder(s)) or in the
target folders ("Development" or "Release" folder(s)). NodeBuilder
attempts only to "clean" files produced by NodeBuilder.
4005 Can't delete intermediate file <file>: <reason> [PMK#1005]
See PMK#4004, but for an individual file. Failure reasons include
the file being locked by another process, the file being write-
protected, etc. Failure details are given in <reason>, part of the
actual message being displayed.
4006
The channel type number noted in the program ID <id> is
<cid1>, whereas the transceiver is designed for channel type
<cid2> [PMK#4006]
The channel type ID field in the standard program ID describes a
channel type that is different from the one referred to by the
transceiver used by the current hardware template. This does not
affect the build, but might result in an improperly implemented
L
ONMARK device. This warning may only occur if a standard
program ID is used (0x8* or 0x9* format).
4007
The program ID model number field has reached the
configured maximum of <maximum>. The previous program
ID <previous_pid> will be changed to use the configured
minimum model number <minumum>. Note that this might
cause a failure when importing the external interface
template into LNS [PMK#4007]
Automatic program ID management detected a required program
ID change and reached the end of the configured range. Program
ID management proceeds by re-starting at the beginning of the
specified range. This is likely to cause a problem when importing
the external interface into LNS, you will have to delete the
relevant LNS device template objects and reattempt the build.
4008
The file <file> (<full path>) was previously required for a
build, but can not be found. This might cause a build failure
[PMK#4008]
The build status calculator recognizes a file that was required for a
previous build does not exist any more. This can possibly cause a
build failure, and it could be a normal situation after purposeful
removal of the file in question. For example, if the file in question
were a .h file which is no longer included by the NC code, then this
would be normal. If the #include statement still exists, then this
might result in a compilation failure.