Installing Message Queuing (MSMQ)

The following procedures show how to install Message Queuing 4.0 and Message Queuing 3.0.

Message Queuing 4.0 is not available in Windows XP and Windows Server 2003.

To install Message Queuing 4.0 on Windows Server 2008 or Windows Server 2008 R2

In Server Manager, click Features.

In the right-hand pane under Features Summary, click Add Features.

In the resulting window, expand Message Queuing.

Expand Message Queuing Services.

Click Directory Services Integration (for computers joined to a Domain), then click HTTP Support.

Click Next,then click Install.

To install Message Queuing 4.0 on Windows 7 or Windows Vista

Open Control Panel.

Click Programs and then, under Programs and Features, click Turn Windows Features on and off.

Expand Microsoft Message Queue (MSMQ) Server, expand Microsoft Message Queue (MSMQ) Server Core, and then select the check boxes for the following Message Queuing features to install:

MSMQ Active Directory Domain Services Integration (for computers joined to a Domain).

MSMQ HTTP Support.

Click OK.

If you are prompted to restart the computer, click OK to complete the installation.

To install Message Queuing 3.0 on Windows XP and Windows Server 2003

Open Control Panel.

Click Add Remove Programs and then click Add Windows Components.

Select Message Queuing and click Details.

If you are running Windows Server 2003, select Application Server to access Message Queuing.

Ensure that the option MSMQ HTTP Support is selected on the details page.

Click OK to exit the details page, and then click Next. Complete the installation.

If you are prompted to restart the computer, click OK to complete the installation.

Установка системы очередей сообщений (MSMQ) Installing Message Queuing (MSMQ)

В процедурах ниже показана методика установки очереди сообщений 4.0 и очереди сообщений 3.0. The following procedures show how to install Message Queuing 4.0 and Message Queuing 3.0.

Служба очереди сообщений 4,0 недоступна в Windows XP и Windows Server 2003. Message Queuing 4.0 is not available in Windows XP and Windows Server 2003.

Установка Message Queuing 4.0 в Windows Server 2008 или Windows Server 2008 R2 To install Message Queuing 4.0 on Windows Server 2008 or Windows Server 2008 R2

В диспетчер сервера щелкните компоненты. In Server Manager, click Features.

В области справа в разделе Сводка компонентов щелкните Добавить компоненты. In the right-hand pane under Features Summary, click Add Features.

В открывшемся окне разверните очередь сообщений. In the resulting window, expand Message Queuing.

Разверните узел службы очередей сообщений. Expand Message Queuing Services.

Щелкните Интеграция служб каталогов (для компьютеров, присоединенных к домену), а затем щелкните Поддержка HTTP. Click Directory Services Integration (for computers joined to a Domain), then click HTTP Support.

Нажмите кнопку Далее, а затем — установить. Click Next,then click Install.

Установка очереди сообщений 4.0 в Windows 7 или Windows Vista To install Message Queuing 4.0 on Windows 7 or Windows Vista

Откройте Панель управления. Open Control Panel.

Щелкните программы , а затем в разделе программы и компоненты щелкните Включение и отключение компонентов Windows. Click Programs and then, under Programs and Features, click Turn Windows Features on and off.

Разверните сервер очереди сообщений Microsoft (MSMQ), разверните ядро сервера очереди сообщений Microsoft (MSMQ) и затем отметьте флажками установку следующих возможностей очереди сообщений: Expand Microsoft Message Queue (MSMQ) Server, expand Microsoft Message Queue (MSMQ) Server Core, and then select the check boxes for the following Message Queuing features to install:

MSMQ Доменные службы Active Directory (для компьютеров, подключенных к домену). MSMQ Active Directory Domain Services Integration (for computers joined to a Domain).

Поддержка MSMQ HTTP. MSMQ HTTP Support.

Нажмите кнопку ОК. Click OK.

Если появится запрос на перезагрузку компьютера, нажмите кнопку ОК , чтобы завершить установку. If you are prompted to restart the computer, click OK to complete the installation.

Установка Message Queuing 3.0 в Windows XP или Windows Server 2003 To install Message Queuing 3.0 on Windows XP and Windows Server 2003

Откройте Панель управления. Open Control Panel.

Щелкните Добавить удалить программы , а затем — Добавить компоненты Windows. Click Add Remove Programs and then click Add Windows Components.

Выберите очередь сообщений и щелкните сведения. Select Message Queuing and click Details.

Если вы используете Windows Server 2003, выберите сервер приложений для доступа к очереди сообщений. If you are running Windows Server 2003, select Application Server to access Message Queuing.

Удостоверьтесь, что на странице сведений выбрана функция поддержки MSMQ HTTP. Ensure that the option MSMQ HTTP Support is selected on the details page.

Нажмите кнопку ОК , чтобы закрыть страницу сведения, а затем нажмите кнопку Далее. Click OK to exit the details page, and then click Next. Завершите установку. Complete the installation.

Если появится запрос на перезагрузку компьютера, нажмите кнопку ОК , чтобы завершить установку. If you are prompted to restart the computer, click OK to complete the installation.

Не устанавливается служба Message Queuing в Windows XP

Имею:
Машина диспетчерская, для сбора информации со счётчиков электроэнергии.
Windows XP Pro x32 SP3 со всеми последними обновлениями (лицензионка, Downgrade с 7-ки, требовалось для некоторых специфических программ).
Мать ASUS P5P43TD PRO
Процессор Intel Pentium Dual-Core E5300 2,6GH
Оперативы 4(3,25)Gb

Вопрос заключается в следующем:
Изначально не была установлена служба Message Queuing. Впоследствии она потребовалась.
При установке через «Панель Управления-Установка Компонентов Windows» происходит сбой (ошибка 0х42с) при установке Триггеров очереди сообщений (в окне пишет — «Не удаётся запустить службу «MSMQTriggers». Код ошибки: 0х42с. Описание ошибки: Не удалось запустить дочернюю службу.») При этом в «Управление Компьютером-Службы и приложения» подраздела Message Queuing нет. Зато в «Управление Компьютером-Службы и приложения-Службы» как служба появляется Message Queuing, а триггеров нет. Координатор транзакций запущен, все остальные, необходимые для работы Message Queuing службы запущены. Но саму Message Queuing запустить не удаётся. Пишет, что служба была запущена и затем остановлена.
В папке System32 файлы mqsvc.exe и mqtgsvc.exe присутствуют.
Кстати, интересная ситуация: в момент установки, при появлении окна об ошибке 0х42с, служба триггеров в «Управление Компьютером-Службы и приложения-Службы» появляется. При этом установка приостанавливается до момента нажатия на кнопку ОК в окне об ошибке. Но, сразу после нажатия кнопки ОК, служба помечается на удаление и исчезает.

Что можно сделать в данной ситуации для полной установки и запуска службы Message Queuing?

How do I activate Message Queuing in my Windows installation?

How do I activate Message Queuing in my Windows installation in order to use the Windows MSMQ Queue Length sensor?

Last change on Jul 9, 2019 5:45:34 AM by Maike Guba [Paessler Support]

This article applies to PRTG Network Monitor 19 or later

MSMQ Message Queuing

To use the Windows MSMQ Queue Length sensor in PRTG, you need to start the Message Queuing service on both the computer running the PRTG probe and the target system (for example, start services in services.msc).

Message Queuing is only automatically installed on some Windows Server versions. Depending on the Windows version you are using, you have to install the Microsoft Message Queue (MSMQ) Server first.

For details, see the Microsoft article Installing and Managing Message Queuing.
Applies to: Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012, Windows 10, Windows Server 2016

Directory Service Integration

Note: When installing Microsoft Message Queue (MSMQ) Server, make sure you install it including the Directory Service. Depending on your Windows installation, this might have different names, such as

• MSMQ Active Directory Domain Service Integration
• Directory Service Integration
• Active Directory Integration

See sample screenshots below.

Windows Server 2012 R2 and Windows Server 2016

Click to enlarge.

Windows 10

Windows Server 2008 R2

Click to enlarge.

Windows 7

Last change on Jul 25, 2019 4:37:32 AM by Maike Guba [Paessler Support]

Please log in or register to enter your reply.

