Unable To Configure Oracle MessageQ 5.0 Service On Window Server 2008 (Doc ID 1384450.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle MessageQ - Version: 5.0 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

.
Assuming:
- the MessageQ software has been installed on the Windows platform, and the related BEADIR environment variable defined to its root directory,
- a MessageQ group has been created with its related environment variables (DMQ_BUS_ID and DMQ_GROUP_ID), and can be started and stopped through manual commands such as:
"%BEADIR%\bin\dmqstartup.exe" -b %DMQ_BUS_ID% -g %DMQ_GROUP_ID% -f <config-file> -n <Group_name> -l <LogFileName>

MessageQ Service Utility (%BEADIR%\bin\dmqedit.exe) allows to configure bus(es) and group(s) that will be started at machine startup.
Configuring under Administrator account is Ok, but frequently for security reasons, the account which is used is not Administrator and has just administration rights.
However on 'recent' Windows platform such as Window server 2008, this seems to fail.
.

Changes

.
'recent' Window operating systems have an enhanced security mechanism which does not elevate by default to Administrator mode.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms