Al.exe Tool Errors and Warnings
The following table lists the errors generated by Al.exe.
| Error | Description |
|---|---|
| al1001 | Internal compiler error
Try to determine whether Al.exe is failing because of its inability to parse unexpected syntax. Then, contact Microsoft Product Support Services. |
| al1002 | Out of memory
Al.exe ran out of memory and halted. Increase the amount of available memory. |
| al1003 | Compiler option 'option' must be followed by an argument
Al.exe expected an argument to be passed to a command-line option. For example, if you specify /algid:, you must pass an algorithm identifier. |
| al1004 | Unexpected common language runtime initialization error — 'reason'
Al.exe reported an error with the Visual Studio or common language runtime installation for the specified reason. |
| al1005 | File 'file' too big to open
All files opened by Al.exe must be smaller than 4 gigabytes (GB). |
| al1006 | Response file 'file' was already included
The same response file was specified (@file) more than once on the command line. The response file can only be included once. |
| al1007 | Error opening response file 'file' — 'reason'
Al.exe cannot open the specified response file for the specified reason. |
| al1008 | Missing file specification for 'option' command-line option
Al.exe expected a file to be passed to a command-line option. For example, if you specify the /out option, you must specify a file. |
| al1009 | Can't open 'file' for writing
Al.exe was unable to write to a file, such as the output assembly file. The disk might be full, the file might be read-only, or you might not have access rights to the file. |
| al1010 | Command-line syntax error: Missing ':text' for 'option' option
Al.exe expected an argument to be passed to a command-line option. For example, if you specify the /title option, you must pass a string. |
| al1011 | File 'file' is an executable file and cannot be opened as a text file
A binary file was specified where a text file was expected. For example, this error occurs if a binary file is passed on the command line as a response file. |
| al1012 | 'value' is not a valid setting for option 'option'
An unexpected value was passed to a command-line option. For example, this error occurs if you specify an invalid value to the /target option. |
| al1013 | Unrecognized command-line option: 'option'
An invalid command-line option was specified. |
| al1014 | Unexpected initialization error — 'reason'
Al.exe detected a COM initialization failure. This might be caused by a lack of memory, but a more likely cause is your system DLL files. You should see a similar error if you run any Automation-aware or COM-aware program, such as Microsoft Visual Studio. Reinstall your operating system. |
| al1015 | Unable to find messages file 'alinkui.dll'
Al.exe requires Alinkui.dll. Make sure that this file is on your path. If necessary, copy it from the product CD. |
| al1016 | No valid input files were specified
Al.exe requires one or more input files that do not have assembly information. |
| al1017 | No target filename was specified
A command-line option was specified without a file parameter. For example, this error occurs if you specify /keyname:. |
| al1018 | Required file 'file' could not be loaded
Certain DLL files cannot be loaded. Reinstall Visual Studio or the Microsoft .NET Framework SDK. |
| al1019 | Metadata failure while creating assembly — reason
Generation of the assembly was interrupted for the specified reason. For example, this error occurs if a file that you specify with the /win32res option is not found. |
| al1020 | Ignoring included assembly 'file'
An input file that contained an assembly was specified. Al.exe input files cannot contain assemblies. |
| al1021 | 'setting' : overriding previous setting
A module had a value for a particular setting, possibly assigned through custom attributes, which was overridden with a value passed using an Al.exe command-line option. |
| al1022 | Error reading embedded resource 'file' — reason
Al.exe cannot read the file passed to the /embedresource option for the specified reason. |
| al1023 | Error embedding resource 'file' — reason
The operating system cannot embed the resource file in the assembly for the specified reason. |
| al1025 | ComType record 'record' points to an invalid file record 'record'
Metadata in the input module is invalid. The tool that produced the module must be fixed. |
| al1026 | The version specified 'version' is invalid
See information on the /version option for valid formats. |
| al1028 | Key file 'file' is missing the private key needed for signing
A key file that contains only the public key was passed to the /keyfile option. Use the Strong Name Tool (Sn.exe) to generate a file with both a public and private key, as shown in the following command. |
| al1029 | The key container name 'container' does not exist
The value passed to the /keyname option is not a valid container. Use the Strong Name Tool (Sn.exe) to create a container. |
| al1030 | The cryptographic service is not installed properly or does not have a suitable key provider
You might need to either reinstall your operating system or install some cryptographic utility that was used in the creation of the key. |
| al1031 | Error reading icon 'file' — reason
Al.exe cannot read the file that was passed to the /win32icon option for the specified reason |
| al1032 | Error generating resources for 'file' — reason
Al.exe cannot create a file due to insufficient disk space or some other error. This error occurs when you specify the /win32icon option (which generates an .ico file) or do not specify the /win32res option (which generates a file with resource information). If you cannot resolve the file generation problem, use /win32res, which specifies a file that can contain version or bitmap (icon) information. |
| al1033 | Assembly custom attribute 'attribute' was specified multiple times with different values
Different values were passed to two occurrences of the same custom attribute in source modules that are specified as input to Al.exe. |
| al1034 | Assembly 'file' cannot be copied or renamed
While using the Al.exe syntax that allows you to both specify an input file and copy it, a name conflict arose that stopped the compiler. For example, this error occurs if you specify |
| al1035 | Libraries cannot have an entry point
You cannot specify both the /target:lib option (the default) and the /main option. |
| al1036 | Entry point required for executable applications
When using the /target:exe or /target:win option, you must also specify the /main option. |
| al1037 | Unable to find the entry point method 'main'
Al.exe cannot find a Main method at the location specified by the /main option. |
| al1039 | Initialization of global assembly cache manager failed — reason
Reinstall Visual Studio or the .NET Framework SDK. |
| al1040 | Failed to install assembly into cache — reason
Only signed assemblies can be installed into the cache. See Global Assembly Cache for more information. |
| al1041 | 'method': cannot be the entry point because the signature or visibility is incorrect
A method was specified with the /main option, but that method is not static, does not return int or void, or has invalid arguments. |
| al1042 | 'exe': EXEs cannot be added modules
An .exe file that does not have an assembly was specified as an input file to Al.exe. Al.exe can only take .dll files without assemblies as input files. |
| al1043 | Manifest file name 'name' cannot be the same as any modules
The name specified with the /out option cannot be the same as any of the file names that are specified as input to Al.exe. |
| al1044 | Error reading key file 'file' — reason
An error occurred while opening or reading from a file specified with /keyfile or the AssemblyKeyFileAttribute. |
| al1045 | Filename 'file' is too long or invalid
A file name longer than 260 characters was passed to Al.exe. Choose a file name with fewer characters or a shorter path, or rename the file. |
| al1046 | Resource identifier 'ID' has already been used in this assembly
Two resources, embedded or linked, have the same identifier or name (the second argument). Remove or rename one of the conflicting resources. |
| al1047 | Error importing file 'file' — reason
A module file cannot be opened for the specified reason. |
| al1048 | Error importing module 'module' of assembly 'assembly' — reason
An error occurred when opening a nonmanifest file of a multifile assembly. This error is not emitted directly by Al.exe, but can be passed programmatically to a process that uses Al.exe. |
| al1049 | Cannot auto-generate build and revision version numbers for dates previous to January 1, 2000
The system clock on your computer is set to a date earlier than January 1, 2000. |
| al1050 | The feature you are using 'old feature' is no longer supported; please use 'new feature' instead
A feature previously supported by Al.exe is now obsolete. Use the recommended feature instead. |
| al1051 | Error emitting 'attribute' attribute —'reason'
An assembly custom attribute was not processed by Al.exe for the specified reason. |
| al1052 | File 'filename' is not an assembly
The file specified with /template must contain assembly metadata. This error indicates that the file specified by /template did not contain an assembly. |
| al1053 | The version 'version' specified for the 'option' is not in the normal 'major.minor.build.revision' format
Al.exe detected ill-formed version information specified with the /fileversion or /productversion options. |
| al1054 | The version 'version' specified for the 'option' is not in the normal 'major.minor.build.revision' format
Al.exe detected ill-formed version information specified with the SatelliteContractVersionAttribute. |
| al1055 | Referenced assembly 'filename' does not have a strong name
This error is issued when you are building an assembly with a strong name and reference an assembly that does not have a strong name. If an assembly has a strong name, it can be installed in the global assembly cache. Consequently, referenced assemblies would also need to go into the global assembly cache. Only assemblies with strong names can go into the global assembly cache. |
| al1056 | Referenced assembly 'filename' is a localized satellite assembly
An assembly created using the AssemblyCultureAttribute attribute was referenced in the creation of the current assembly. The AssemblyCultureAttribute attribute indicates the file is a localized satellite assembly and it is not normal to reference a satellite assembly. You should probably reference the main parent assembly instead. |
| al1057 | Executables cannot be localized, Culture should always be empty
An assembly is being created with /target:exe but /culture was specified. Assemblies in the .exe cannot have information in the Culture field. |
| al1058 | 'file' is an assembly and cannot be added as a module
In a C++ compilation, /assemblymodule (linker option) was passed a file that contained an assembly. |
| al1059 | Unknown error (code)
Al.exe received an unknown error code (code). Possible solutions include:
|
| al1060 | Cryptographic failure while creating hashes — reason
An error occurred while creating the file hashes for a multifile assembly. |
| al1061 | Cannot set option 'option' because 'reason'
The value specified for this option is invalid for the specified reason. |
| al1062 | Module 'module' was specified multiple times; it will only be included once
This warning is generated when the same source, input, or module file is specified multiple times on the command line. Make sure you specify the file name only once. |