Vista/MSMQ question

I'm developing an application geared towards the Vista platform and I'd like
to use MSMQ services through WCF.
My concern is that by default, MSMQ in not installed and I'm hesitant to
"hope" that even with simple instructions one can ask a non-technically
inclined user to install MSMQ services in order to use my application.

Is there a programmatic way to invoke / install MSMQ?

"ESmith" <> wrote in message
news:...
> I'm developing an application geared towards the Vista platform and I'd
> like to use MSMQ services through WCF.
> My concern is that by default, MSMQ in not installed and I'm hesitant to
> "hope" that even with simple instructions one can ask a non-technically
> inclined user to install MSMQ services in order to use my application.
>
> Is there a programmatic way to invoke / install MSMQ?
>
This is a user to user support group. You will probably have better luck
with this question in a developer such as one of the MSDN, Microsoft
Developers Network, newsgroups:

http://msdn.microsoft.com/newsgroups/default.aspx
--
Michael Solomon
Backup is a PC user's best friend
DTS-L.Org: http://www.dts-l.org/

"ESmith" <> wrote ...
> I'm developing an application geared towards the Vista platform and I'd
> like to use MSMQ services through WCF.
> My concern is that by default, MSMQ in not installed and I'm hesitant to
> "hope" that even with simple instructions one can ask a non-technically
> inclined user to install MSMQ services in order to use my application.

Hi Eliana,

It's not programmatic, as such; but you can start a silent installation of
MSMQ from the command line, by using the new "Package Manager" facility in
Vista and Server 2008 (and, yes: this is very reminiscent of BSD Unix and
Solaris!!! :-).Run "pkgmgr /?" at a command prompt, to see the syntax.

To install MSMQ the command would basically be:

C:\>pkgmgr /iu:MSMQ-Container;MSMQ-Server

You could run this is a batch file, script or ShellExec() call in your code.
Be aware that Windows may require Administrator consent to complete the
installation (although, there may be workarounds).

The exact details of package names for various Windows components is
described in the WAIK ("Windows Automated Installer Kit"); see
http://www.microsoft.com/downloads/d...DisplayLang=en

Thank you for using MSMQ - this is one of the most powerful and little-known
features of Windows. I spent several years working with MSMQ applications;
it can reliably sustain very high transaction rates in punishing enterprise
environments.

Good luck with the project.
--
Andrew McLaren
amclar (at) optusnet dot com dot au

Hi all!
I have a problem with msmq installation on my computer (Windows Vista, MSMQ
4.0). My computer is in domain and domain controller on Win 2003 server. I
have tried to install msmq in domain mode but it always is in workgroup mode
even if i have installed it without Active Directory Domain Services
integration and delete my msmq settings from AD before installation. Does
enyone know steps to fix this problem? I am a developer and need to be able
to access public queues either on my local machine as on servers.

"Marina" <> wrote ...
> I have a problem with msmq installation on my computer (Windows Vista,
> MSMQ
> 4.0). My computer is in domain and domain controller on Win 2003 server. I
> have tried to install msmq in domain mode but it always is in workgroup
> mode
> even if i have installed it without Active Directory Domain Services
> integration and delete my msmq settings from AD before installation. Does
> enyone know steps to fix this problem? I am a developer and need to be
> able
> to access public queues either on my local machine as on servers.


Hi Marina

There could be a few causes. I'd suggest you try asking over in the
microsoft.public.msmq.setup newsgroup - John B and the other folks there can
probably answer this off the top of their heads.

The main causes I'd investigate:

1) permissions - you need to make sure you are running as Administrator,
when you install MSMQ. If you don't have permissions to create AD objects,
MSMQ Setup may fall back to Workgroup mode. If you are using pkgmgr to
install, it is not enough merely to be logged in as an Administrator, you
must start it from a Command Prompt which you run "As Administrator" from
the context menu; ie, it must say "Administrator:Command Prompt" in the
title bar.

2) Problems contacting the Domain Controller - make sure there are no
networking issues.