Chapter 5 Windows Installation

This chapter covers the following topics as they apply to a Windows installation of Message Queue 4.3:

Hardware Requirements

In order to install Message Queue 4.3, your Windows system should satisfy the minimum hardware requirements shown in Table 5–1. See Supported Platforms and Components for information on software requirements.

Table 5–1 Minimum Hardware Requirements for Windows Installation

Intel Pentium 3

(2 GB recommended for high-availability or high-volume deployments)

Compressed installation ( .zip ) file: approximately 45 MB

Temporary working directory (for extracting installation files): approximately 87 MB

Installed product: approximately 26 MB. More space may be needed if broker stores persistent messages locally.

Upgrading from Previous Versions

It is not possible on the Windows platform to upgrade directly to Message Queue 4.3 from an earlier Message Queue version, but you can either uninstall the earlier version or install Message Queue 4.3 side by side with it at a different location in your file system. See Upgrade Issues for details on how to preserve data from such a previous installation.

Caution –

The Message Queue 4.3 Installer does not share the same product registry with other installers, such as those of the Sun Java TM Enterprise System (JES) and Sun Java System Application Server, which include Message Queue as a component. The Message Queue Installer also installs or upgrades shared software components that Message Queue depends on, such as the Java Software Development Kit (SDK), Netscape Portable Runtime (NSPR), Network Security Services (NSS), and JavaHelp. Using this Installer to upgrade an earlier version of Message Queue that was installed with another installer may upgrade such shared components without correctly updating their version numbers in the other installer’s product registry, leaving that registry in an inconsistent state.

If you later run the other installer, the inconsistent registry entries may in turn cause that installer to inadvertently remove Message Queue 4.3. The safest and cleanest way to upgrade an earlier version of Message Queue that was installed with a different installer is as follows:

Use the other installer’s uninstaller to remove Message Queue.

Use the Message Queue 4.3 Installer to install Message Queue 4.3.

Installation Procedure

You can run the Message Queue Installer in either of two modes:

In GUI (graphical user interface) mode, the Installer presents a series of graphical screens with which you interact using mouse clicks and keyboard text entry.

In silent mode, the Installer operates from a predefined answer file representing your responses to the GUI screens. This allows you to script the installation process in advance and then perform it in batch mode without actually displaying the GUI screens and responding to them interactively.

The following sections describe each of these two modes of Installer operation.

Installing in GUI Mode

The following procedure shows how to use the Message Queue Installer in GUI mode to install the Message Queue 4.3 product on your Windows system.

To Install Message Queue in GUI Mode

Download the Message Queue Installer.

The Installer is available for download from the Message Queue product Web site at

It is distributed as a compressed archive ( .zip ) file named

Decompress the Installer archive.

Right-click on the mq4_3-installer-WINNT.zip file and choose Extract All from the context menu.

The Windows Extraction Wizard opens.

Follow the steps in the Extraction Wizard.

This creates a folder named

containing the files needed for Message Queue 4.3 installation.

Open the Installer folder.

Double-click on the mq4_3-installer folder to open it in Windows Explorer.

Start the Installer.

Locate the Installer executable (a VBS script) and double-click to launch it. The Installer’s Welcome screen (Figure 5–1) appears.

Figure 5–1 Installer Welcome Screen

Click the Next button.

The Installer’s License screen (Figure 5–2) appears.

Figure 5–2 Installer License Screen

Read and accept the product license agreement.

Installation and use of the Message Queue product are subject to your acceptance of the license agreement. You must read and accept the terms of the license agreement before installing the product.

Read the product license agreement.

Make sure the radio button labeled “I accept the terms in the license agreement” is selected.

If you instead select “I do not accept the terms in the license agreement,” the Next button becomes disabled. You cannot proceed with installation without accepting the license terms.

Click the Next button.

The Installer’s Install Home screen (Figure 5–3) appears.

Figure 5–3 Installer Install Home Screen

Specify the home directory in which to install Message Queue.

Provide the location of the installation home directory.

Enter the path to the installation home directory in the text field, or use the button marked with an ellipsis (…) to browse to it interactively.

If you enter a path to a directory that does not exist on your system, the Installer will create the directory for you automatically.

