Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Message Queuing service freezes when queue size increases in Windows Server 2008 SP2 or Windows Server 2008 R2

Message Queuing service freezes when queue size increases in Windows Server 2008 SP2 or Windows Server 2008 R2

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install Microsoft Message Queuing (also known as MSMQ) 4.0 on a computer that is running Windows Server 2008 Service Pack 2 (SP2). Or you install MSMQ 5.0 on a computer that is running Windows Server 2008 R2.
  • Message Queuing deployment uses one or more of the following cache-related registry entries:
    • CryptReceiveKeyCacheSize
    • CryptSendKeyCacheSize
    • CertInfoCacheSize
    • QmPbKeyCacheSize
    • UserCacheSize
  • The cache size increases to a value that exceeds the limit for the cache in use.
In this scenario, the Message Queuing service freezes.

Notes
  • Information about the CryptReceiveKeyCacheSize registry entry:
    Registry PathHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
    Data TypeREG_DWORD
    Range0x0–0xFFFFFFFF (keys)
    Default Value0x7F (127)
    DescriptionDetermines the maximum number of symmetric encryption keys that are found in incoming messages that can be stored in the cryptographic key cache on the receiving server.
  • Information about the CryptSendKeyCacheSize registry entry:
    Registry PathHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
    Data TypeREG_DWORD
    Range0x0–0xFFFFFFFF (keys)
    Default Value0x35 (53)
    DescriptionDetermines the maximum number of outgoing symmetric encryption keys that can be stored in the cryptographic key cache on the sending server.
  • Information about the CertInfoCacheSize registry entry:
    Registry PathHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
    Data TypeREG_DWORD
    Range0x0–0xFFFFFFFF (certificates)
    Default Value0x35 (53)
    DescriptionDetermines the maximum number of certificates stored in the certificate cache, which stores information about certificates found in incoming messages. This cache helps Message Queuing authenticate incoming messages more quickly.
  • Information about the QmPbKeyCacheSize registry entry:
    Registry PathHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
    Data TypeREG_DWORD
    Range0x0–0xFFFFFFFF (keys)
    Default Value0x35 (53)
    DescriptionDetermines the maximum number of keys that can be stored in the queue manager (QM) public encryption key cache. This cache stores public encryption keys recently used in replication and notification messages.
  • Information about the UserCacheSize registry entry:
    Registry PathHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
    Data TypeREG_DWORD
    Range0x0–0xFFFFFFFF (entries)
    Default Value0xFD (253)
    DescriptionDetermines the maximum number of entries that can be stored in the user account information cache. This cache stores information about users who recently sent messages to the computer.

↑ Back to the top

Cause

This issue occurs because of an incorrect partition algorithm. The cache is full at some point during the operation. At this point, half of the keys in the cache have to be deleted to make space for new keys. The oldest keys are deleted first. Therefore, a partition algorithm is invoked for the median time-stamped key partition. However, the partition algorithm goes into an infinite loop.

↑ Back to the top

Resolution

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:
http://support.microsoft.com/contactus/?ws=support
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 Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.

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

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

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, 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 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
    2.
    23xxx    		Windows Server 2008SP2LDR
  • 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" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to 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
File nameFile versionFile sizeDateTimePlatform
Mqqm.dll6.0.6002.23078931,32819-Mar-201302:54x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Mqqm.dll6.0.6002.230781,520,12819-Mar-201303:47x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Mqqm.dll6.0.6002.230783,009,53619-Mar-201302:27IA-64
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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.1.760
    1.
    22xxx    		Windows Server 2008 R2SP1LDR
  • 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 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Mqqm.dll6.1.7601.223171,517,56804-May-201305:17x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Mqqm.dll6.1.7601.223173,014,14404-May-201304:25IA-64

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about Message Queuing, go to the following Microsoft website:
General information about Message Queuing service
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 Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_66c75275702bd84953359bfb3249499e_31bf3856ad364e35_6.0.6002.23078_none_54a83bc25cc9dac8.manifest
File versionNot applicable
File size710
Date (UTC)19-Mar-2013
Time (UTC)23:19
PlatformNot applicable
File nameX86_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.0.6002.23078_none_81e43237760f3c57.manifest
File versionNot Applicable
File size9,378
Date (UTC)19-Mar-2013
Time (UTC)03:17
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_8681969e37cd73919178b620a5604794_31bf3856ad364e35_6.0.6002.23078_none_e918e4cb2e913cb7.manifest
File versionNot applicable
File size714
Date (UTC)19-Mar-2013
Time (UTC)23:19
PlatformNot applicable
File nameAmd64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.0.6002.23078_none_de02cdbb2e6cad8d.manifest
File versionNot applicable
File size9,706
Date (UTC)19-Mar-2013
Time (UTC)04:03
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_948305207f49e4adfb674e99b2e8c92e_31bf3856ad364e35_6.0.6002.23078_none_9eded3c3f250b500.manifest
File versionNot applicable
File size712
Date (UTC)19-Mar-2013
Time (UTC)23:19
PlatformNot applicable
File nameIa64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.0.6002.23078_none_81e5d62d760d4553.manifest
File versionNot applicable
File size9,684
Date (UTC)19-Mar-2013
Time (UTC)02:39
PlatformNot applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_aaaec215fef8489fc09ea345c89b650c_31bf3856ad364e35_6.1.7601.22317_none_10b347d426f7d614.manifest
File versionNot Applicable
File size714
Date (UTC)04-May-2013
Time (UTC)10:55
PlatformNot Applicable
File nameAmd64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.1.7601.22317_none_de6a6a428f543d67.manifest
File versionNot Applicable
File size2,746
Date (UTC)04-May-2013
Time (UTC)05:50
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,008
Date (UTC)04-May-2013
Time (UTC)10:55
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_e68ab0467ba0bcf067745a18e81baf8b_31bf3856ad364e35_6.1.7601.22317_none_4d534ec19e58f3fc.manifest
File versionNot Applicable
File size712
Date (UTC)04-May-2013
Time (UTC)10:55
PlatformNot Applicable
File nameIa64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.1.7601.22317_none_824d72b4d6f4d52d.manifest
File versionNot Applicable
File size2,744
Date (UTC)04-May-2013
Time (UTC)05:26
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,453
Date (UTC)04-May-2013
Time (UTC)10:55
PlatformNot Applicable

↑ Back to the top

Keywords: kb, kbqfe, kbautohotfix, kbhotfixserver, kbsurveynew, kbexpertiseadvanced, kbfix

↑ Back to the top

Article Info
Article ID : 2829589
Revision : 1
Created on : 1/7/2017
Published on : 6/13/2013
Exists online : False
Views : 206