3) Under HKLM\SOFTWARE\Microsoft\MSMQ\Parameters the REG_DWORD value
"Workgroup" is set to 1 not 0, and you don't have permissions to change it.
Workgroup must be 0, in order for Domain integration to work (and thus,
Public Queues to be available).

FWIW, I have MSMQ installed on several Vista workstations and haven't had
any problems accessing public queues ... whatever is blocking your setup is
likely to be some small glitch easily corrected, and domain mode should work
fine after that.

--
Andrew McLaren
amclar (at) optusnet dot com dot au

Unfortunaly, these issues didn't help.
Yes, I'm an admin on my computer, and we don't have some problems with
domaim controller access. I have asked our network administrator to install
msmq with his rights by it doesn't help too, the result is the same and
Workgroup key = 1 in register. I have read/write access to my active
directory (AD of my computer). Change of register key was helpful to create
public queue but i coudn't acces it from application (web service. My app
doesn't see it if i configure it by name "DIRECT=OS:<computer name>\<queue
name> and says "A workgroup installation computer does not support the
operation." for name = "<comp name>\<queue name>"). And i can't open queue
messages subfolder from Server Explorer too (from VS 2005) with error about
workgroup installation. Do someone have any other idea?


"Andrew McLaren" wrote:

> "Marina" <> wrote ...
> > I have a problem with msmq installation on my computer (Windows Vista,
> > MSMQ
> > 4.0). My computer is in domain and domain controller on Win 2003 server. I
> > have tried to install msmq in domain mode but it always is in workgroup
> > mode
> > even if i have installed it without Active Directory Domain Services
> > integration and delete my msmq settings from AD before installation. Does
> > enyone know steps to fix this problem? I am a developer and need to be
> > able
> > to access public queues either on my local machine as on servers.
>
>
> Hi Marina
>
> There could be a few causes. I'd suggest you try asking over in the
> microsoft.public.msmq.setup newsgroup - John B and the other folks there can
> probably answer this off the top of their heads.
>
> The main causes I'd investigate:
>
> 1) permissions - you need to make sure you are running as Administrator,
> when you install MSMQ. If you don't have permissions to create AD objects,
> MSMQ Setup may fall back to Workgroup mode. If you are using pkgmgr to
> install, it is not enough merely to be logged in as an Administrator, you
> must start it from a Command Prompt which you run "As Administrator" from
> the context menu; ie, it must say "Administrator:Command Prompt" in the
> title bar.
>
> 2) Problems contacting the Domain Controller - make sure there are no
> networking issues.
>
> 3) Under HKLM\SOFTWARE\Microsoft\MSMQ\Parameters the REG_DWORD value
> "Workgroup" is set to 1 not 0, and you don't have permissions to change it.
> Workgroup must be 0, in order for Domain integration to work (and thus,
> Public Queues to be available).
>
> FWIW, I have MSMQ installed on several Vista workstations and haven't had
> any problems accessing public queues ... whatever is blocking your setup is
> likely to be some small glitch easily corrected, and domain mode should work
> fine after that.
>
> --
> Andrew McLaren
> amclar (at) optusnet dot com dot au
>
>

"Marina" <> wrote ...

> Unfortunaly, these issues didn't help.

In that case, I strongly recommend you shift the discussion across to
microsoft.public.msmq.deployment.

The problem you are seeing needs to be solved; but it is not intrinsic to
Vista. In general, MSMQ can run in Domain mode on Vista, much the same as it
did on Windows 2003 and XP. I suspect there's some slightly unusual factor
in your environment which is causing the effect you're seeing. It's not
necessarily wrong; just something you need to take into account.

This KnowledgeBase article might be relevant:
http://support.microsoft.com/default...b;EN-US;935498

This article discusses MSMQ on the "server" but applies to MSMQ 4.0 on Vista
workstation as well.

If that doesn't solve the problem, please ask over on
microsoft.public.msmq.deployment.

--
Andrew McLaren
amclar (at) optusnet dot com dot au