MSMQ setup

[Chris]

I created an XPe (SP2) image and added all the components prefixed by
"Message Queuing...". I ran a dependency check, built the image, deployed
it, resealed it and copied the image to a 2nd machine but I get an crash in
my application which might be due to problems with the MSMQ setup. The
MSMQ & MSMQ Triggers services are both running.

My VB6 component uses the MSMQ COM library and is able to send messages but
crashes when querying a property of a Queue object when receiving a message.

In msmqinst.log I can see that the "Final selection" shows "INSTALL" for
msmq_HTTP and "DO NOTHING" for the others. (My understanding is that MSMQ
setup thinks that some components are already installed.) Looking further
down the log I can see that only the msmq_HTTP component is installed. In
setupapi.log the "OcGetUnattendComponentSpec" entry for all the MSMQ
components shows "[on]".

Can someone help me out as to why all the MSMQ components aren't
(apparently) being installed?

 

[KM]

Chris,

The first thought - did you check XPe/SP1 Rel.Notes? There are some tips on MSMQ.
Here we go:

a.. To enable full functionality support of Message Queuing (MSMQ) COM Library and Message Queuing (MSMQ) DCOM Library components,
register Mqoa.dll by creating an FBA COM/DLL Registration resource or by running the command RegSvr32.exe MQOA.DLL from the command
line. Failure to register Mqoa.dll will have an impact on applications using IDispatch, such as Microsoft Visual Basic Scripting
Edition (VBScript) programming language and Active Server Pages (ASP).

 

[Chris]

Thanks. In my component the VB6 TypeName function of an MSMQ objects were
returning Object instead of the specific class name (as on XP Pro) which
explains a lot. I have registered MQOA.DLL and a number of others and now
get an "Access is denied" error which I suspect is permissions related.

I'm still a little confused over what happened with the MSMQ setup and which
components actually got installed? Does the MSMQ setup need to run on
every XPe machine or just the machine that was sealed? (We're using AD
integration & public queues.)

Chris,

The first thought - did you check XPe/SP1 Rel.Notes? There are some tips on MSMQ.
Here we go:

a.. To enable full functionality support of Message Queuing (MSMQ) COM

Library and Message Queuing (MSMQ) DCOM Library components,

register Mqoa.dll by creating an FBA COM/DLL Registration resource or by

running the command RegSvr32.exe MQOA.DLL from the command

line. Failure to register Mqoa.dll will have an impact on applications

using IDispatch, such as Microsoft Visual Basic Scripting

Edition (VBScript) programming language and Active Server Pages (ASP).

--
Regards,
KM, BSquare Corp.

I created an XPe (SP2) image and added all the components prefixed by
"Message Queuing...". I ran a dependency check, built the image, deployed
it, resealed it and copied the image to a 2nd machine but I get an crash in
my application which might be due to problems with the MSMQ setup. The
MSMQ & MSMQ Triggers services are both running.

My VB6 component uses the MSMQ COM library and is able to send messages but
crashes when querying a property of a Queue object when receiving a message.

In msmqinst.log I can see that the "Final selection" shows "INSTALL" for
msmq_HTTP and "DO NOTHING" for the others. (My understanding is that MSMQ
setup thinks that some components are already installed.) Looking further
down the log I can see that only the msmq_HTTP component is installed. In
setupapi.log the "OcGetUnattendComponentSpec" entry for all the MSMQ
components shows "[on]".

Can someone help me out as to why all the MSMQ components aren't
(apparently) being installed?

 

[KM]

Chris,

Thanks. In my component the VB6 TypeName function of an MSMQ objects were
returning Object instead of the specific class name (as on XP Pro) which
explains a lot. I have registered MQOA.DLL and a number of others and now
get an "Access is denied" error which I suspect is permissions related.

I'm still a little confused over what happened with the MSMQ setup and which
components actually got installed? Does the MSMQ setup need to run on
every XPe machine or just the machine that was sealed? (We're using AD
integration & public queues.)

To answer your question I have to understand what you mean by MSMQ setup.

I don't recall any fbreseal problems with MSMQ components.

KM

Chris,

The first thought - did you check XPe/SP1 Rel.Notes? There are some tips on MSMQ.
Here we go:

a.. To enable full functionality support of Message Queuing (MSMQ) COM

Library and Message Queuing (MSMQ) DCOM Library components,

register Mqoa.dll by creating an FBA COM/DLL Registration resource or by

running the command RegSvr32.exe MQOA.DLL from the command

line. Failure to register Mqoa.dll will have an impact on applications

using IDispatch, such as Microsoft Visual Basic Scripting

Edition (VBScript) programming language and Active Server Pages (ASP).

--
Regards,
KM, BSquare Corp.

I created an XPe (SP2) image and added all the components prefixed by
"Message Queuing...". I ran a dependency check, built the image, deployed
it, resealed it and copied the image to a 2nd machine but I get an crash in
my application which might be due to problems with the MSMQ setup. The
MSMQ & MSMQ Triggers services are both running.

My VB6 component uses the MSMQ COM library and is able to send messages but
crashes when querying a property of a Queue object when receiving a message.

In msmqinst.log I can see that the "Final selection" shows "INSTALL" for
msmq_HTTP and "DO NOTHING" for the others. (My understanding is that MSMQ
setup thinks that some components are already installed.) Looking further
down the log I can see that only the msmq_HTTP component is installed. In
setupapi.log the "OcGetUnattendComponentSpec" entry for all the MSMQ
components shows "[on]".

Can someone help me out as to why all the MSMQ components aren't
(apparently) being installed?

 

[Chris]

By MSMQ setup I mean adding, configuring and registering the MSMQ components
that were added to the image. (i.e. Indpendent client, AD integration etc
as determined by the components selected.) On a non-XPe OS the equivalent
would be from the Add / Remove Programs dialogue or by running SYSOCMGR.EXE.

I had assumed that the setup would be started by FBA.

 

[KM]

Chris,

I see.
The reason I asked about the Setup was that it is your own code (or binary app) and I don't really know what it does and how it
works. Therefore I can't easy answer your question regarding the image cloning.

I would think that if you properly reseal the image and it generates unique SIDs on your client devices, there shouldn't be any
problem with the MSMQ Setup (assuming all the dependencies are satisfied but you check and test it before the cloning, right?). With
AD, you can consider your XPE clients as just XP Pro machines on the network.