After you restart your computer, transactional messages in Microsoft Message Queuing may be purged for any one of the following reasons:
The Local Queue Storage (LQS) files are missing.
The LQS files are inaccessible.
The LQS files are corrupted.
Message Queuing keeps a cache of parameters for local public queues. The cache of parameters for local public queues is named LQS. When you restart your computer to recover packet files, Message Queuing uses this cache to create internal queue objects. If an LQS file is not found for a local public queue, messages are considered "outgoing." When Message Queuing connects to the Active Directory directory service and then finds that the queue is a local public queue, Message Queuing marks the queue object not valid and then purges all messages from the queue.
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 Microsoft 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.
No prerequisites are required.
You must restart your computer after you apply this hotfix.
The 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.
The following issues are addressed in this hotfix:
A problem may occur when building the LQS cache. If there are temporary problems that occur when querying Active Directory, Message Queuing may delete valid LQS files. Message Queuing does not re-create the valid LQS files until you restart your computer. This hotfix makes sure that any error is correctly handled. Also, the hotfix makes sure that the LQS files are not deleted.
When Message Queuing starts and then recovers packet files, Message Queuing uses the LQS cache. Message Queuing does not query the Active Directory directory service. If an LQS file is missing or is inaccessible, the packets and the queue are considered "outgoing." Subsequently, when Message Queuing connects to the Active Directory directory service and then validates the queues, Message Queuing encounters an inconsistency. The inconsistency occurs because the queue is marked "outgoing," but the Active Directory directory service identifies the queue as "local." Therefore, the queue is purged. This has been fixed by using flags for each packet. The flags mark the packet as "local" or "in the target queue." On recovery, if the packets are "local," but the queue object that is created is "outgoing" because of a missing LQS file, Message Queuing marks the queue object as "not consistent." Message Queuing then enters a "non-responsive" mode. Message Queuing will not accept sessions, and the remote procedure call (RPC) interfaces are not started. The Message Queuing service waits to go online and then to re-build the LQS cache.
The following two situations may occur:
The inconsistent queue may be caused by a public queue that has been deleted. Messages may still be in the queue if notification is not received. In this case, the queue is purged, and Message Queuing resumes ordinary operation.
The queue is actually in an inconsistent state. Message Queuing quits, and you have to restart Message Queuing. However, messages are not lost. The Message Queuing service has to quit because of the complexity and the risk that are involved when an "outgoing" queue is converted to a "local" queue.
When an inconsistent state is encountered after you apply this hotfix, the following event may be logged in the event log during recovery:
Description:Unable to recover the persistence packet file and the log file. (Error: Inconsistent queue status. See Microsoft Knowledge Base article 827493 at support.microsoft.com. For more information, see Help and Support Center at http://support.microsoft.com.
A new registry parameter exists that you can use to revert to the old behavior if you are not interested in the messages in the event log. You can use this new registry parameter when you do not want Message Queuing to be in a "non-responsive" mode until Message Queuing finds a domain controller. Create