Click the Next button.

The Installer’s JDK Selection screen (Figure 5–4) appears.

Figure 5–4 Installer JDK Selection Screen

Specify the version of the Java SDK for Message Queue to use.

Select a Java SDK.

You can do this in either of two ways:

Choose an SDK already installed on your system.

The drop-down menu under the option “Choose a Java SDK from the list below” lists existing SDKs found in standard locations on your system. You can use this option to specify one of these SDKs for Message Queue to use.

Provide an explicit path to an existing SDK.

To use an SDK from a location other than the standard ones, enter its path in the text field under the option “Type in a Java SDK location below,” or use the button marked with an ellipsis (…) to browse to it interactively.

The third option in the JDK Selection screen, “Install and use the default version of the Java SDK,” is intended for use on other platforms; it is disabled and unavailable for Windows installation.

After installation is complete, you can check which version of the Java runtime Message Queue is using with the command

Click the Next button.

The Installer’s Multilingual Packages screen (Figure 5–5) appears.

Figure 5–5 Installer Multilingual Packages Screen

Specify whether to install multilingual packages.

By default, Message Queue is installed to operate in the English language only. The Multilingual Packages screen allows you to install it for use in another language.

If you will be using Message Queue in a language other than English, select the checkbox labeled “Install Message Queue multilingual packages.”

If you will be using Message Queue only in English, leave this checkbox deselected.

Caution –

If you choose not to install the multilingual packages and later decide that you do need them after all, there is no convenient way to install them incrementally: you will have to uninstall Message Queue and then repeat the entire installation procedure with the multilingual packages selected. Before proceeding to install without the multilingual packages, be sure you will not be needing them in the future.

Click the Next button.

The Installer’s Ready screen (Figure 5–6) appears.

Figure 5–6 Installer Ready Screen

Click Install to begin the installation.

The Installer’s Progress screen (Figure 5–7) appears, tracking the progress of the installation as it proceeds.

Figure 5–7 Installer Progress Screen

When installation is complete, the Installer’s Sun Connection Registration screen (Figure 5–8) appears.

Figure 5–8 Sun Connection Registration Screen

Register Message Queue with Sun Connection.

Sun Connection is a Sun-hosted service that helps you track, organize, and maintain Sun hardware and software. When you register a Message Queue installation with Sun Connection, information such as the release version, host name, operating system, installation date, and other such basic information is securely transmitted to the Sun Connection database. The Sun Connection inventory service can help you organize your Sun hardware and software, while the update service can inform you of the latest available security fixes, recommended updates, and feature enhancements.

Registration requires that you have a Sun Online account or create one. If you do not already have an account, the installer provides the following screen (Figure 5–9) for creating a Sun Online account:

Figure 5–9 Create Sun Online Account Screen

If you choose not to register Message Queue during installation, you can subsequently register Message Queue by running the installer in register-only mode, as follows:

The register-only mode requires that Message Queue 4.3 already be installed and will display only the installer screens related to registration.

When Sun Connection registration is complete, the Installer’s Summary screen (Figure 5–10) appears, summarizing the steps that were performed during installation.

Figure 5–10 Installer Summary Screen

You can click the links on this screen for a detailed summary report and a log file giving more details on the installation.

Click the Exit button to dismiss the Summary screen.

Message Queue installation is now complete.

After installation is complete, you can check that the expected version of Message Queue has been installed by navigating to the mqInstallHome \mq\bin directory and executing the following command:

The output from this command identifies the versions of Message Queue and the Java SDK that are installed on your system.

Installing in Silent Mode

In silent mode, the Installer operates from a predefined answer file representing your responses to the GUI screens. This allows you to script the installation process in advance and then perform it in batch mode without actually displaying the GUI screens and responding to them interactively.

To create an answer file, start the Installer with the -n option:

where answerFile identifies the file in which to record your responses. This causes the Installer to execute a “dry run,” presenting the sequence of GUI screens without actually performing the installation. Your input responses are recorded in the specified answer file. You can then perform the installation at a later time by starting the Installer with the -s (“silent”) option, specifying the same answer file:

