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


The information in this article applies to:

  • Microsoft Windows 95
  • Microsoft Windows 98
  • Microsoft Windows 98 Second Edition
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows 2000
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 "AppID" 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.

REFERENCES

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

246054 INFO: DCOMCNFG and AppID\.exe Mapping and Implication

179690 FIX: Launching COM Server with Long File Name Returns 0x80080005

201318 FIX: Registering ATL Server with Long Name Causes 0x80070002

Modification Type:MinorLast Reviewed:12/21/2004
Keywords:KbClientServer kbDCOM kbprb KB262297
©2004 Microsoft Corporation. All rights reserved.