Article ID: 326813 - View products that this article applies to.
This article was previously published under Q326813
During the build of a Visual C++ project, you may incorrectly receive the following error message:
Note The actual token number and name ('0A000008' and 'CreateM' respectively in this sample error message) vary from project to project but the linker errors (LNK2020 and LNK1120) are consistent. There are circumstances in which these errors message are correct. For more information, search the Visual C++ documentation for these linker errors.
LINK : error LNK2020: unresolved token (0A000008) CreateM
LINK : fatal error LNK1120: 1 unresolved externals
Because of a bug in the C++ compiler, some programming constructs that involve variable argument lists (...) can create this problem. For example, you receive the error message that appears in the "Symptoms" section when you compile and then link the following code samples:
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Visual Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/837234/ )List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1
Hotfix informationThe English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------------- 24-JUL-2002 01:41 13.0.9521.0 2,105,344 c1xx.dll
Note After you install the hotfix, you must fully rebuild any affected projects to repair the error.
To work around this problem, do not use the variable argument list (...), or change the return type of the function to be a simpler type (not a string or class, as appear in the sample code in the "Cause" section).
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.
Article ID: 326813 - Last Review: 27 September 2005 - Revision: 3.1