PRB: Incorrect Type Name Causes Problems Using Resource Types

ID: Q182658

The information in this article applies to:

• Microsoft Win32 Software Development Kit (SDK)
• Microsoft Windows NT Server Enterprise Edition version 4.0

SYMPTOMS

If you register a resource type DLL with the cluster using a different type name than you specify in the DLL itself, you might experience one or more of the following problems:

• The Cluster Administrator reports that an error occurred trying to read the properties of the resource type.
• The Administrator extension for the DLL cannot be registered because the type name is not found.

   The system cannot find the file specified.

   The data is invalid.

CAUSE

Because a resource type DLL can support more than one resource type, the name of the resource type is supplied to the DLL upon startup. If the name is not recognized, you may write the DLL so that the startup will fail.

In the case of the extension DLL, it looks explicitly for the type name supplied when the DLL was created.

RESOLUTION

Make sure the type name used to register a resource type and the type name used internally in the DLL match.

STATUS

This behavior is by design.

Additional query words:

Keywords          : kbcluster 
Version           : WINNT:4.0
Platform          : winnt
Issue type        : kbprb
Solution Type     : kbnofix

Last Reviewed: June 10, 1998