This performs a silent installation as defined by the answer file, without visibly displaying the GUI screens.

Manually Configuring the Java Runtime Environment

The Message Queue Installer’s JDK Selection screen is not the only way to specify a version of the Java Runtime Environment for Message Queue to use. The JRE used by the Message Queue command line utilities ( imqadmin , imqbrokerd , imqcmd , imqobjmgr , imqdbmgr , imqusermgr , imqkeytool ) is determined by the following sources, in order of precedence:

The -jrehome or -javahome command line option to the imqbrokerd command. (If both are specified, the one occurring last on the command line takes precedence).

The J2SE file location specified in the jdk.env file. (This file is deprecated, but is still supported for backward compatibility. For historical reasons, it has higher priority than anything else except option 1.)

The IMQ_JAVAHOME environment variable.

The environment variable IMQ_DEFAULT_JAVAHOME in the imqenv.conf file.

The system default locations, as specified in the documentation for your platform.

To check which version of the Java runtime Message Queue will use, enter the command

The output from this command includes the version and pathname of the configured JRE: for example,

When you specify a JRE location through the Installer’s JDK Selection screen, the Installer saves that location as the value of IMQ_DEFAULT_JAVAHOME in the imqenv.conf file (option 4 in the list above). On Windows, this file is located by default at

After a successful Message Queue installation, it should include something like the following:

You can override this setting, however, either by editing the imqenv.conf file or by setting one of the other options higher in the list. This can be useful, for instance, for testing or reconfiguring the broker when a newer JRE version becomes available. Understanding how the JRE is determined can also help in troubleshooting problems. For instance, if the imqbrokerd -version command shows that Message Queue is using an unexpected JRE, it may be that one of the higher-precedence options has been set inadvertently (such as by an old jdk.env file that should have been deleted).

Configuring Message Queue for Automatic Startup

To start a Message Queue message broker automatically at Windows system startup, you must define the broker as a Windows service. The broker will then start at system startup time and run in the background until system shutdown. Consequently, you will not need to use the Message Queue Broker utility ( imqbrokerd ) unless you want to start an additional broker.

To install a broker as a Windows service, use the Message Queue Service Administrator utility:

You can use the imqsvcadmin command’s -args option to pass startup arguments to the broker. For more information, see the sections “Automatic Startup on Windows” in Chapter 3, “Starting Brokers and Clients,” and “Service Administrator Utility” in Chapter 13, “Command Line Reference,” of the Message Queue Administration Guide .

Installed Directory Structure

Table 5–2 shows the installed directory structure for Message Queue 4.3 on the Windows platform. Paths shown are relative to the Message Queue installation home directory, denoted by the directory variable mqInstallHome . This is the directory you specify to the Message Queue Installer in step 7 of the procedure To Install Message Queue in GUI Mode, above (by default, C:\Program Files\Sun\MessageQueue ).

Table 5–2 Installed Directory Structure (Windows)

mqInstallHome \mq\bin ( IMQ_HOME\bin )

Executable files for Message Queue administration tools:

Administration Console ( imqadmin )

Broker utility ( imqbrokerd )

Command utility ( imqcmd )

Object Manager utility ( imqobjmgr )

Database Manager utility ( imqdbmgr )

User Manager utility ( imqusermgr )

Key Tool utility ( imqkeytool )

Message Queue uninstall script ( nquninstall )

All executable files have the filename extension .exe . This directory also includes other executables ( imqbrokersvc ).

mqInstallHome \mq\lib ( IMQ_HOME\lib )

Support files for Message Queue Java client runtime:

.jar files for building and running Java Message Service (JMS) client applications

.rar files for JMS Resource Adapter

.war files for HTTP servlet and Universal Message Service (UMS) deployment

Support files for Message Queue tools and processes

Support libraries for C client applications

See Component Dependencies in Sun Java System Message Queue 4.3 Release Notes for the versions of Netscape Portable Runtime (NSPR) and Network Security Services (NSS) needed to support the C API.

mqInstallHome \mq\lib\props ( IMQ_HOME\lib\props )

Broker’s default configuration files

mqInstallHome \mq\lib\ext ( IMQ_HOME\lib\ext )

