Article ID: 816002
Article Last Modified on 10/11/2005
APPLIES TO
- Microsoft Message Queuing 2.0
SYMPTOMS
When you renew a cryptographic key on a Microsoft Windows NT 4.0-based Primary Site Controller (PSC) in a Microsoft Message Queuing environment, the renewed key is not replicated to other PSC computers in the enterprise. Because the key is not replicated, the PSC where you renewed the cryptographic key is not synchronized with the enterprise.
CAUSE
This problem occurs when you upgrade a Windows NT 4.0-based Primary Enterprise Controller (PEC) to a Microsoft Windows 2000 Server-based domain controller that runs the Message Queuing service. When the Message Queuing Replication service retrieves the key from the Active Directory directory service, the service does not correctly format the key and replicates raw data to other PSC computers in the enterprise.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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 tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------------- 05-Mar-2003 22:31 5.0.0.766 281,360 Mq1repl.dll 04-Feb-2003 15:51 5.0.0.766 14,096 Mq1sync.exe 19-Feb-2003 17:21 5.0.0.769 75,408 Mqac.sys 05-Mar-2003 22:31 5.0.0.771 217,360 Mqads.dll 30-Oct-2002 16:43 5.0.0.761 25,360 Mqbkup.exe 05-Mar-2003 22:31 5.0.0.750 76,560 Mqdscli.dll 05-Mar-2003 22:31 5.0.0.770 41,744 Mqdssrv.dll 21-Oct-2002 20:31 5.0.0.759 98,064 Mqmig.exe 05-Mar-2003 22:31 5.0.0.759 265,488 Mqmigrat.dll 05-Mar-2003 22:31 5.0.0.740 222,480 Mqoa.dll 05-Mar-2003 22:31 5.0.0.762 8,464 Mqperf.dll 05-Mar-2003 22:31 5.0.0.771 427,280 Mqqm.dll 05-Mar-2003 22:31 5.0.0.765 102,672 Mqrt.dll 05-Mar-2003 22:31 5.0.0.759 70,928 Mqsec.dll 05-Mar-2003 22:31 5.0.0.769 400,656 Mqsnap.dll 05-Mar-2003 22:31 5.0.0.762 23,824 Mqupgrd.dll 05-Mar-2003 22:31 5.0.0.767 110,352 Mqutil.dll 05-Mar-2003 22:31 5.0.0.748 64,784 Msmq.cpl
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
Additional query words: MSMQ
Keywords: kbbug kbfix kbqfe kbwin2000presp5fix kbhotfixserver KB816002
