Microsoft KB Archive/262297

= PRB: COM AppID Mapping Must Include Both Long and Short File Names of COM .exe Servers =

Article ID: 262297

Article Last Modified on 2/12/2007

-

APPLIES TO


 * Microsoft Windows 95
 * Microsoft Windows 98 Standard Edition
 * Microsoft Windows 98 Second Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows 2000 Standard Edition

-



This article was previously published under Q262297



SYMPTOMS
A Component Object Model (COM) application that has a long file name may not see the run-time configuration (Access permission) that is set under the &quot;AppID&quot; section.



CAUSE
COM uses the module name to find the .exe-to-AppID mapping that is used to locate the AppID settings in the registry. If the .exe file name is a long file name, and if the module name is the short form, the runtime does not find these settings.



RESOLUTION
You must include .exe-to-AppID mappings for both the long and the short file names.



STATUS
This behavior is by design.



MORE INFORMATION
In most cases, when you register a COM .exe file, the short file name is put in the registry. For example, Active Template Library (ATL) applications and Microsoft Foundation Classes (MFC) applications mostly register .exe file with the short file name in the registry. However, if you start the application manually, the long file name of the application may be used. Therefore, depending on which .exe-Name-AppID mapping is present in the registry, the application-specific COM configuration may or may not be picked up.