.jar or .zip files to be added to broker’s CLASSPATH environment variable

Typically used for configuring JDBC-based persistence or Java Authentication and Authorization Service (JAAS) login modules.

mqInstallHome \mq\lib\images ( IMQ_HOME\lib\images )

Administration GUI image files

mqInstallHome \mq\lib\help ( IMQ_HOME\lib\help )

Administration GUI help files

mqInstallHome \mq\javadoc ( IMQ_HOME\javadoc )

Message Queue and JMS API documentation in JavaDoc format

mqInstallHome \mq\examples ( IMQ_HOME\examples )

Example Java client applications

mqInstallHome \mq\examples\C ( IMQ_HOME\examples\C )

Example C client applications

mqInstallHome \mq\include ( IMQ_HOME\include )

Header files to support C client applications

mqInstallHome \var\mq ( IMQ_VARHOME )

Message Queue working storage

mqInstallHome \var\mq\instances ( IMQ_VARHOME\instances )

Configuration properties, file-based persistent data stores, log files, flat-file user repositories, and access control properties files for individual broker instances

Message Queue configuration files, instance template files, sample password file, and so forth

Message Queue installer implementation, required jar files, and installer log files

Message Queue uninstall script

Message Queue files needed by installer and uninstaller

Uninstallation Procedure

Like the Installer, the Message Queue Uninstaller can be run in either of two modes of operation:

In GUI (graphical user interface) mode, the Uninstaller presents a series of graphical screens with which you interact using mouse clicks and keyboard text entry.

In silent mode, the Uninstaller operates from a predefined answer file representing your responses to the GUI screens. This allows you to script the uninstallation process in advance and then perform it in batch mode without actually displaying the GUI screens and responding to them interactively.

The following sections describe each of these three modes of Uninstaller operation.

Caution –

The Message Queue installation includes several scripts and executables named uninstaller , both in the Installer .zip bundle and on your system after installation. To uninstall Message Queue 4.3, it is important that you run the correct uninstaller executable, located at

where mqInstallHome is the installation home directory you specified when you installed Message Queue 4.3 (by default, C:\Program Files\Sun\MessageQueue ). Be careful not to invoke some other uninstaller by mistake.

Uninstalling in GUI Mode

The following procedure shows how to use the Message Queue Uninstaller in GUI mode to uninstall Message Queue 4.3 from your Windows system.

To Uninstall Message Queue in GUI Mode

Start the Windows Command Prompt utility.

Choose Command Prompt from the Programs submenu of the Windows Start menu.

Set your working directory to the directory containing the Uninstaller.

Enter the command

where mqInstallHome is the installation home directory you specified to the Message Queue Installer’s Install Home screen in step 7 of the procedure To Install Message Queue in GUI Mode, above.

Start the Uninstaller.

Enter the command

The Uninstaller’s Ready screen (Figure 5–11) appears.

Figure 5–11 Uninstaller Ready Screen

Click the Remove button.

The Uninstaller’s Progress screen (Figure 5–12) appears.

Figure 5–12 Uninstaller Progress Screen

When uninstallation is complete, the Uninstaller’s Summary screen (Figure 5–13) appears, summarizing the steps that were performed during uninstallation. You can click the links on this screen for a detailed summary report and a log file giving more details on the uninstallation.

Figure 5–13 Uninstaller Summary Screen

Click the Exit button to dismiss the Summary screen.

Message Queue uninstallation is now complete.

Uninstalling in Silent Mode

In silent mode, the Uninstaller operates from a predefined answer file representing your responses to the GUI screens. This allows you to script the uninstallation process in advance and then perform it in batch mode without actually displaying the GUI screens and responding to them interactively. To create an answer file, start the Uninstaller with the -n option:

where answerFile identifies the file in which to record your responses. This causes the Uninstaller to execute a “dry run,” presenting the sequence of GUI screens without actually performing the uninstallation. Your input responses are recorded in the specified answer file. You can then perform the uninstallation at a later time by starting the Uninstaller with the -s (“silent”) option, specifying the same answer file:

This performs a silent uninstallation as defined by the answer file, without visibly displaying the GUI screens.