Microsoft Message Queuing failed

  • N.º del artículo: 116488
  • Actualizado: 27 ago 2013

Issue

At the end of the Enterprise Console 5.x installation, the following error message is displayed:

Sophos Enterprise Console 5.0.0 Installation Failed
Microsoft Message Queuing failed.

First seen in

Enterprise Console 5.0.0

Cause

There are many reasons that the Microsoft component MSMQ may fail to install.  Please see the 'What To Do' section below for guidance on resolving this issue.

What To Do

Firstly it is recommended to manually try adding the MSMQ component to Windows.  This can be added as follows:

Windows 2003
  1. Start | Run | type: appwiz.cpl | Press Return.
  2. Click 'Add/Remove Windows Components' (to the left of the installed programs).
  3. Highlight 'Application Server' and hit 'Details'.
  4. Tick 'Message Queuing' and select 'Details'.
  5. Ensure that the sub-component 'Common' is selected.

Windows 2008

  1. Start | Run | type: appwiz.cpl | Press Return.
  2. Click on 'Turn Windows Features on or off'.
  3. In the 'Server Manager' window, in the left-hand pane, right click 'Features' and select 'Add Features'.
  4. From the available list of features, locate 'Message Queuing' | 'Message Queuing Services' | 'Message Queuing Server'.
  5. Tick 'Message Queuing Server' and click 'Next' to add the feature.

Once you have added the component please re-run the Enterprise Console installer, i.e. 'C:\sec_50\ServerInstaller\Setup.exe'.

If you are still having problems, please check the Windows Application Event log for errors when adding the MSMQ component and if necessary consult the log file: 'C:\windows\msmqinst.log'.

One possibility is that the port 1801 is in use by another process.  

Note: Future versions of Enterprise Console installer perform a check to see if port 1801 is in use. 

The port already being in use is more likely to be the case on Windows 2003 based on the default ephemeral port range including port 1801.  To establish if this is the case; in a command prompt running as an administrative user, execute the command:

netstat -abno > netstat.txt

Once complete, search the output file, netstat.txt for ':1801' (minus the quotes), If this makes a match it should reveal the process using the port.  If possible stop the process and retry the install.  It maybe sufficient to restart the process using the port as this should free up port 1801 as long as it is not re-taken by the process.

 
Si necesita más ayuda, póngase en contacto con soporte técnico.

Valore el artículo

Muy malo Excelente

Comentarios