DIGITAL Visual Fortran Error Messages Date: September, 1998 Software Version: DIGITAL Visual Fortran Version 6.
Copyright Page Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Contents This document contains information on the following topics (this color denotes a link): o o o o o o o o o o o Visual Fortran Run-Time Messages Linker Tools Messages (LNKxxxx) BSCMAKE Messages (BKxxxx) C Run-Time Errors (Rxxxx) CVPACK Messages (CKxxxx) CVTRES Messages (CVTxxxx) Math Messages for x86 systems (M6xxx) NMAKE Messages (Uxxxx) Profiler Messages (PRFxxxx) Resource Compiler Messages (RCxxxx) Resource Compiler Messages (RWxxxx)
Visual Fortran Run-Time Errors Page 1 of 48 Visual Fortran Run-Time Errors This section describes Visual Fortran run-time error messages. For each error, the tables in the following sections provide the error number, the severity code, error message text, condition symbol name, and a detailed description of the errors. The severity of the message determines whether program execution continues: Severity Description severe Must be corrected.
Visual Fortran Run-Time Errors Page 2 of 48 l Default Run-Time Error Processing l Handling Run-Time Errors l Locating Run-Time Errors l Run-Time Environment Variables l The Floating-Point Environment Run-Time Errors Having No Numbers and Errors 1 Through 30 This section describes in detail Visual Fortran run-time errors having no numbers and run-time error numbers 1 through 30. In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O error is detected.
Visual Fortran Run-Time Errors Page 3 of 48 Fortran run-time messages. 8 severe (8): Internal consistency check failure FOR$IOS_BUG_CHECK. Internal error. Please check that the program is correct. Recompile if an error existed in the program. If this error persists, submit a problem report. 9 severe (9): Permission to access file denied FOR$IOS_PERACCFIL. Check the permissions of the specified file and whether the network device is mapped and available.
Visual Fortran Run-Time Errors Page 4 of 48 l An array variable was specified with too many or too few subscripts for the l l l l 20 variable. An attempt was made to specify a substring of a noncharacter variable or array name. A substring specifier of the character variable was out-of-bounds. A subscript or substring specifier of the variable was not an integer constant. An attempt was made to specify a substring by using an unsubscripted array variable. severe (20): REWIND error FOR$IOS_REWERR.
Visual Fortran Run-Time Errors Page 5 of 48 This error is returned by END and ERRSNS. 25 severe (25): Record number outside range FOR$IOS_RECNUMOUT. A direct access READ, WRITE, or FIND statement specified a record number outside the range specified when the file was opened. 26 severe (26): OPEN or DEFINE FILE required FOR$IOS_OPEDEFREQ. A direct access READ, WRITE, or FIND statement was attempted for a file when no prior DEFINE FILE or OPEN statement with ACCESS=’DIRECT’ was performed for that file.
Visual Fortran Run-Time Errors Page 6 of 48 In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O error is detected. The first line of the second column provides the message as it is displayed (following forrtl:), including the severity level, message number, and the message text. The following lines of the second column contain the status condition symbol (such as FOR$IOS_INCRECTYP) and an explanation of the message.
Visual Fortran Run-Time Errors Page 7 of 48 RECORDTYPE=’FIXED’ or ’VARIABLE’ in effect, or was created by a program written in a language other than Fortran or Fortran 90. 36 severe (36): Attempt to access non-existent record FOR$IOS_ATTACCNON. A direct-access READ or FIND statement attempted to access beyond the end of a relative file (or a sequential file on disk with fixed-length records) or access a record that was previously deleted from a relative file.
Visual Fortran Run-Time Errors Page 8 of 48 FOR$IOS_INCRECTYP. The RECORDTYPE value in an OPEN statement did not match the record type attribute of the existing file that was opened. 45 severe (45): Keyword value error in OPEN statement FOR$IOS_KEYVALERR. An improper value was specified for an OPEN or CLOSE statement specifier requiring a value. 46 severe (46): Inconsistent OPEN/CLOSE parameters FOR$IOS_INCOPECLO. Specifications in an OPEN or CLOSE statement were inconsistent.
Visual Fortran Run-Time Errors Page 9 of 48 other operations on the logical unit may be performed between the READ and REWRITE statements. 55 severe (55): DELETE error FOR$IOS_DELERR. An error condition was detected by the DIGITAL Fortran RTL I/O system during execution of a DELETE statement. 57 severe (57): FIND error FOR$IOS_FINERR. The DIGITAL Fortran RTL I/O system detected an error condition during execution of a FIND statement. 58¹ info (58): Format syntax error at or near xx FOR$IOS_FMTSYN.
Visual Fortran Run-Time Errors Page 10 of 48 Number Severity Level, Number, and Message Text; Condition Symbol and Explanation 61 severe or info¹ (61): Format/variable-type mismatch FOR$IOS_FORVARMIS². An attempt was made either to read or write a real variable with an integer field descriptor (I, L, O, Z, B), or to read or write an integer or logical variable with a real field descriptor (D, E, or F). To suppress this error message, see the description of /check:noformat.
Visual Fortran Run-Time Errors Page 11 of 48 FOR$IOS_VFEVALERR². The value of a variable format expression was not within the range acceptable for its intended use; for example, a field width was less than or equal to zero. A value of 1 was assumed, except for a P edit descriptor, for which a value of zero was assumed. 70³ severe (70): Integer overflow FOR$IOS_INTOVF. During an arithmetic operation, an integer value exceeded byte, word, or longword range.
Visual Fortran Run-Time Errors 77³ Page 12 of 48 severe (77): Subscript out of range FOR$IOS_SUBRNG. An array reference was detected outside the declared array bounds. 78³ error (78): Process killed FOR$IOS_SIGTERM. The process received a signal requesting termination of this process. Determine source of this software termination signal. 79³ error (79): Process quit FOR$IOS_SIGQUIT. The process received a signal requesting termination of itself.
Visual Fortran Run-Time Errors Page 13 of 48 Run-Time Errors 120 Through 300 This section describes in detail Visual Fortran run-time errors 120 through 300. In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O error is detected. The first line of the second column provides the message as it is displayed (following forrtl:), including the severity level, message number, and the message text.
Visual Fortran Run-Time Errors 146¹ Page 14 of 48 severe (146): Null pointer error FOR$IOS_NULPTRERR. Attempted to use a pointer that does not contain an address. Modify the source program, recompile, and relink. 147¹ severe (147): Stack overflow FOR$IOS_STKOVF. The DIGITAL Fortran RTL encountered a stack overflow while executing your program. 148¹ severe (148): String length error FOR$IOS_STRLENERR.
Visual Fortran Run-Time Errors 155¹ Page 15 of 48 severe(155): Array index out of bounds for index nn FOR$IOS_RANGE2. An array subscript is outside the dimensioned boundaries of that array. Recompile with the /check:bounds option set. 156¹ severe(156): GENTRAP code = hex dec FOR$IOS_DEF_GENTRAP. The DIGITAL Fortran RTL has detected an unknown GENTRAP code. The cause is most likely a software problem due to memory corruption, or software signalling an exception with an incorrect exception code.
Visual Fortran Run-Time Errors Page 16 of 48 FOR$IOS_PGM_BOUNDS. The program tried to access an array element that is outside the specified boundaries of the array. Recompile with the/check:bounds option set. 162¹ severe(162): Program Exception - denormal floating-point operand FOR$IOS_PGM_DENORM. A floating-point arithmetic or conversion operation has a denormalized number as an operand. A denormalized number is smaller than the lowest value in the normal range for the data type specified.
Visual Fortran Run-Time Errors Page 17 of 48 FOR$IOS_PGM_INPGERR. The program tried to access a page that was not present, so the system was unable to load the page. For example, this error might occur if a network connection was lost while trying to run a program over the network. This is an operating system error. See your operating system documentation for more information. 168¹ severe(168): Program Exception - illegal instruction FOR$IOS_PGM_ILLINST.
Visual Fortran Run-Time Errors Page 18 of 48 FOR$IOS_FLAWEDPENT. The Fortran run-time system detected a flawed Pentium® processor. Please contact Intel® to upgrade your processor. To allow program execution to continue when this condition occurs, set the environment variable FOR_RUN_FLAWED_PENTIUM to true and rerun the program. For more information, see Intel Pentium Floating-Point Flaw. 256 severe (256): Unformatted I/O to unit open for formatted transfers FOR$IOS_UNFIO_FMT.
Visual Fortran Run-Time Errors Page 19 of 48 encountered during program execution was nn. This summary message appears at program completion. 298¹ info (298): nn floating overflow traps FOR$IOS_FLOOVFEXC. The total number of floating-point overflow traps encountered during program execution was nn. This summary message appears at program completion. 299¹ info (299): nn floating divide-by-zero traps FOR$IOS_FLODIV0EXC.
Visual Fortran Run-Time Errors Page 20 of 48 FOR$IOS_F6098. The label assigned to the integer-variable name was not specified in the label list of the assigned GOTO statement. 543 severe (543): INTEGER arithmetic overflow FOR$IOS_F6099. This error occurs whenever integer arithmetic results in overflow. 544 severe (544): INTEGER overflow on input FOR$IOS_F6100. An integer item exceeded the legal size limits. An INTEGER(1) item must be in the range -127 to 128.
Visual Fortran Run-Time Errors Page 21 of 48 opened with FORM=’FORMATTED’ and ACCESS=’SEQUENTIAL’. 553 severe (553): Terminal I/O not consistent with OPEN options FOR$IOS_F6202. When a special device such as CON, LPT1, or PRN is opened in an OPEN statement, its access must be sequential and its format must be either formatted or binary. By default ACCESS=’SEQUENTIAL’ and FORM=’FORMATTED’ in OPEN statements.
Visual Fortran Run-Time Errors 562 Page 22 of 48 severe (562): IOFOCUS option illegal with non-window unit FOR$IOS_F6211. IOFOCUS was specified in an OPEN or INQUIRE statement for a non-window unit. The IOFOCUS option can only be used when the unit opened or inquired about is a QuickWin child window. 563 severe (563): IOFOCUS option illegal without QuickWin FOR$IOS_F6212. IOFOCUS was specified in an OPEN or INQUIRE statement for a non-QuickWin application.
Visual Fortran Run-Time Errors Page 23 of 48 This section describes in detail Visual Fortran run-time errors 570 through 614. In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O error is detected. The first line of the second column provides the message as it is displayed (following forrtl:), including the severity level, message number, and the message text.
Visual Fortran Run-Time Errors 575 Page 24 of 48 severe (575): Illegal SHARE value FOR$IOS_F6309. An illegal value was used with the SHARE= option. SHARE= accepts the values ’COMPAT’, ’DENYRW’, ’DENYWR’, ’DENYRD’, and ’DENYNONE’. 577 severe (577): Illegal record number FOR$IOS_F6311. An invalid number was specified as the record number for a directaccess file. The first valid record number for direct-access files is 1. 578 severe (578): No unit number associated with * FOR$IOS_F6312.
Visual Fortran Run-Time Errors Page 25 of 48 FOR$IOS_F6400. A BACKSPACE statement specified a unit connected to a terminal device such as a terminal or printer. 587 severe (587): EOF illegal on terminal device FOR$IOS_F6401. An EOF intrinsic function specified a unit connected to a terminal device such as a terminal or printer. 588 severe (588): ENDFILE illegal on terminal device FOR$IOS_F6402. An ENDFILE statement specified a unit connected to a terminal device such as a terminal or printer.
Visual Fortran Run-Time Errors Page 26 of 48 For example, consider you have a file LONG.DAT that is one continuous record with data fields separated by commas. You then set the buffer associated with the file to 512 bytes, read more than one buffer size of data, tab left to data in the previous buffer, and attempt to read further data, as follows: INTEGER value(300) OPEN (1, FILE = ’LONG.
Visual Fortran Run-Time Errors 605 Page 27 of 48 severe (605): Illegal structure for unformatted file FOR$IOS_F6419. The file was opened with FORM=’UNFORMATTED’ and ACCESS=’SEQUENTIAL’, but its internal physical structure was incorrect or inconsistent. Possible causes: the file was created in another mode or by a non-Fortran program. 606 severe (606): Unknown unit number FOR$IOS_F6420. A statement such as BACKSPACE or ENDFILE specified a file that had not yet been opened.
Visual Fortran Run-Time Errors 612 Page 28 of 48 severe (612): File not open for reading or file locked FOR$IOS_F6500. The program tried to read from a file that was not opened for reading or was locked. 613 severe (613): End of file encountered FOR$IOS_F6501. The program tried to read more data than the file contains. 614 severe (614): Positive integer expected in repeat field FOR$IOS_F6502. When the i*c form is used in list-directed input, the i must be a positive integer.
Visual Fortran Run-Time Errors Page 29 of 48 For example, consider the following: READ(*,*) I, J The preceding statement would cause this error if the input were: 123 ’abc’. 617 severe (617): Invalid string in input FOR$IOS_F6505. A string item was not enclosed in single quotation marks. 618 severe (618): Comma missing in COMPLEX input FOR$IOS_F6506. When using list-directed input, the real and imaginary components of a complex number were not separated by a comma.
Visual Fortran Run-Time Errors 625 Page 30 of 48 severe (625): Wrong number of array dimensions FOR$IOS_F6513. In namelist input, an array name was qualified with a different number of subscripts than its declaration, or a non-array name was qualified. 626 severe (626): Array subscript exceeds allocated area FOR$IOS_F6514. A subscript was specified in namelist input which exceeded the declared dimensions of the array. 627 severe (627): Invalid subrange in NAMELIST input FOR$IOS_F6515.
Visual Fortran Run-Time Errors 634 Page 31 of 48 severe (634): D field exceeds W field in ES edit descriptor FOR$IOS_F6970. The specified decimal length D exceeds the specified total field width W in an ES edit descriptor. 635 severe (635): D field exceeds W field in EN edit descriptor FOR$IOS_F6971. The specified decimal lengthD exceeds the specified total field width W in an EN edit descriptor. 636 severe (636): Exponent of 0 not allowed in format FOR$IOS_F6972.
Visual Fortran Run-Time Errors Page 32 of 48 FOR$IOS_F6985. To control interpretation of embedded and trailing blanks within numeric input fields, you must specify BN (to ignore them) or BZ (to interpret them as zeros). 643 severe (643): Format nesting limit exceeded FOR$IOS_F6986. More than 16 sets of parentheses were nested inside the main level of parentheses in a format. 644 severe (644): ’.’ expected in format FOR$IOS_F6987.
Visual Fortran Run-Time Errors Page 33 of 48 commas or slashes (/). 651 severe (651): %c or $: nonstandard edit descriptor in format FOR$IOS_F6994. 652 severe (652): Z: nonstandard edit descriptor in format FOR$IOS_F6995. Z is not a standard edit descriptor in format. If you want to transfer hexadecimal values, you must use the edit descriptor form Zw [.m], where w is the field width and m is the minimum number of digits that must be in the field (including leading zeros).
Visual Fortran Run-Time Errors Page 34 of 48 Number Severity Level, Number, and Message Text; Condition Symbol and Explanation 657 severe (657): DIM argument to SIZE out of range FOR$IOS_F6702. The argument specified for DIM must be greater than or equal to 1, and less than or equal to the number of dimensions in the specified array. Consider the following: i = SIZE (array, DIM = dim) In this case, 1 <= dim <= n, where n is the number of dimensions in array.
Visual Fortran Run-Time Errors Page 35 of 48 length ’len’ FOR$IOS_F6709. A substring ending position must be a positive integer variable or expression that indicates a position in the string: at least 1 and no greater than the length of the string. 665 severe (665): Subscript ’n’ of ’str’ (value ’val’) is out of range (’first:last’) FOR$IOS_F6710. The subscript for a substring within a string is not a valid string position: at least 1 and no greater than the length of the string.
Visual Fortran Run-Time Errors Page 36 of 48 (’size1’ and ’size2’) FOR$IOS_F6718. ORDER specifies the order of the array dimensions given in SHAPE, and they must be vectors of the same size. 674 severe (674): Element ’n’ of ORDER argument to RESHAPE is out of range (’range’) FOR$IOS_F6719. The ORDER argument specifies the order of the dimensions of the reshaped array, and it must be a permuted list of (1, 2, ..., n) where n is the highest dimension in the reshaped array.
Visual Fortran Run-Time Errors Page 37 of 48 to the number of dimensions in the array to be shifted. That is, 1 <=DIM <= n, where n is the number of dimensions in the array to be shifted. 682 severe (682): DIM argument (’dim’) to CSHIFT is out of range (1:’n’) FOR$IOS_F6727. The optional argument DIM specifies the dimension along which to perform the circular shift, and must be greater than or equal to 1 and less than or equal to the number of dimensions in the array to be shifted.
Visual Fortran Run-Time Errors Page 38 of 48 In the following table, the first column lists error numbers returned to IOSTAT variables when an I/O error is detected. The first line of the second column provides the message as it is displayed (following forrtl:), including the severity level, message number, and the message text. The following lines of the second column contain the status condition symbol (such as FOR$IOS_INCRECTYP) and an explanation of the message.
Visual Fortran Run-Time Errors Page 39 of 48 rank ’rank’ FOR$IOS_F6739. The optional argument DIM specifies the dimension along which to sum the elements of an array, and must be greater than or equal to 1 and less than or equal to the number of dimensions (rank) of the array. That is, 1 <= DIM <= n, where n is the number of dimensions in array holding the elements to be summed. 695 severe (695): Real zero raised to zero power FOR$IOS_F6740.
Visual Fortran Run-Time Errors Page 40 of 48 EOSHIFT FOR$IOS_F6746. The SHIFT argument to EOSHIFT must be either scalar or an array one dimension smaller than the shifted array. If an array, the shape of the SHIFT must conform to the shape of the array being shifted in every dimension except the one being shifted along. 702 severe (702): BOUNDARY argument to EOSHIFT has wrong LEN (’len1 instead of len2’) FOR$IOS_F6747.
Visual Fortran Run-Time Errors 711 Page 41 of 48 severe (711): INTEGER zero raised to zero power FOR$IOS_F6756. Zero of any type (integer, real, or complex) cannot be raised to zero power. 712 severe (712): SIZE argument (’size’) to ISHFTC intrinsic out of range FOR$IOS_F6757. The argument SIZE must be positive and must not exceed the bit size of the integer being shifted. The bit size of this integer can be determined with the function BIT_SIZE.
Visual Fortran Run-Time Errors Page 42 of 48 FOR$IOS_F6763. There is not enough memory space to hold a temporary array. Dynamic memory allocation is limited by several factors, including swap file size and memory requirements of other applications that are running. If you encounter an unexpectedly low limit, you might need to reset your virtual memory size through the Windows Control Panel or redefine the swap file size. Allocated arrays that are no longer needed should be deallocated.
Visual Fortran Run-Time Errors Page 43 of 48 Dynamic memory allocation is limited by several factors, including swap file size and memory requirements of other applications that are running. If you encounter an unexpectedly low limit, you might need to reset your virtual memory size through the Windows Control Panel or redefine the swap file size. Allocated arrays that are no longer needed should be deallocated. 723 severe (723): DEALLOCATE: object not allocated/associated FOR$IOS_F6768.
Visual Fortran Run-Time Errors Page 44 of 48 FOR$IOS_F6773. There is not enough memory space to hold the automatic data object. Dynamic memory allocation is limited by several factors, including swap file size and memory requirements of other applications that are running. If you encounter an unexpectedly low limit, you might need to reset your virtual memory size through the Windows Control Panel or redefine the swap file size. Allocated arrays that are no longer needed should be deallocated.
Visual Fortran Run-Time Errors Page 45 of 48 FOR$IOS_F6779. MOD(A,P) is computed as A - INT(A/P) * P. So, P cannot be zero. 735 severe (735): P argument to MODULO is real zero FOR$IOS_F6780. MODULO(A,P) for real numbers is computed as A - FLOOR(A/P) * P. So, P cannot be zero. 736 severe (736): P argument to MODULO is zero FOR$IOS_F6781. In the function, MODULO(A,P), P cannot be zero. 737 severe (737): Argument S to NEAREST is zero FOR$IOS_F6782.
Visual Fortran Run-Time Errors 741 Page 46 of 48 severe (741): Recursive i/o reference FOR$IOS_F6786. 742 severe (742): Argument to SHAPE intrinsic is not PRESENT FOR$IOS_F6787. 743 severe (743): Out of range: DIM argument to UBOUND had value ’dim’ FOR$IOS_F6788. The optional argument DIM specifies the dimension whose upper bound is to be returned, and must be greater than or equal to 1 and less than or equal to the number of dimensions in the array.
Visual Fortran Run-Time Errors Page 47 of 48 POSITION= accepts the following values: l ’ASIS’ (the default) l ’REWIND’ - on Fortran I/O systems, this is the same as ’ASIS’ l ’APPEND’ 749 severe (749): Illegal ACTION value FOR$IOS_F6794. An illegal value was used with the ACTION= specifier. ACTION= accepts the following values: l ’READ’ l ’WRITE’ l ’READWRITE’ - the default 750 severe (750): DELIM= specifier not allowed for an UNFORMATTED file FOR$IOS_F6795.
Visual Fortran Run-Time Errors 754 Page 48 of 48 severe (754): Illegal CARRIAGECONTROL= value FOR$IOS_F6799. An illegal value was used with the CARRIAGECONTROL= specifier. CARRIAGECONTROL= accepts the following values: l ’FORTRAN’ - default if /vms is specified or the unit is connected to a terminal or console l ’LIST’ - default for formatted files l ’NONE’ - default for unformatted files 755 severe (755): SIZE= specifier only allowed with ADVANCE=’NO’ FOR$IOS_F6800.
Linker Tools Messages Page 1 of 32 Linker Tools Messages The following topics cover linker tools errors and warnings (LNKnnnn), which can be generated LINK, LIB, DUMPBIN, and EDITBIN: l l l l l l l l l l Linker Errors LNK1000 to LNK1149 Linker Errors LNK1152 to LNK1189 Linker Errors LNK1190 to LNK1581 Linker Errors LNK2001 to LNK2014 Linker Warnings LNK4001 to LNK4039 Linker Warnings LNK4040 to LNK4069 Linker Warnings LNK4070 to LNK4099 Linker Warnings LNK4102 to LNK4549 Linker Warnings LNK6001 to LNK602
Linker Tools Messages Page 2 of 32 The version of MSPDBxx.DLL available on your system does not match the version required by this tool. Linker Tools Error LNK1102 out of memory There was not enough memory for the tool to run. Probably the paging file exceeded available disk space. If a shortage of disk space is not the cause, note the circumstances of the error, try to isolate the problem and create a reproducible test case, then request technical support.
Linker Tools Messages Page 3 of 32 the problem. l There may be a bad block on your disk. Although the operating system and disk hardware should have detected such an error, you may want to run a disk checking program. Linker Tools Error LNK1107 invalid or corrupt file: cannot read at location The tool could not read the file. Recreate the file. Linker Tools Error LNK1108 cannot write file at location The tool could not write to the file.
Linker Tools Messages Page 4 of 32 file in the input. Linker Tools Error LNK1117 syntax error in option "option" The given option was not correctly specified. Linker Tools Error LNK1118 syntax error in keyword statement The given module-definition statement was not correctly specified. Linker Tools Error LNK1119 invalid ordinal number "argument" The argument following the at sign (@) in an ordinal specification was not a valid number.
Linker Tools Messages Page 5 of 32 Linker miscalc (base relocations off by number) There was not enough space in the image to write base relocations. Linker Tools Error LNK1131 no library file specified The LIB /EXTRACT command required a library as input, but a library filename was not specified. Linker Tools Error LNK1132 invalid format for MS-DOS stub file "filename" The filename specified with the /STUB option was not a valid real-mode MS-DOS executable (.EXE) file.
Linker Tools Messages Page 6 of 32 Linker Tools Error LNK1145 /MERGE created circular link for section "section" You attempted to merge a section into itself. Check the /MERGE options. Linker Tools Error LNK1146 no argument specified with option "option" The given option requires an argument. Linker Tools Error LNK1147 invalid number specified with option "option" The argument to the given option was specified incorrectly.
Linker Tools Messages Page 7 of 32 The given symbol is reserved for use by LINK. Linker Tools Error LNK1156 .sbss section not supported An object file contained an .sbss section. Linker Tools Error LNK1157 fixup overflow; offset of target symbol "symbol" greater than +-8MB The VXD is too large, or the sections are not arranged properly.
Linker Tools Messages Page 8 of 32 The build failed due to fixup errors. The /FORCE or /FORCE:UNRESOLVED option overrides this error. Linker Tools Error LNK1166 cannot adjust code at offset=offset, va=value LINK was unable to pad the code as required. Certain instructions are not allowed to cross page boundaries on some processors. LINK attempts to add pads to correct this situation. In this case, LINK could not work around the problem.
Linker Tools Messages Page 9 of 32 failed to /REBASE filename The rebase operation failed on the given file. Linker Tools Error LNK1177 TOC size limit exceeded The linker was unable to create a TOC (Table of Contents) in your image file. The limit is 2048 entries in the TOC. Linker Tools Error LNK1178 missing MODEND record; file is invalid or corrupt The linker tool tried to convert an OMF object module to COFF format but could not find an expected MODEND (module end) record in the OMF object.
Linker Tools Messages Page 10 of 32 Your COFF object module is corrupt since it contains a relocation entry for an undefined static symbol. See Corrupt Object File for more information. Linker Tools Error LNK1187 Corrupt object - unmatched name relocation; ignored Your object file contains bad relocation information. Recopy or recreate the object file. See Corrupt Object File for more information.
Linker Tools Messages Page 11 of 32 Linker Tools Error LNK1199 invalid or corrupt import object: non-zero reserved fields The import library has become corrupted. Rebuild the library. Linker Tools Error LNK1200 error reading program database "filename" The given program database (PDB) could not be read, probably because it is corrupted. If filename is the PDB for an object file, recompile the object file; use the /debug:full and /pdbfile options.
Linker Tools Messages Page 12 of 32 for an object file, recompile to recreate the PDB. Linker Tools Error LNK1210 insufficient memory for incremental link; relink with /INCREMENTAL:NO There was not enough virtual memory available for LINK to create the incremental status (.ILK) file. Linker Tools Error LNK1211 precompiled type information not found; "filename" not linked or overwritten The given object file, compiled with /Yc, either was not specified in the LINK command or was overwritten.
Linker Tools Messages Page 13 of 32 l Mismatched case in your code or module-definition (.DEF) file can cause LNK2001. For l l l l l l l l l example, if you named a variable "var1" in one C++ source file and tried to access it as "VAR1" in another, you would receive this error. The solution is to exactly match the case of the symbol in all references. A project that uses function inlining yet defines the functions in a .CPP file rather than in the header file can cause LNK2001.
Linker Tools Messages l l l l l l l l l l l Page 14 of 32 you don’t create an entrypoint to wWinMainCRTStartup. Use the /ENTRY option or type this value in the Project Settings dialog box. (To find this option in the development environment, click Settings on the Project menu, then click the Link tab, and click Output in the Category box.) See the following Microsoft® Knowledge Base articles located in the Online Information System for more information.
Linker Tools Messages Page 15 of 32 l When you are porting an application from 16 to 32 bits, LNK2001 can occur. The current 32- bit module-definition (.DEF) file syntax requires that __cdecl, __stdcall, and __fastcall functions be listed in the EXPORTS section without underscores (undecorated). This differs from the 16bit syntax, where they must be listed with underscores (decorated). For more information, see the description of the EXPORTS section of module-definition files.
Linker Tools Messages Page 16 of 32 more than one file but was changed between compilations. Recompile all files that include the symbol. l The given symbol was defined differently in two member objects in different libraries, and both member objects were used. l An absolute was defined twice, with a different value in each definition. This error is followed by fatal error LNK1169.
Linker Tools Messages Page 17 of 32 However, if data is referenced in multiple modules, then the TOC space cannot be eliminated to save space. Linker Tools Error LNK2014 TLS relative fixup overflow; .tls section ("section") is too large The section created for thread-local storage (.tls) is too large. TLS data must fit in 32 KB. This data is created using the __declspec(thread) storage class modifier in the declaration and definition of that data.
Linker Tools Messages Page 18 of 32 invalid version number "number"; default version assumed Either the major or the minor number in the specified version argument was not valid. Each part of a version specification must be an integer in the range 1-65535. Options that take a version argument include /SUBSYSTEM and /VERSION. Linker Tools Warning LNK4011 unknown subsystem "argument"; default assumed The /SUBSYSTEM option was incorrectly specified.
Linker Tools Messages Page 19 of 32 Linker Tools Warning LNK4022 cannot find unique match for symbol "symbol" LINK or LIB found multiple matches for the given undecorated symbol and it could not resolve the ambiguity. No output file (.EXE, .DLL, .EXP, or .LIB) is produced. This warning is followed by one warning LNK4006 for each duplicate symbol and is finally followed by fatal error LNK1152. To prevent this warning, specify the symbol in its decorated form.
Linker Tools Messages Page 20 of 32 Linker Tools Warning LNK4038 displaying raw data in number units per line The /RAWDATA option was specified without a formatting argument. DUMPBIN assumed a format value of number units per line of the specified or assumed data type, as follows: Data Type Number none 16 BYTES 16 SHORTS 8 LONGS 4 Linker Tools Warning LNK4039 section "name" specified with /SECTION option does not exist DUMPBIN or EDITBIN could not find a section called name in the input file.
Linker Tools Messages Page 21 of 32 Linker Tools Warning LNK4045 creating LINK_REPRO test case in dir "directory" The LINK_REPRO environment variable, when set, specifies a directory where the linker will copy object files, libraries, and other files. Microsoft can use these files to recreate internal linker errors. The linker will only copy files if LINK_REPRO is set.
Linker Tools Messages Page 22 of 32 the linker before library2. For example, library1 might contain an updated version of a function in library2. If you specify library2 first, the linker will link in the old version rather than the newer version from library1. Linker Tools Warning LNK4059 resourcefile already specified; additional resource file ignored Only one resource file is allowed. The first .RES file specified in the command was used.
Linker Tools Messages Page 23 of 32 cannot create map and/or checksum image; checksum set to 0 This warning can occur if IMAGEHLP.DLL is not available. Return to Main Linker Error Page Linker Warnings LNK4070 to LNK4099 Linker Tools Warning LNK4070 /OUT:filename directive in .EXP differs from output filename f"ilename"; ignoring directive The filename specified in the NAME or LIBRARY statement when the .
Linker Tools Messages Page 24 of 32 Linker Tools Warning LNK4076 invalid incremental status file "filename"; linking nonincrementally LINK cannot write to the incremental status (.ILK) file. Either filename is corrupt or it is not an incremental linking database. Remove the file and relink. Linker Tools Warning LNK4077 exports file "filename" used; ignoring other export specifications The given exports file provides the program’s exports.
Linker Tools Messages Page 25 of 32 Linker Tools Warning LNK4087 CONSTANT keyword is obsolete; use DATA This warning occurs if you use CONSTANT with your exports in a module definition file or on the command line. Use DATA instead. Linker Tools Warning LNK4088 image being generated due to /FORCE option; image may not run The linker encountered an error. Normally it deletes the image it created because the image may not run due to the error.
Linker Tools Messages Page 26 of 32 duplicate name "name" in order file; using last one Order files specify the order you want the linker to load your functions. In your order file, a function appears more than once, so the linker ignored all references to it except the last. For more information on order files, see the /ORDER linker option. Linker Tools Warning LNK4098 defaultlib "library" conflicts with use of other libs; use /NODEFAULTLIB:library You are trying to link with incompatible libraries.
Linker Tools Messages Page 27 of 32 The linker was unable to find your .PDB file. Copy it into the directory that contains object/library. Return to Main Linker Error Page Linker Warnings LNK4102 to LNK4549 Linker Tools Warning LNK4102 export of deleting destructor symbol name; image may not run correctly The program has attempted to export a deleting destructor. The resulting delete may occur across a DLL boundary such that a process can free memory that it does not own.
Linker Tools Messages Page 28 of 32 "/option" not supported by this version of MSPDBxx.DLL; ignored MSPDBxx.DLL does not support the specified option. Linker Tools Warning LNK4108 /ALIGN specified without /DRIVER or /VXD; image may not run The /ALIGN option has been specified without also specifying either /DRIVER or /VXD. Bad alignment can prevent the operating system from loading the final image. Do not use the /ALIGN option unless building a driver or vxd.
Linker Tools Messages Page 29 of 32 reference the library. The linker ignored the container. Linker Tools Warning LNK4546 Mismatch in versions detected. Container may not load. Use /VERBOSE for details. The linker detected a problem with versions in your import libraries (containers). To find out which container (and its version number) is causing the problem, rerun LINK with the /VERBOSE option. Linker Tools Warning LNK4547 Setting "versiontype" to version The linker set versiontype to version.
Linker Tools Messages Page 30 of 32 exports changed; performing full link One or more exports were added or deleted since the last incremental linking session. LINK attempted to correct the problem by running a full link to recreate the incremental status (.ILK) file. Linker Tools Warning LNK6006 program database pdbname missing; performing full link LINK could not find the program database (.PDB) file that it created during the last incremental linking session.
Linker Tools Messages Page 31 of 32 bss (uninitialized data) change; performing full link A bss symbol was changed since the last incremental linking session. A full link was required in order to recreate the incremental status (.ILK) file. Linker Tools Warning LNK6016 absolute symbol changed; performing full link The address of an absolute symbol was changed since the last incremental linking session. A full link was required in order to recreate the incremental status (.ILK) file.
Linker Tools Messages Page 32 of 32 A full link was required. The format of debugging information from Visual C++ version 4.0 or earlier. Code that was initially linked with version 4.0 and that is now linked with a later version thus has inconsistent debugging information. Therefore, a full link was performed to rectify the inconsistency.
BSCMAKE Messages BK1500 through BK4503 Page 1 of 4 BSCMAKE Messages BK1500 through BK4503 7KH IROORZLQJ GHVFULSWLRQV FRYHU %6&0$.( (UURU %. WKURXJK :DUQLQJ %. %6&0$.( (UURU %. 81.12:1 (5525 %6&0$.( GHWHFWHG DQ XQNQRZQ HUURU FRQGLWLRQ 1RWH WKH FLUFXPVWDQFHV RI WKH HUURU WU\ WR LVRODWH WKH SUREOHP DQG FUHDWH D UHSURGXFLEOH WHVW FDVH WKHQ UHSRUW WKH FLUFXPVWDQFHV WR WHFKQLFDO VXSSRUW %6&0$.( (UURU %. XQNQRZQ FKDUDFWHU FKDUDFWHU LQ RSWLRQ RSWLRQ %6&0$.
BSCMAKE Messages BK1500 through BK4503 Page 2 of 4 UHSHDW WKH EXLOG l 7KH GLVN ZDV IXOO l $ KDUGZDUH HUURU RFFXUUHG l 7KH VSHFLILHG RXWSXW ILOH KDG WKH VDPH QDPH DV DQ H[LVWLQJ VXEGLUHFWRU\ %6&0$.( (UURU %. FDQQRW RSHQ WHPSRUDU\ ILOH ILOHQDPH > UHDVRQ@ %6&0$.
BSCMAKE Messages BK1500 through BK4503 Page 3 of 4 QRQLQFUHPHQWDO XSGDWH UHTXLUHV DOO 6%5 ILOHV $Q DWWHPSW ZDV PDGH WR EXLOG D QHZ EURZVH LQIRUPDWLRQ %6& ILOH EXW RQH RU PRUH RI WKH VSHFLILHG 6%5 ILOHV ZDV WUXQFDWHG 7KLV PHVVDJH LV DOZD\V SUHFHGHG E\ ZDUQLQJ %. ZKLFK JLYHV WKH QDPH RI WKH 6%5 ILOH WKDW FDXVHG WKH HUURU %6&0$.
BSCMAKE Messages BK1500 through BK4503 Page 4 of 4 l 7KH ZURQJ ILOHQDPH ZDV VSHFLILHG l 7KH ILOH ZDV GHOHWHG (UURU %. ZLOO UHVXOW l 7KH ILOH ZDV FRUUXSWHG UHTXLULQJ D IXOO EXLOG %6&0$.( :DUQLQJ %.
C Run-Time Errors R6002 through R6025 Page 1 of 3 C Run-Time Errors R6002 through R6025 7KH IROORZLQJ GHVFULSWLRQV FRYHU & 5XQ 7LPH (UURUV 5 WKURXJK 5 IRU PL[HG ODQJXDJH SURJUDPPLQJ & 5XQ 7LPH (UURU 5 IORDWLQJ SRLQW VXSSRUW QRW ORDGHG 7KH SURJUDP QHHGV WKH IORDWLQJ SRLQW OLEUDU\ EXW WKH OLEUDU\ ZDV QRW OLQNHG WR WKH SURJUDP 2QH RI WKH IROORZLQJ PD\ KDYH RFFXUUHG l 7KH SURJUDP ZDV FRPSLOHG RU OLQNHG ZLWK DQ RSWLRQ VXFK DV )3L WKDW UHTXLUHG D FRSURFHVVRU EXW WKH SURJUDP ZDV UXQ R
C Run-Time Errors R6002 through R6025 Page 2 of 3 & 5XQ 7LPH (UURU 5 QRW HQRXJK VSDFH IRU HQYLURQPHQW 7KHUH ZDV HQRXJK PHPRU\ WR ORDG WKH SURJUDP EXW QRW HQRXJK PHPRU\ WR FUHDWH WKH HQYS DUUD\ 2QH RI WKH IROORZLQJ PD\ EH D VROXWLRQ l ,QFUHDVH WKH DPRXQW RI PHPRU\ DYDLODEOH WR WKH SURJUDP l 5HGXFH WKH QXPEHU DQG VL]H RI FRPPDQG OLQH DUJXPHQWV l 5HGXFH WKH HQYLURQPHQW VL]H E\ UHPRYLQJ XQQHFHVVDU\ YDULDEOHV ,I \RXU SURJUDP XVHV WKH FRPSDFW ODUJH RU KXJH PHPRU\ PRGHO WKLV HUURU PD\ EH DYRLGH
C Run-Time Errors R6002 through R6025 Page 3 of 3 1R REMHFW KDV EHHQ LQVWDQWLDWHG WR KDQGOH WKH SXUH YLUWXDO IXQFWLRQ FDOO 7KLV HUURU LV FDXVHG E\ FDOOLQJ D YLUWXDO IXQFWLRQ LQ DQ DEVWUDFW EDVH FODVV WKURXJK D SRLQWHU WKDW LV FUHDWHG E\ D FDVW WR WKH W\SH RI WKH GHULYHG FODVV EXW LV DFWXDOO\ D SRLQWHU WR WKH EDVH FODVV 7KLV FDQ RFFXU ZKHQ FDVWLQJ IURP D YRLG WR D SRLQWHU WR D FODVV ZKHQ WKH YRLG ZDV FUHDWHG GXULQJ WKH FRQVWUXFWLRQ RI WKH EDVH FODVV
CVPACK Messages CK1001 through CK4010 Page 1 of 4 CVPACK Messages CK1001 through CK4010 7KH IROORZLQJ GHVFULSWLRQV FRYHU &93$&. HUURU &. WKURXJK ZDUQLQJ &. &93$&. )DWDO (UURU &. RXW RI PHPRU\ &93$&.
CVPACK Messages CK1001 through CK4010 Page 2 of 4 &93$&. )DWDO (UURU &. FDQQRW ZULWH RXWSXW ILOH 7KH GLVN LV SUREDEO\ IXOO 7KLV HUURU OHDYHV D FRUUXSW ILOH RQ GLVN &93$&. )DWDO (UURU &. W\SH LQIRUPDWLRQ FRUUXSW UHFRPSLOH PRGXOH PRGXOHQDPH 7KH JLYHQ REMHFW ILOH FRQWDLQV FRUUXSWHG LQIRUPDWLRQ 5HFRPSLOH 7U\ FRPSLOLQJ ZLWK D GLIIHUHQW GHEXJ NH\ZRUG &93$&. )DWDO (UURU &.
CVPACK Messages CK1001 through CK4010 Page 3 of 4 &93$&. )DWDO (UURU &. FDQQRW RSHQ SURJUDP GDWDEDVH SGEILOH &93$&. FRXOG QRW RSHQ WKH JLYHQ SURJUDP GDWDEDVH 3'% ILOH 2QH RI WKH IROORZLQJ PD\ EH D FDXVH l 7KH 3'% ILOH GRHV QRW H[LVW &KHFN WKH VSHOOLQJ RI WKH ILOHQDPH DQG SDWK l 7KH 3'% ILOH ZDV RSHQHG RU GHOHWHG E\ DQRWKHU SURFHVV &93$&. DQG /,1.
CVPACK Messages CK1001 through CK4010 Page 4 of 4 GLVFDUGHG WKH UHFRUG 7KH GHEXJJHU FDQ UXQ WKH UHVXOWLQJ H[HFXWDEOH ILOH +RZHYHU WKH V\PERO ZLOO EH DFFHVVLEOH RQO\ E\ WKH GHFRUDWHG QDPH NQRZQ WR WKH OLQNHU DQG GLVSOD\ RI WKH V\PERO ZLOO EH OLPLWHG 7R VHH GHFRUDWHG QDPHV RI LGHQWLILHUV XVH '803%,1 81'(&25$7( &93$&. :DUQLQJ &. XQUHFRJQL]HG W\SH FRQYHUWHG WR 18// UHFRPSLOH PRGXOH PRGXOHQDPH 7KH FRPSLOHU JHQHUDWHG DQ LQYDOLG W\SH UHFRUG LQ WKH PRGXOHQDPH REMHFW ILOH &93$&.
CVTRES Messages CVT1100 through CVT4001 Page 1 of 2 CVTRES Messages CVT1100 through CVT4001 7KH IROORZLQJ GHVFULSWLRQV FRYHU &97 WKURXJK ZDUQLQJ &97 &975(6 )DWDO (UURU &97 GXSOLFDWH UHVRXUFH W\SH W\SH QDPH QDPH ODQJXDJH ODQJXDJH IODJV IODJV VL]H VL]H 7KH JLYHQ UHVRXUFH ZDV VSHFLILHG PRUH WKDQ RQFH &975(6 )DWDO (UURU &97 FDQQRW RSHQ ILOHQDPH IRU UHDGLQJ &975(6 FRXOG QRW RSHQ DQG UHDG WKH JLYHQ ILOH 2QH RI WKH IROORZLQJ PD\ EH D FDXVH l l l l 7KH ILOH GRHV QRW H[LVW &KHFN WK
CVTRES Messages CVT1100 through CVT4001 Page 2 of 2 PDFKLQH W\SH QRW VSHFLILHG DVVXPHG W\SH &975(6 GLG QRW ILQG D PDFKLQH VSHFLILFDWLRQ ,W DVVXPHG WKH JLYHQ PDFKLQH W\SH ,I WKH GHIDXOW LV LQFRUUHFW UHUXQ &975(6 XVLQJ WKH 0$&+,1( RSWLRQ
Math Errors M6101 through M6205 (x86 only) Page 1 of 2 Math Errors M6101 through M6205 (x86 only) 7KH IROORZLQJ GHVFULSWLRQV FRYHU 0DWK (UURUV 0 WKURXJK 0 ZKLFK FDQ RFFXU RQ [ V\VWHPV $OO RI WKHVH PDWK HUURUV WHUPLQDWH WKH SURJUDP ZLWK DQ H[LW FRGH RI D VHYHUH HUURU 0DWK (UURU 0 LQYDOLG $Q LQYDOLG RSHUDWLRQ RFFXUUHG 7KLV HUURU XVXDOO\ RFFXUV ZKHQ WKH RSHUDQG LV 1D1 QRW D QXPEHU RU LQILQLW\ 0DWK (UURU 0 GHQRUPDO $ YHU\ VPDOO IORDWLQJ SRLQW QXPEHU ZDV JHQHUDWHG ZKLFK PD\ QR
Math Errors M6101 through M6205 (x86 only) Page 2 of 2 0DWK (UURU 0 VWDFN XQGHUIORZ $ IORDWLQJ SRLQW RSHUDWLRQ UHVXOWHG LQ D VWDFN XQGHUIORZ RQ WKH FRSURFHVVRU RU WKH HPXODWRU 7KLV HUURU LV RIWHQ FDXVHG E\ D FDOO WR D ORQJ GRXEOH IXQFWLRQ WKDW GRHV QRW UHWXUQ D YDOXH 0DWK (UURU 0 IXQFWLRQ B'20$,1 HUURU $Q DUJXPHQW WR WKH JLYHQ IXQFWLRQ ZDV RXWVLGH WKH GRPDLQ RI OHJDO LQSXW YDOXHV IRU WKDW IXQFWLRQ )RU H[DPSOH WKH IROORZLQJ VWDWHPHQWV JHQHUDWH WKLV HUURU result = sqrt(-1.
NMAKE Messages Page 1 of 12 NMAKE Messages The following topics cover NMAKE Error U1000 through Warning U4011: l NMAKE Errors U1000 to U1049 l NMAKE Errors U1050 to U1100 l NMAKE Error U2001 to Warning U4011 NMAKE Error U1000 through U1050 The following topics cover NMAKE Error U1000 through U1049: NMAKE Fatal Error U1000 syntax error : ’)’ missing in macro invocation A left parenthesis, (, appeared without a matching right parenthesis, ), in a macro invocation.
NMAKE Messages Page 2 of 12 NMAKE Fatal Error U1005 syntax error : text must follow ’:’ in macro A string substitution was specified for a macro, but the string to be changed in the macro was not specified. NMAKE Fatal Error U1006 syntax error : missing closing double quotation mark An opening double quotation mark (") appeared without a closing double quotation mark.
NMAKE Messages Page 3 of 12 NMAKE Fatal Error U1024 illegal argument to !CMDSWITCHES An unrecognized command switch was specified. NMAKE Fatal Error U1025 syntax error : !ENDIF unexpected An !ENDIF directive was found that was not preceded by an !IF directive, or the directive was placed in a syntactically incorrect place. The !IF preprocessing directives include !IF, !IFDEF, !IFNDEF, !ELSE IF, !ELSE IFDEF, and !ELSE IFNDEF.
NMAKE Messages Page 4 of 12 syntax error : too many names to left of ’=’ Only one string is allowed to the left of a macro definition. NMAKE Fatal Error U1037 syntax error : target name missing A colon (:) was found before a target name was found. At least one target is required. NMAKE Fatal Error U1038 internal error : lexer Note the circumstances of the error, try to isolate the problem, create a reproducible test case, and report to technical support.
NMAKE Messages Page 5 of 12 NMAKE Fatal Error U1049 macro or inline file too long (maximum : 64K) An inline file or a macro exceeded the limit of 64K. Return to Main NMAKE Messages Page NMAKE Error U1050 through U1100 The following topics cover NMAKE Error U1050 through U1100: NMAKE Fatal Error U1050 message The message specified with the !ERROR directive was displayed. NMAKE Fatal Error U1051 out of memory NMAKE ran out of memory, including virtual memory, because the makefile was too large or complex.
NMAKE Messages Page 6 of 12 l A file by that name exists with a read-only attribute. l The disk is full. NMAKE Fatal Error U1055 out of environment space The operating system ran out of room for environment variables. Either increase the environment space or set fewer environment variables. NMAKE Fatal Error U1056 cannot find command processor The command processor was not in the path specified in the COMSPEC or PATH environment variables. NMAKE uses COMMAND.COM or CMD.
NMAKE Messages Page 7 of 12 NMAKE Fatal Error U1063 missing macro name before ’=’ A macro definition on the NMAKE command line contained an equal sign (=) without a preceding name. This error can occur if the macro name being defined is itself a macro that expands to nothing. NMAKE Fatal Error U1064 MAKEFILE not found and no target specified The NMAKE command line did not specify a makefile or a target, and the current directory did not contain a file named MAKEFILE.
NMAKE Messages Page 8 of 12 l Check the spelling of the target name. l If targetname is a pseudotarget, specify it as a target in another description block. l If targetname is a macro invocation, be sure it does not expand to a null string. NMAKE Fatal Error U1076 name too long A string exceeded one of the following limits: l A macro name cannot exceed 1024 characters. l A target name (including its path) cannot exceed 256 characters. l A command cannot exceed 2048 characters.
NMAKE Messages Page 9 of 12 target macro ’target’ expands to nothing The given target is an invocation of a macro that has not been defined or has a null value. NMAKE cannot process a null target. NMAKE Fatal Error U1084 cannot create temporary file ’filename’ NMAKE was unable to create the temporary file it needs when it processes the makefile. One of the following may be a cause: l The file already exists with a read-only attribute. l There is insufficient disk space to create the file.
NMAKE Messages Page 10 of 12 NMAKE Fatal Error U1093 cannot mix dot directives Multiple dot directives cannot be specified on one line. The dot directives are .IGNORE, .PRECIOUS, .SILENT, and .SUFFIXES. NMAKE Fatal Error U1094 syntax error : only (NO)KEEP allowed here Something other than KEEP or NOKEEP appeared after the closing set of angle brackets (<<) specifying an inline file. Only KEEP, NOKEEP, or a newline character may follow the angle brackets. No spaces, tabs, or other characters may appear.
NMAKE Messages Page 11 of 12 Return to Main NMAKE Messages Page NMAKE Error U2001 through Warning U4011 The following topics cover NMAKE Error U2001 through Warning U4011: NMAKE Error U2001 no more file handles (too many files open) NMAKE could not find a free file handle. One of the following may be a solution: l Reduce recursion in the build procedures. l In Windows 95 or Windows 98, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files.
NMAKE Messages Page 12 of 12 Because the target was not specified in the .PRECIOUS list, NMAKE deleted the file. NMAKE Warning U4010 ’target’ : build failed; /K specified, continuing ... A command in the commands block for the giventarget returned a nonzero exit code. The /K option told NMAKE to continue processing unrelated parts of the build and to issue an exit code 1 when the NMAKE session is finished.
Profiler Errors PRF1005 through PRF4642 Page 1 of 7 Profiler Errors PRF1005 through PRF4642 7KH IROORZLQJ GHVFULSWLRQV FRYHU 3URILOHU (UURUV 35) WKURXJK 35) 3URILOHU (UURU 35) IDWDO HUURU FRPPRQ RSHUDWLQJ V\VWHP UDQ RXW RI PHPRU\ 7KHUH LV QRW HQRXJK PHPRU\ WR UXQ WKLV SURILOHU PRGXOH 3URILOHU (UURU 35) IDWDO HUURU FRPPRQ FDQQRW RSHQ ILOH ILOHQDPH 7KH SURILOHU PRGXOH FRXOG QRW ILQG WKH VSHFLILHG ILOH 3URILOHU (UURU 35) IDWDO HUURU FRPPRQ FDQQRW UHDG H[SHFWHG QXPE
Profiler Errors PRF1005 through PRF4642 Page 2 of 7 IDWDO HUURU FRPPRQ ILOH ILOHQDPH KDV DQ LQFRUUHFW ROG VLJQDWXUH $ 3%, 3%2 3%7 B;( RU B// ILOH GRHV QRW FRQWDLQ WKH FRUUHFW KHDGHU E\WHV 3HUKDSV WKH ILOH LV FRUUXSWHG RU ZDV FUHDWHG E\ DQ ROG YHUVLRQ RI WKH SURILOHU 3URILOHU (UURU 35) IDWDO HUURU FRPPRQ 3%, ILOH ILOHQDPH KDV DQ LQFRUUHFW ROG YHUVLRQ QXPEHU $ 3%, ILOH GRHV QRW FRQWDLQ WKH FRUUHFW YHUVLRQ QXPEHU 3HUKDSV WKH ILOH LV FRUUXSWHG RU ZDV FUHDWHG E\ DQ ROG YHUVLRQ RI
Profiler Errors PRF1005 through PRF4642 Page 3 of 7 3URILOHU (UURU 35) IDWDO HUURU 35(3 , ILOHQDPH LQYDOLG UXQWLPH UHORFDWLRQ WU\ UHOLQN 7KH SURILOHU IRXQG EDG UHORFDWLRQ LQIRUPDWLRQ LQ WKH SURJUDP WR EH SURILOHG 7KLV LV XVXDOO\ FDXVHG E\ XVLQJ DQ REVROHWH YHUVLRQ RI WKH OLQNHU 5HOLQN \RXU FRGH ZLWK WKH QHZ SURILOHU DQG UXQ 35(3 DJDLQ 3URILOHU (UURU 35) $ IL[HG LPDJH H[HFXWDEOH FDQQRW EH SURILOHG UHOLQN ILOH ZLWKRXW WKH IL[HG VZLWFK 3URILOHU (UURU 35) ([HFXWDEOH LPDJH WRR ODUJH
Profiler Errors PRF1005 through PRF4642 Page 4 of 7 WKH LQFRPLQJ 3%7 RU 3%2 ILOHV $OO SURILOHU VWHSV PXVW EH UXQ RQ WKH VDPH W\SH RI FRPSXWHU 3URILOHU (UURU 35) IDWDO HUURU 3/,67 RSWLRQ LQFRQVLVWHQW ZLWK VRUWLQJ W\SH 7KH RSWLRQV IRU 3/,67 GHSHQG RQ WKH NLQG RI SURILOLQJ EHLQJ GRQH 7KLV HUURU RFFXUV IRU H[DPSOH ZKHQ WKH 6RUW %\ 1DPH RSWLRQ LV VSHFLILHG IRU D OLQH SURILOLQJ UXQ 3URILOHU (UURU 35) IDWDO HUURU 35(3 RU 352),/( DEQRUPDO WHUPLQDWLRQ LQ 35(3 RU 352),/( GHWHFWHG 3/,67
Profiler Errors PRF1005 through PRF4642 Page 5 of 7 IDWDO HUURU 352),/( 1W6HW,QWHUYDO3URILOH 17 LQWHUQDO HUURU QXPEHU RFFXUUHG $ :LQGRZV 17 HUURU ZDV GHWHFWHG 3URILOHU (UURU 35) IDWDO HUURU 352),/( IXQFWLRQ VDPSOLQJ LV QR ORQJHU VXSSRUWHG )XQFWLRQ VDPSOLQJ LV QRW VXSSRUWHG LQ WKLV YHUVLRQ 8VH IXQFWLRQ WLPLQJ WR JHW PRUH DFFXUDWH UHVXOWV 3URILOHU (UURU 35) IDWDO HUURU 35(3 , QR GHEXJJLQJ LQIRUPDWLRQ LQ ILOH ILOHQDPH /LQH SURILOLQJ RQO\ GHEXJJLQJ LQIRUPDWLRQ PXVW EH LQFOXGH
Profiler Errors PRF1005 through PRF4642 Page 6 of 7 FRYHUDJH SURILOLQJ 3URILOHU (UURU 35) ZDUQLQJ FRPPRQ QR HUURU ILOH ( VSHFLILHG IRU $ RSWLRQ 7KH $ RSWLRQ FDQQRW EH XVHG ZLWKRXW WKH ( RSWLRQ 7KH $ RSWLRQ LV LJQRUHG DQG WKH HUURU RXWSXW VHQW WR VWGRXW 3URILOHU (UURU 35) ZDUQLQJ 35(3 , DQ RIIVHW GXSOLFDWLRQ ZDV GHWHFWHG 7KHUH DSSHDUV WR EH D SUREOHP ZLWK WKH FRGHYLHZ OLQH QXPEHU GHEXJ LQIRUPDWLRQ 3HUKDSV WKHUH LV DQ DOLDVLQJ SUREOHP 3URILOHU (UURU 35) ZDUQLQJ
Profiler Errors PRF1005 through PRF4642 Page 7 of 7 35(3 FRXOG QRW ILQG WKH VSHFLILHG VWDUW IXQFWLRQ HQWU\ IXQFWLRQ LQ WKH PDSILOH VHH 6) VZLWFK 3HUKDSV WKH IXQFWLRQ QDPH LV PLVVSHOOHG 3URILOHU (UURU 35) ZDUQLQJ 35(3 , FDQQRW SURILOH IXQFWLRQ IXQFWLRQ LQ ILOH ILOHQDPH $ VSHFLDO IXQFWLRQ VXFK DV VHWMPS ZDV VSHFLILHG 3URILOHU (UURU 35) ZDUQLQJ 35(3 , PRGXOH PRGXOH DOUHDG\ LQFOXGHV SURILOHU '// ILOHQDPH 7KH VSHFLILHG (;( RU '// DOUHDG\ LPSRUWV IURP 352),/(5 '// 7KH (;( RU '//
Resource Compiler Messages Page 1 of 24 Resource Compiler Messages-RCn The following topics cover Resource Compiler Errors RC1000 through Warning RC4413: l l l l Resource Compiler Errors RC1000 through RC1208 Resource Compiler Errors RC2001 through RC2129 Resource Compiler Errors RC2130 through RC2236 Resource Compiler Warnings RC4000 through RC4413 For information about Resource Compiler RWxxxx messages, see: l Resource Compiler Messages (RWxxxx) Resource Compiler Errors RC1000 through RC1208 The foll
Resource Compiler Messages Page 2 of 24 The specified option is not valid. Resource Compiler Fatal Error RC1008 no input file specified One or more source files must be specified on the Resource Compiler command line. Resource Compiler Fatal Error RC1009 compiler limit : macros too deeply nested m ’ acro’ The Resource Compiler limit for macro nesting was exceeded. Revise the specified source file to decrease the nesting depth of its macros.
Resource Compiler Messages Page 3 of 24 Resource Compiler Fatal Error RC1018 unexpected ’#elif’ The #elif directive did not appear within an #if, #ifdef, or #ifndef construct. Make sure that there is an #if, #ifdef, or #ifndef statement in effect before this statement. Resource Compiler Fatal Error RC1019 unexpected ’#else’ The #else directive did not appear within an #if, #ifdef, or #ifndef construct. Make sure that there is an #if, #ifdef, or #ifndef statement in effect before this statement.
Resource Compiler Messages Page 4 of 24 The program exceeded the maximum allowable nesting levels for #if and #ifdef directives. This error can be caused by include files that use these preprocessor directives. Resource Compiler Fatal Error RC1067 compiler limit : identifier overflowed internal buffer An internal compiler limit was exceeded. Resource Compiler Fatal Error RC1101 no resource binary filename specified The Rename Output (/fo) option was specified, but was not followed by filename.
Resource Compiler Messages Page 5 of 24 Resource Compiler Fatal Error RC1110 could not open filename RC could not open the specified resource script file. Make sure that the file exists. Resource Compiler Fatal Error RC1116 RC terminating after preprocessor errors The Resource Compiler halted due to other errors. Fix the other errors and recompile. Resource Compiler Fatal Error RC1120 out of memory, needed number bytes The Resource Compiler ran out of storage for items that it stores in its heap.
Resource Compiler Messages Page 6 of 24 The Specify Default Language (/l) option was specified, but was followed by an invalid hexadecimal language ID. See the Platform SDK for a list of valid language IDs. Resource Compiler Fatal Error RC1204 Invalid switch - missing code page after /c The Specify Code Page (/c) option was specified, but it was not followed by a code page.
Resource Compiler Messages Page 7 of 24 expected ’defined(id)’ An identifier was expected after the left parenthesis following the specified preprocessing keyword. Resource Compiler Error RC2005 #line expected a line number, found t’oken’ A #line directive lacked the required line-number specification. Resource Compiler Error RC2006 #include expected a filename, found token’ ’ An #include directive lacked the required filename specification.
Resource Compiler Messages Page 8 of 24 Resource Compiler Error RC2017 illegal escape sequence An escape sequence appeared where one was not expected. An escape sequence - a backslash ( \ ) followed by a number or letter - may occur only in a character or string constant. Resource Compiler Error RC2018 unknown character ’hexnumber’ The ASCII character corresponding to the given hexadecimal number appeared in the source file but is an illegal character.
Resource Compiler Messages Page 9 of 24 the file that contains the offending #pragma directive may not be immediately obvious. The #ifndef RC_INVOKED technique can control including header files in project-based header files. Resource Compiler Error RC2102 string literal too long An RCDATA string exceeded the maximum allowable length. Resource Compiler Error RC2103 unexpected end of file in string literal An end of file was found before the end of a string.
Resource Compiler Messages Page 10 of 24 AUTOCHECK, AUTORADIO, BEDIT, CHECKBOX, COMBOBOX, CONTROL, CTEXT, DEFPUSHBUTTON, EDITTEXT, GROUPBOX, HEDIT, ICON, IEDIT, LISTBOX, LTEXT, PUSHBOX, PUSHBUTTON, RADIOBUTTON, RTEXT, SCROLLBAR, USERBUTTON. Make sure these CONTROL statements are spelled correctly. Resource Compiler Error RC2112 BEGIN expected in dialog The BEGIN keyword must immediately follow the DIALOG keyword.
Resource Compiler Messages Page 11 of 24 Resource Compiler Error RC2121 BEGIN expected in menu The BEGIN keyword must immediately follow the MENU keyword. Resource Compiler Error RC2122 unknown menu subtype The item-definition field of the MENU statement can contain only MENUITEM and POPUP statements. Resource Compiler Error RC2123 END expected in menu The END keyword must come at the end of a MENU statement.
Resource Compiler Messages Page 12 of 24 #line expected a string containing the file name, found token’ ’ A #line directive was missing a required filename. Resource Compiler Error RC2131 expecting quoted string for key The field for this statement must be a character string enclosed in double quotation marks. Resource Compiler Error RC2132 expected VALUE, BLOCK, or, END keyword A block in a VERSION resource doesn’t end properly, or a new block doesn’t begin properly.
Resource Compiler Messages Page 13 of 24 A CHARACTERISTICS resource must be a number. Resource Compiler Error RC2141 invalid type A different type was expected. Resource Compiler Error RC2142 ellipsis requires three periods An incorrect number of periods (.) was used in an ellipsis. Resource Compiler Error RC2143 font names must be ordinals The pointsize field in the FONT statement must be an integer, not a string.
Resource Compiler Messages Page 14 of 24 Resource Compiler Error RC2151 cannot re-use string constants You are using the same value twice in a STRINGTABLE statement. Make sure you are not mixing overlapping decimal and hexadecimal values. Each ID in a STRINGTABLE must be unique. For maximum efficiency use contiguous constants that start on a multiple of 16. Resource Compiler Error RC2152 invalid control character A control character in the ACCELERATORS statement is invalid.
Resource Compiler Messages Page 15 of 24 expected macro formal parameter The token following a stringizing operator (#) was not a formal parameter name. Resource Compiler Error RC2163 accelerator type required [ASCII or VIRTKEY] The type field in the ACCELERATORS statement must contain either the ASCII or VIRTKEY value. Resource Compiler Error RC2164 unexpected value in RCDATA The raw-data values in the RCDATA statement must be integers or strings, each separated by a comma.
Resource Compiler Messages Page 16 of 24 Resource Compiler Error RC2175 resource file filename is not in 3.00 format The specified resource used a format earlier than version 3.00. The resource file must be converted or recreated using the format for version 3.00 or later. Resource Compiler Error RC2176 old DIB in filename. An old format Device Independent Bitmap was found in the specified file. It should be converted to the current format.
Resource Compiler Messages Page 17 of 24 Resource Compiler Warning RC4002 too many actual parameters for macro ’identifier’ The number of actual parameters specified with the given identifier was greater than the number of formal parameters given in the macro definition of the identifier. The additional actual parameters were collected but ignored during expansion of the macro.
Resource Compiler Messages Page 18 of 24 Check the syntax of the line containing the specified token. Resource Compiler Warning RC4093 unescaped newline in character constant in inactive code The constant expression of an #if, #elif, #ifdef, or #ifndef preprocessor directive evaluated to zero, making the code that follows inactive. Within that inactive code, a newline character appeared within a set of single or double quotation marks.
Resource Compiler Messages Page 19 of 24 The type of specified file is not known to the Resource Compiler. It was compiled as an 8-bit ASCII file. Return to Main Resource Compiler Messages Page Resource Compiler Errors RW1004 through RW4004 The following topics cover Resource Compiler Errors RW1004 through RW4004: Resource Compiler Fatal Error RW1004 Unexpected end of file This error can be caused by omitting the linefeed and carriage-return characters on the last line of a text file.
Resource Compiler Messages Page 20 of 24 Resource Compiler Fatal Error RW1030 Output Error The output error can be caused by any of following conditions: l Errors occurred when linking file l l l l l l LINK failed. See Set Linker Options and Linker Reference for more information about linking an executable. .EXE file too large; relink with higher /ALIGN value f the .EXE file is larger than 800K, you should use the /ALIGN:32 value on your LINK line. File not created by LINK You must create the .
Resource Compiler Messages Page 21 of 24 l Accelerator type required (ASCII or VIRTKEY) l l l l l l l l l l l l l l l l The type field in the ACCELERATORS statement must contain either the ASCII or VIRTKEY value. BEGIN expected in accelerator table The BEGIN keyword must immediately follow the ACCELERATORS keyword. BEGIN expected in dialog The BEGIN keyword must immediately follow the DIALOG keyword. BEGIN expected in menu The BEGIN keyword must immediately follow the MENU keyword.
Resource Compiler Messages Page 22 of 24 you have used a #define constant to specify the value and that the constant is spelled correctly. l Expected numeric constant in string table l l l l l l l l l l l l l l l A numeric constant, defined in a #define statement, must immediately follow the BEGIN keyword in a STRINGTABLE statement. Expected numeric point size The pointsize field of the FONT option in the DIALOG statement must be an integer point size value.
Resource Compiler Messages Page 23 of 24 have a #define statement for the control. l Mismatched parentheses Make sure you have closed every open parenthesis in the DIALOG statement. l Unexpected value in RCData The raw-data values in the RCDATA statement must be integers or strings, each separated by a comma. Make sure you did not leave out a comma or leave out a quotation mark around a string.
Resource Compiler Messages Page 24 of 24 Resource Compiler Warning RW4004 ASCII character not equivalent to virtual key code A string literal was used for the virtual key code in a VIRTKEY type accelerator. This warning lets you continue, but be aware that the accelerator keys generated may not match the string you indicated. (VIRTKEYs use different key codes than ASCII accelerators.
