RPC returns an out-of-memory error incorrectly when you use an RPC over HTTP client to connect to an RPC over HTTP server in Windows Server 2008 or in Windows Vista

Applies to: Windows Server 2008 EnterpriseWindows Server 2008 Enterprise without Hyper-VWindows Server 2008 Datacenter More

Symptoms


Consider the following scenario:
  • You run a remote procedure call (RPC) over HTTP client on a computer that is running Windows Server 2008 or Windows Vista.
  • You use the client to connect to an RPC over HTTP server.
  • The password in the RPC over HTTP credentials that is passed to the RPC over HTTP client is specified as blank.
In this scenario, RPC returns an out-of-memory error incorrectly.

Note This issue typically occurs when the RPC over HTTP client uses a UserTarget credential together with the RpcBindingSetAuthInfoEx function.

For example, consider the following scenario:
  • On a computer that is running Windows Server 2008, Microsoft Outlook tries to connect to Microsoft Exchange Server by using RPC over HTTP.
  • Outlook passes in a blank password in the RPC over HTTP credentials when Outlook tries to execute the RPC call on the Exchange server.
In this scenario, RPC returns an out-of memory-error incorrectly. Therefore, you are prompted multiple times to type credentials for the same account to authenticate with multiple servers.

Resolution


After you install the following hotfix, the RPC over HTTP server considers the scenario as valid if the password field in the RPC over HTTP credentials is blank, and it uses the same set of credentials for authentication.

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 the problem described in this article. 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 website: 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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service SP2
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    0.
    20xxx
    Windows VistaRTMLDR
    6.0.600
    1.
    22xxx
    Windows Vista and Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Rpcrt4.dll6.0.6001.22877785,40812-Mar-201122:25x86
Rpcrt4.dll6.0.6002.22611784,89613-Mar-201101:53x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Rpcrt4.dll6.0.6001.228771,318,40012-Mar-201123:03x64
Rpcrt4.dll6.0.6002.226111,311,23213-Mar-201100:11x64
Rpcrt4.dll6.0.6001.22877677,37612-Mar-201122:26x86
Rpcrt4.dll6.0.6002.22611677,37613-Mar-201101:54x86
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Rpcrt4.dll6.0.6001.228773,304,96012-Mar-201122:42IA-64
Rpcrt4.dll6.0.6002.226113,304,96012-Mar-201123:30IA-64
Rpcrt4.dll6.0.6001.22877677,37612-Mar-201122:26x86
Rpcrt4.dll6.0.6002.22611677,37613-Mar-201101:54x86

Status


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

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size3,577
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameX86_1b4d420b670646c64e2fb6107134cf7d_31bf3856ad364e35_6.0.6002.22611_none_ebe1567058f3f2a1.manifest
File versionNot applicable
File size697
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameX86_42340f0d6dce187593646d82c162368e_31bf3856ad364e35_6.0.6001.22877_none_97e625dd96f97cbc.manifest
File versionNot applicable
File size697
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameX86_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6001.22877_none_b43f9bbe5e645032.manifest
File versionNot applicable
File size28,463
Date (UTC)12-Mar-2011
Time (UTC)22:40
PlatformNot applicable
File nameX86_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6002.22611_none_b660ed585b5f62cd.manifest
File versionNot applicable
File size28,463
Date (UTC)13-Mar-2011
Time (UTC)02:16
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_162341c44cba2f6bc929f5cd05c09d91_31bf3856ad364e35_6.0.6001.22877_none_88c91d0830baa6fa.manifest
File versionNot applicable
File size701
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameAmd64_71de1fa15c5fce2dd05ee28186c8a39a_31bf3856ad364e35_6.0.6001.22877_none_e06546a612afb96c.manifest
File versionNot applicable
File size1,044
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameAmd64_9da6fe7349be0a6ba87839ff9a508e62_31bf3856ad364e35_6.0.6002.22611_none_0614c9e86fb2fec3.manifest
File versionNot applicable
File size1,044
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameAmd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6001.22877_none_105e374216c1c168.manifest
File versionNot applicable
File size28,503
Date (UTC)12-Mar-2011
Time (UTC)23:18
PlatformNot applicable
File nameAmd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6002.22611_none_127f88dc13bcd403.manifest
File versionNot applicable
File size28,503
Date (UTC)13-Mar-2011
Time (UTC)00:25
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,605
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameWow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6001.22877_none_1ab2e1944b228363.manifest
File versionNot applicable
File size26,089
Date (UTC)12-Mar-2011
Time (UTC)22:30
PlatformNot applicable
File nameWow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6002.22611_none_1cd4332e481d95fe.manifest
File versionNot applicable
File size26,089
Date (UTC)13-Mar-2011
Time (UTC)01:58
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_539bb9e6f6c677704a8a12064e97c62f_31bf3856ad364e35_6.0.6001.22877_none_d14369d263798802.manifest
File versionNot applicable
File size699
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameIa64_a355880f11e19398d922af2f2d8e65f2_31bf3856ad364e35_6.0.6001.22877_none_ed15643ea80f6f33.manifest
File versionNot applicable
File size1,042
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameIa64_cce09195035f38281e9f9d6ae46e8727_31bf3856ad364e35_6.0.6002.22611_none_7996cf44dd983f60.manifest
File versionNot applicable
File size1,042
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameIa64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6001.22877_none_b4413fb45e62592e.manifest
File versionNot applicable
File size28,481
Date (UTC)12-Mar-2011
Time (UTC)22:53
PlatformNot applicable
File nameIa64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6002.22611_none_b662914e5b5d6bc9.manifest
File versionNot applicable
File size28,481
Date (UTC)12-Mar-2011
Time (UTC)23:43
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,758
Date (UTC)14-Mar-2011
Time (UTC)15:10
PlatformNot applicable
File nameWow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6001.22877_none_1ab2e1944b228363.manifest
File versionNot applicable
File size26,089
Date (UTC)12-Mar-2011
Time (UTC)22:30
PlatformNot applicable
File nameWow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6002.22611_none_1cd4332e481d95fe.manifest
File versionNot applicable
File size26,089
Date (UTC)13-Mar-2011
Time (UTC)01:58
PlatformNot applicable