MSMQ IC Does Not Start if Protected Storage Disabled or Delayed (238953)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server 4.0 SP3
- Microsoft Windows NT Server 4.0 SP4
- Microsoft Windows NT Workstation 4.0 SP3
- Microsoft Windows NT Workstation 4.0 SP4
- Microsoft Windows NT version 4.0 Option Pack
This article was previously published under Q238953 SYMPTOMS
If you disable the Protected Storage service on a computer running Windows NT 4.0 Service Pack 3 or Service Pack 4, and then restart the computer, the Microsoft Message Queue Server Independent Client (MSMQ IC) program may not start automatically.
If you install an application that delays the startup of the Protected Storage service (for example Microsoft SQL Server 7.0), and then restart the computer, the MSMQ IC does not automatically start and an Event Viewer System log entry is generated.
CAUSE
This behavior occurs because the Microsoft CryptoAPI needs the Protected Storage service.
RESOLUTIONWindows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual software update. For information on obtaining the
latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft
Product Support Services. For a complete list of Microsoft Product Support
Services phone numbers and information on support costs, please go to the
following address on the World Wide Web:
To resolve this issue, when a program is delaying the start of the Protected Storage service, you may be able to manually start MSMQ IC since the Protected Storage service was only delayed by the program and not disabled. To do this, follow these steps:
- Click Start, point to Settings, click Control Panel, and then double-click Services.
- Click Protected Storage, and then click Start.
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Modification Type: | Major | Last Reviewed: | 5/14/2003 |
---|
Keywords: | kbbug kbfix kbinterop kbtool kbWinNT4sp6fix KB238953 |
---|
|