BUG: Setup of Dependent Client Stops SQL Service (176118)
The information in this article applies to:
- Microsoft Message Queue Server (MSMQ) 1.0
This article was previously published under Q176118 SYMPTOMS
During the installation of a dependent client on a SQL Server, Setup stops
the SQL Server service.
STATUS
Microsoft has confirmed this to be a bug in Microsoft Message Queue Server
version 1.0. We are researching this bug and will post new information here
in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
The installation of dependent clients stops any local SQL Server service.
However, the dependent client does not use or access SQL Server, and should
not be stopping the service. The purpose of this article is to point out
that there will be a brief interruption in the availability of the SQL
Server, and to prevent the misconception that the Message Queue Server
(MSMQ) dependent client depends on or interacts with a local SQL server
installation.
Because MSMQ Setup restarts the SQL Server after installing the MSMQ
client, the user does not have to restart the server. However, other
services that are directly or indirectly dependent on SQL Server may be
stopped by the Service Control Manager, and will not be automatically
restarted afterwards.
Behavior of various applications or services cannot be predicted, so before
installing MSMQ on a dependent client, it is recommended that you stop the
SQL Server and any other applications or services that are using it or that
are dependent on it.
REFERENCES
For more information, search for Message Queue Server at:
| Modification Type: | Major | Last Reviewed: | 11/10/1999 |
|---|
| Keywords: | kbbug kbsetup KB176118 |
|---|
|