Article ID: 834467 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
The following two problems are resolved in this hotfix.
Problem 1On a computer that is running Microsoft Windows XP Embedded in domain mode, you cannot modify public queue properties or computer properties if the queue is hosted on a Windows 2000-based computer. You receive the following error message:
"Invalid parameter was passed to a function."
Problem 2If you delete a queue, and then immediately create a queue, you may receive the following error message:
"Queue is not registered in the DS."
Problem 1This problem occurs because the Mqdscli.dll file is not installed on the computer that is running Windows XP Embedded.
Problem 2This problem occurs because Microsoft Message Queuing uses the incorrect interface to modify objects in the Active Directory directory service.
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322389/EN-US/ )How to obtain the latest Windows XP service pack
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart your computer after you apply this hotfix.
File informationThe English version of this hotfix has the file attributes (or later) 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 --------------------------------------------------------------------------------------- 14-Jan-2004 18:53 126.96.36.1992 165,888 Mqrt.dll 14-Jan-2004 18:53 188.8.131.522 115,200 Mqrtdep.dll 14-Jan-2004 18:53 184.108.40.2062 478,208 Mqsnap.dll 14-Jan-2004 18:53 220.127.116.112 154,112 Msmqocm.dll 14-Jan-2004 17:42 18.104.22.168 356,120 Windowsxp-kb834467-x86-enu-symbols.exe 14-Jan-2004 17:43 22.214.171.124 564,504 Windowsxp-kb834467-x86-enu.exe
Problem 1If it is possible, you can copy the Mqdscli.dll file to the %windir%\system32 directory to work around this problem.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
Message Queuing 3.0 can use Active Directory Service Interfaces (ADSI) to access Active Directory or the Directory Service RPC interface, depending on the version of Message Queuing that the client is running. The Windows XP Embedded Active Directory SLD file contains the Mqad.dll file, but it does not contain the Mqdscli.dll file. The Mqdscli.dll file is needed to use the Directory ServiceRPC interface. In domain mode, Message Queuing 3.0 uses the Directory Service RPC interface to the domain controller if the computer that owns the queue is running Windows 2000. This is done to enable "downlevel" notifications to the queue owner when the computer properties or the queue properties have changed because Message Queuing 2.0 can only accept "downlevel" notifications from a domain controller.
Important This hotfix makes the behavior more consistent across the Message Queuing Directory Service APIs. The Message Queuing Directory Service APIs are used to modify objects in the Directory Service over remote procedure calls. The APIs all now check to determine if the host is a downlevel computer and if it will call the Directory Service APIs. This does not mean that the application will not encounter problems because of replication delays. Internally, all Directory Service calls that query for objects always use ADSI. A well-written application must always assume that a Directory Service operation may not be immediately visible because of possible replication delays between domain controllers.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/ )New file naming schema for Microsoft Windows software update packages