When you install a Microsoft SQL Server 2008 service pack or hotfix that tries to update a custom resource DLL, the CLUSCTL_RESOURCE_UPGRADE_DLL control code fails with an "access denied" error message. Therefore, you cannot install the service pack or the hotfix. Additionally, you see an event that is similar to the following in the cluster log:

0000068c.00001370::date & time ERR [RCM] rcm::RcmResControl::DoResourceControl: ERROR_ACCESS_DENIED(5)' because of 'MoveFileEx( currentDllPath.c_str(), oldFileName.c_str(), MOVEFILE_REPLACE_EXISTING | MOVEFILE_COPY_ALLOWED | MOVEFILE_WRITE_THROUGH )'

This problem occurs if the following conditions are true:

• You have a Microsoft SQL Server 2005 database instance installed in a Windows Server 2008 Failover Cluster environment.
• You installed a SQL Server 2008 RTM database instance. The installation process uses resource control to upgrade the SQL Server custom resource DLLs. The DLLs are shared by all instances.
• During the installation, you receive no indication that a restart is required. Therefore, you do not restart the Cluster service or the whole cluster node after the installation.

Note This problem is known to affect SQL Server, but it could affect any product that uses resource control to update a custom resource DLL.

The Windows ClusterResourceControl API is used to update resource type DLLs in a Windows Server 2008 Failover Cluster environment. This API causes the computer to require a restart each time a resource DLL is updated, even if it is not necessary. If the computer is not restarted, the access denied error occurs.

A hotfix is available to resolve this problem. This hotfix resolves the problem for all products that use resource control to update a custom resource DLL.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have the Enterprise edition or the Datacenter edition of Windows Server 2008 installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to change the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Server 2008 note

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

For all supported Itanium-based versions of Windows Server 2008

To work around the issue, you can restart each node of the cluster after each update to custom resource DLLs.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008

For more information about the CLUSCTL_RESOURCE_UPGRADE_DLL control code, visit the following Microsoft Developer Network (MSDN) Web site:For more information about custom resource types, visit the following MSDN Web site:For additional information, click the following article number to view the article in the Microsoft Knowledge Base: