Al.exe Tool Errors and Warnings 

al1002

Out of memory

Al.exe ran out of memory and halted. Increase the amount of available memory.

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.

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.

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.

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.

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.

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.

al1016

No valid input files were specified

Al.exe requires one or more input files that do not have assembly information.

al1018

Required file 'file' could not be loaded

Certain DLL files cannot be loaded. Reinstall Visual Studio or the Microsoft .NET Framework SDK.

al1020

Ignoring included assembly 'file'

An input file that contained an assembly was specified. Al.exe input files cannot contain assemblies.

al1022

Error reading embedded resource 'file' — reason

Al.exe cannot read the file passed to the /embedresource option 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.

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.

sn -k keypair.snk.

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.

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.

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 input.dll,somename.dll /out:somename.dll.

al1036

Entry point required for executable applications

When using the /target:exe or /target:win option, you must also specify the /main option.

al1039

Initialization of global assembly cache manager failed — reason

Reinstall Visual Studio or the .NET Framework SDK.

al1041

'method': cannot be the entry point because the signature or visibility is incorrect, or it is generic

A method was specified with the /main option, but that method is not static, does not return int or void, was generic, or has invalid arguments.

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.

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.

al1047

Error importing file 'file' — reason

A module file cannot be opened for the specified reason.

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.

al1051

Error emitting 'attribute' attribute —'reason'

An assembly custom attribute was not processed by Al.exe for the specified reason.

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.

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. To fix this, you need to either regenerate your assembly with a strong name, or attach a strong name to the assembly using sn.exe (see the documentation for sn.exe).

A common occurrence of this error is when you are using COM objects via wrapper assemblies, such as when you add a reference to a COM module to a C# project via the VS IDE. To avoid the error, you can specify the strong name key file for COM wrapper assemblies in the Project Property "Wrapper Assembly Key File/Name"

If you are creating the wrapper assembly via tlbimp, see the tlbimp documentation for information on how to assign a strong name to the wrapper assembly.

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.

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.

al1059

Unknown error (code)

Al.exe received an unknown error code (code).

Possible solutions include:

• Reinstall Visual Studio.

• Reinstall the .NET Framework SDK.

• Check for missing files.

• Check for adequate disk space.

• Check for adequate memory.

• Stop other processes that might be accessing the files.

• Reboot your computer.

al1061

Cannot set option 'option' because 'reason'

The value specified for this option is invalid for the specified reason.

al1063

Public type 'type' is defined in multiple places in this assembly: 'file1' and 'file2'

The same type was found in more than one module within the assembly. Only one version of each type may be present in an assembly.

al1065

File name 'File Name' is too long or invalid

The specified file name is longer than the maximum allowed.

al1067

'filename' is a binary file instead of a text file

The file is in binary format instead of text.

al1069

Cannot create short filename 'filename' when a long filename with the same short filename already exists

The current file has a name that is the short version of a file name that already exists. For example, compiling LongFileName.cs and then recompiling with the name LongFi~1.cs will cause a compiler error similar to this. If the compiler output files with long names were deleted, but the analogous linker files remained, this error could occur.

al1072

Assembly and module 'Module Name' cannot target different processors

You cannot link together an assembly and a module that are targeted for different processors, because the result has to run on a single processor.

al1074

Module name 'Module Name' stored in 'File Name' must match its filename

This is a requirement of the linker. To resolve this problem, make the two names match.

al1076

Type 'type' is forwarded to multiple assemblies: 'assembly' and 'assembly'.

A type can only be forwarded to one assembly.